[Bug 223825] Re: aiccu init.d script will race dhclient (upstart issue?)
Lars Düsing
lars at camelotsweb.de
Fri Nov 6 21:28:12 GMT 2009
Ok, after some reading through source-code of upstart, browsing through
upstart-wiki, and countless reboots , I found the problem:
Nov 6 22:14:12 artus init: aiccu main process (1691) became new process (1702)
Nov 6 22:14:12 artus aiccu: AICCU running as PID 1747
Nov 6 22:19:30 artus init: Handling net-device-down event
Nov 6 22:19:30 artus init: aiccu goal changed from start to stop
Nov 6 22:19:30 artus init: aiccu state changed from running to pre-stop
Nov 6 22:19:30 artus init: aiccu state changed from pre-stop to stopping
Nov 6 22:19:30 artus init: Handling stopping event
Nov 6 22:19:30 artus init: aiccu state changed from stopping to killed
Nov 6 22:19:30 artus init: Sending TERM signal to aiccu main process (1702)
upstart wants to kill a process that is not there anymore at all.
(and this is also the problem, why aiccu won't be reloaded any more... ->#21 MY FAULT :) )
so please wait a little bit, until I got over that. (and sorry for not
answering sooner, I happen to have a flu [no, not that one!])
--
aiccu init.d script will race dhclient (upstart issue?)
https://bugs.launchpad.net/bugs/223825
You received this bug notification because you are a member of Ubuntu
Sponsors for universe, which is a direct subscriber.
More information about the Ubuntu-universe-sponsors
mailing list