Problem: Process or Daemon Dies

This article describes how to determine what is killing a process or daemon on your VPSLink virtual private server.

OpenVZ Platform-Specific Troubleshooting Instructions

Run cat /proc/user_beancounters and check the failcnt column - if you notice any failcnt values, there is a good chance that qmail is being killed for pushing your VPS over its memory allocation limit.

Please see the Meaning of the beancounters values for more information on the beancounters rows.

If you have determined that the process or daemon is not being killed as a result of its memory usage, proceed to the General Troubleshooting Instructions.

General Troubleshooting Instructions

1. Review log files for the process or daemon
2. If the process or daemon's log files do not indicate the cause of the issue, use strace to log the activity of the process or daemon:
   1. Download and install strace
   2. Begin stack trace logging for the process or daemon and its child processes with the following command:
      nohup strace -f -p `pgrep <process_name>` 2>&1 | tail -1000 > ~/strace.log
      (where <process_name> is the name of the process or daemon which you would like to track)
   3. Post relevant log entries on the VPSLink forums in the appropriate subforum for community review