pid stands for
process id. Every program instance running on your server runs with it's own pid. The pids can be dynamic for processes that start and stop, or last a long time for processes that run until you reboot.
to find what program is running under a particular pid, run:
where in this case you'd replace
nnnnnnn with 59405.
However based on the error message, I think you won't find anything; no such process means there's no such PID. Which could happen if you've got a stale pid file.
Check the contents of all the pid files:
Code:
grep nnnnnnn /var/run/*.pid
again changing the
nnnnnnn as above. The left side of the filename returned (before the
.pid is the name of the daemon that the system thinks is running under that pid. You need to restart that daemon; generally you can do it this way:
where NAME is replaced by the name of the daemon as found above.
It appears that newsyslog can't restart one of the daemons; it probably tries to do that as part of logrotate.
Jeff