• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Health alarm

mastrofreddy

New Pleskian
Hello,

I've checked my health-alarm.log and I've found tons of this message:
2016-09-04T08:37:01+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)

The health monitor works normally.
I don't have any idea about the reason of this error and I wasn't able to find anything related to it.

Could someone help me?

Thanks
 
Most probably that database server was stopped for some reasons during this time period.
Do you have the same error messages now?
 
Yes, always the same error.
Thank you, IgorG

2016-09-07T11:46:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T11:51:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T11:56:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:01:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:06:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:11:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:16:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:21:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:26:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:31:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:36:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
2016-09-07T12:41:55+02:00 ERR (3): Unable to connect to database: Empty error message from utility. (Error code: 1045)
 
Hello,
I have the exact same message every 5 minutes in /var/log/plesk/health-alarm.log
mysql.err and mysql.log are empty
Did you find any clue on this ?
TIA
Marc
 
Back
Top