Strange Problem - Services Reported as Dead

ljj3

• January 25, 2021 10:31

On a brand new VPS running 92.0.9 with zero loading last evening CPDAVD failed and restarted several times. This morning a bazillion emails - every service failed - all showing as failed in WHM - but all of them apparently up and running. Log: Service Check Started Loading services .....apache_php_fpm....cpanellogd....cpdavd....cphulkd....cpsrvd....crond....dnsadmin....exim....ftpd....httpd....imap....ipaliases....lfd....lmtp....mailman....mysql....nscd....pop....queueprocd....rsyslogd....spamd....sshd..Done [2021-01-25 09:21:34 -0500] Disk check .... /tmp (/tmp) [5.38%] ... / (/) [15.55%] ... /var/tmp (/var/tmp) [5.38%] ... {status:eek:k} ... Done [2021-01-25 09:21:34 -0500] OOM check ....Done [2021-01-25 09:21:34 -0500] Service check .... queueprocd [[check command:-][check command output: The subprocess "/usr/local/cpanel/scripts/restartsrv_queueprocd" ended prematurely because it received the "SEGV" (11) signal.][socket connect:N/A][fail count:72]Restarting queueprocd.... [notify:failed service:queueprocd]]... sshd [[check command:-][check command output: The subprocess "/usr/local/cpanel/scripts/restartsrv_sshd" ended prematurely because it received the "SEGV" (11) signal.][socket connect:N/A][fail count:72]Restarting sshd.... [notify:failed service:sshd]]... spamd [[check command:-][check command output: The subprocess "/usr/local/cpanel/scripts/restartsrv_spamd" ended prematurely because it received the "SEGV" (11) signal.][socket connect:N/A][fail count:72]Restarting spamd.... [notify:failed service:spamd]]... rsyslogd [[check command:+][socket connect:N/A]]... pop [[check command:-][check command output: The subprocess "/usr/local/cpanel/scripts/restartsrv_imap" ended prematurely because it received the "SEGV" (11) signal.][socket connect:N/A][fail count:72]Restarting pop.... [notify:failed service:pop]]... p0f [[check command:N/A][socket connect:N/A]]... nscd [[check command:-][check command output: The subprocess "/usr/local/cpanel/scripts/restartsrv_nscd" ended prematurely because it received the "SEGV" (11) signal.][socket connect:N/A][fail count:72]Restarting nscd.... [notify:failed service:nscd]]... named [[check command:N/A][socket connect:N/A]]... mysql [[check command:-][check command output: The subprocess "/usr/local/cpanel/scripts/restartsrv_mysql" ended prematurely because it received the "SEGV" (11) signal.][socket connect:N/A][fail count:72]Restarting mysql.... [notify:failed service:mysql]]... mailman [[check command:-][check command output: The subprocess "/usr/local/cpanel/scripts/restartsrv_mailman" ended prematurely because it received the "SEGV" (11) signal.][socket connect:N/A][fail count:72]Restarting mailman.... [notify:failed service:mailman]]... lmtp [[check command:-][check command output:

• 

  cPRex Jurassic Moderator

  • January 25, 2021 16:04

  Hey there! You mention this was a VPS server, so it's always possible the parent system had issues that affected your instance. I would recommend checking the /var/log/messages file on the system, looking for timestamps that match up with then these service failures and restarts started happening. If you don't find anything there that helps, I'd contact the hosting provider to see if they can check things on their end.

  0
• 

  ljj3

  • January 25, 2021 17:02

  yep, been thru all the logs - nothing jumps out..... we have many vps' at same provider and no issue like this, but we will check with them....

  0
• 

  cPRex Jurassic Moderator

  • January 25, 2021 17:36

  Hopefully the provider will be able to get you more details. You're always welcome to submit a ticket directly to us if you'd like us to take a look at the machine for you.

  0
• 

  ljj3

  • January 25, 2021 18:53

  they forced a reinstall of the last cpanel update - /scripts/upcp --force we'll see if that helps...

  0
• 

  cPRex Jurassic Moderator

  • January 25, 2021 18:59

  I suppose it's possible, but I wouldn't expect a cPanel update to help keep *all* the services from failing on the machine. That would seem to indicate a deeper issue to me, like lack of resources on the instance or parent.

  0
• 

  ljj3

  • January 25, 2021 19:12

  I may have been unclear - the services were actually up - but reported down......

  0
• 

  cPRex Jurassic Moderator

  • January 25, 2021 19:14

  Thanks for the clarification. That could certainly be fixed with a forced update then if there were some cPanel files that were out of sync. Let me know if you see that happen again!

  0

Please sign in to leave a comment.