I found the elog dead again this morning, and the script didn't kill again. I modified the script to use the following line instead of "pkill elogd":
kill `ps -ef | grep elogd | grep -v grep | grep -v start-elog-nodus | awk '{print $2}'`
Hopefully the script will be a bit more robust in the future.
Quote: |
Quote: |
The elog was so dead this time that the restart script didn't work. I followed the restart-by-hand instructions instead, with success.
|
Just for added interest, I tried a different method when the restart script broke. The "start-elog-nodus" script has a line "kill elogd". This seems not to be actually killing anything anymore, which means the elog can't restart. So this time I went for "kill <pid number>", and then ran the startup script. This worked. So it's the "kill elogd" which isn't working reliably.
|
|