Skip to main content

cPanel service being killed

Comments

3 comments

  • darklord1
    Hi, First bit of advice is to utilize a monitoring service from a 3rd party like pingdom or something of that nature to help determine if the shutdown occurs on a standard interval or not. Also, check out the logs in /var/log/ (anywhere). There may be some information here. High CPU would not be the likely cause of exim shutting down, so I would think there was something else going on. Disk usage hitting 100% will lock the services up and they would appear down. Make sure you do a `ps aux` and see if cPanel/exim/imap is running before thinking they are 100% down. Incase it's something silly, like a backup or process running, check all your cron jobs to make sure nothing is running when things go down. Truth is, there are a lot more complex and efficient ways of determining this. I only offer the advice the way I do because it fits every user of every technical level. - Removed -
    0
  • Stichting FreeSpeechTube
    Hm, all right; thanks for the pointers.
    0
  • cPanelLauren
    I also want to point out that this shouldn't be occurring on a routine basis, I'd second the advice provided by @darklord1 here - /var/log/mesages may be extremely helpful to identify which if any services are being killed (based on the error message it would appear cpsrvd is being killed) You might also check some system statistics using sysstat which can be helpful in identifying resource usage issues. This will get you the memory usage since 12am sar -r
    This will get you the CPU usage since 12am sar -p
    You can also view historical usage by pointing to the file directly at /var/log/sa/saXX where XX = the day of the month. For example if I wanted yesterday's memory stats I would run: sar -r -f /var/log/sa/sa07
    If I wanted the CPU usage from the first I would run: sar -f /var/log/sa/sa01
    0

Please sign in to leave a comment.