Plesk MultiServer: service node is marked as unavailable if web configuration is broken

Created:

2016-12-28 06:11:32 UTC

Modified:

2017-08-10 15:10:34 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Plesk MultiServer: service node is marked as unavailable if web configuration is broken

Note: This article has the reference to the issue with the fix available:

  • #EXTPMS-1212 "A service node became unavailable in the case of a web server configuration error."
    Fixed in:
Please consider updating your server:

Symptoms

Plesk Multi-Server Service Nodes is marked as unavailable .

On the service node, psa.Configurations table contains 'error' status:

mysql> select count(1) from Configurations where status <> 'ok';
+----------+
| count(*) |
+----------+
|        1 |
+----------+
1 row in set (0.03 sec)

Cause

Software bug with id #EXTPMS-1212 that was fixed in Multi Server 1.1.2

Resolution

As a workaround, use the following solution:

1. Download attached file SlaveNodeValidator.php

2. Copy this downloaded file to the management node, to the temporary place:

 # scp SlaveNodeValidator.php login@example.com.ip:/tmp

3. Backup previous file SlaveNodeValidator.php, just in case. At the management node:

# cp /usr/local/psa/admin/plib/modules/plesk-multi-server/library/Model/Node/SlaveNodeValidator.php /tmp/SlaveNodeValidator.php.back

4. Copy new file at the place of old SlaveNodeValidator.php

# cp /tmp/SlaveNodeValidator.php /usr/local/psa/admin/plib/modules/plesk-multi-server/library/Model/Node/SlaveNodeValidator.php

Attachments:

Have more questions? Submit a request
Please sign in to leave a comment.