mySQL service not accessible issue

RickKukiela

• November 29, 2017 10:29

So I have an application running on several hosting accounts on my server that are developed by me and as such I have code in my database driver that emails me a copy of any SQL error occurs so I can stay ahead of any bugs that may arise. That being said. Every day. And I mean EVERY DAY. I get several mysql error log emails from my application that states the following: MySQL Connection Error - No such file or directory I have checked the mysql logs and there is no record of the server shutting down. In fact its up time is the same as the server it's self. I decided to check the messages log to see what the server is doing, if anything at the given time stamps, and every time I get these messages, I find something like this in the log:
250781 Nov 29 05:59:04 host systemd: Stopping tailwatchd... 250782 Nov 29 05:59:05 host restartsrv_tailwatchd: [2982] [2017-11-29 05:59:05 -0600] [main] Current process '16892' stopped 250783 Nov 29 05:59:05 host systemd: Stopped tailwatchd. 250784 Nov 29 05:59:05 host systemd: Starting tailwatchd... 250786 Nov 29 05:59:06 host restartsrv_tailwatchd: [Wed Nov 29 05:59:06 2017] Starting /usr/local/cpanel/libexec/tailwatch/tailwatchd daemon 250787 Nov 29 05:59:06 host restartsrv_tailwatchd: Log is at /usr/local/cpanel/logs/tailwatchd_log 250788 Nov 29 05:59:06 host systemd: tailwatchd.service: Supervising process 3010 which is not our child. We'll most likely not notice when it exits. 250789 Nov 29 05:59:06 host systemd: Started tailwatchd. 250790 Nov 29 05:59:07 host systemd: Stopping tailwatchd... 250792 Nov 29 05:59:08 host restartsrv_tailwatchd: [3035] [2017-11-29 05:59:08 -0600] [main] Current process '3010' stopped 250793 Nov 29 05:59:08 host systemd: Stopped tailwatchd. 250794 Nov 29 05:59:08 host systemd: Starting tailwatchd... 250795 Nov 29 05:59:09 host restartsrv_tailwatchd: [Wed Nov 29 05:59:09 2017] Starting /usr/local/cpanel/libexec/tailwatch/tailwatchd daemon 250796 Nov 29 05:59:09 host restartsrv_tailwatchd: Log is at /usr/local/cpanel/logs/tailwatchd_log 250797 Nov 29 05:59:09 host systemd: tailwatchd.service: Supervising process 3051 which is not our child. We'll most likely not notice when it exits. 250798 Nov 29 05:59:09 host systemd: Started tailwatchd. 250802 Nov 29 05:59:11 host systemd: Stopping tailwatchd... 250804 Nov 29 05:59:12 host restartsrv_tailwatchd: [3073] [2017-11-29 05:59:12 -0600] [main] Current process '3051' stopped 250805 Nov 29 05:59:12 host systemd: Stopped tailwatchd. 250806 Nov 29 05:59:12 host systemd: Starting tailwatchd... 250807 Nov 29 05:59:12 host restartsrv_tailwatchd: [Wed Nov 29 05:59:12 2017] Starting /usr/local/cpanel/libexec/tailwatch/tailwatchd daemon 250808 Nov 29 05:59:12 host restartsrv_tailwatchd: Log is at /usr/local/cpanel/logs/tailwatchd_log 250809 Nov 29 05:59:12 host systemd: tailwatchd.service: Supervising process 3092 which is not our child. We'll most likely not notice when it exits. 250810 Nov 29 05:59:12 host systemd: Started tailwatchd.
Why does tailwatchd do this? And why does it cause PHP to not be able to find the mysql socket file?

• 

  cPanelMichael

  • November 29, 2017 17:55

  Hello, Could you open a support ticket using the link in my signature so we can take a closer look? Thank you.

  0

Please sign in to leave a comment.