Re: daemontools-0.76, AIX 5.2: problem restarting service
[email protected] (Paul Jarc)
| Newsgroups | gmane.comp.djb.syslog |
|---|---|
| Organization | What did you have in mind? A short, blunt, human pyramid? |
| Message-ID | <[email protected]> |
Jurjen Oskam <[email protected]> wrote: > I know that one supervise process was killed, the one supervising > the service /service/enable-printers. Then it's possible there may be two instances of the service running. Stop the service with "svc -d" and then use ps to check whether it is still running. If so, kill it and then restart the supervised instance with "svc -u". > Now, the state of the services is: > > /service/clear-errors: down 4462 seconds, normally up, want up > /service/dsmcad: up (pid 766010) 783525 seconds > /service/enable-printers: up (pid 360594) 1081 seconds > /service/nmbd: up (pid 774230) 776558 seconds > /service/qmail-send: up (pid 704574) 775375 seconds > /service/qmail-smtpd: down 1198531 seconds > /service/smbd: up (pid 823454) 776558 seconds > /service/umclient: up (pid 184372) 1198531 seconds > /service/qmail-send/log: up (pid 167974) 1198531 seconds > /service/qmail-smtpd/log: up (pid 278668) 1198531 seconds > /service/umclient/log: up (pid 274568) 1198531 seconds You should check /service/*/log too. > A truss of the complaining supervise process only showed one line, and I > interrupted it after 5 minutes: > > # truss -p 188608 > _poll(0x00000000, 0, 0) (sleeping...) > Pstatus: process is not stopped AFAICT, this shouldn't be possible. But maybe your kernel exhibits bugs after running out of memory. svc -t might help; rebooting also might not be a bad idea. paul