[00:13] for what it's worth, 'stop cron' does actually kill the cron process (as does 'restart cron', though that one doesn't bring it back up) [00:13] so it's communicating enough that it can do its job, but then not cleaning up properly or continuing to further steps, I guess [00:35] for what it's worth, --verbose doesn't seem to write anything when running stop / restart at runtime, though I do see all the console output at first run [00:35] er, at boot === JanC_ is now known as JanC [18:39] did anyone get around to looking at those strace outputs I pastebined yesterday? [18:58] hi there [18:58] searching for some helping hand of shutdown [18:59] with natty [18:59] + debugging [19:00] problem is that a handfull of services is not shutdown [19:04] define "not shutdown" [19:06] its stopped on runlevel [19:06] 016 [19:06] and i can see until very late in shutdown process normal messages [19:06] of the daemon [19:07] it doesnt do any shutdown messages [19:07] stopping plugins [19:07] or anything [19:07] and late in the boot [19:07] i get stopped with status 1 [19:08] i.e. [19:08] openbox main process (1273) terminated with status 1 [19:09] I doubt openbox is handled by upstart? [19:10] with that message, I'd say it is [19:10] in my install it is [19:10] i written the job ;) [19:11] if you are doing such a customized setup, why use runlevels? [19:11] nice try ;) [19:11] stop on runlevel [016] [19:12] is openbox also others which look the same [19:12] the system is ubuntu natty , customized [19:12] heh [19:13] i dont want to customize everything only the part which we care [19:13] thats why we base it on ubuntu [19:13] i put a test job in to see if the runlevel come [19:14] and that one is executed fine [19:14] is X also started by upstart? [19:14] the openbox job starts X [19:14] xinit openbox basically [19:15] so it's probably X that exits with status 1 ? [19:16] i dont debug that one job [19:16] its maybe 10 [19:16] all show the same behaviour [19:16] all working fine on lucid [19:19] did you check the PID is actually correct? [19:20] believe me the jobs are working [19:20] May 5 19:12:47 vdr init: plymouth-stop pre-start process (1269) terminated with status 1 [19:20] May 5 19:12:47 vdr init: plymouth-splash main process (1328) terminated with status 1 [19:20] May 5 19:39:45 vdr init: vdr-frontend main process (1437) terminated with status 143 [19:20] May 5 19:39:45 vdr init: udisks-automounter main process (1594) terminated with status 143 [19:20] May 5 19:39:45 vdr init: plymouth-upstart-bridge main process (2186) terminated with status 1 [19:20] May 5 19:39:45 vdr init: irexec main process (2245) terminated with status 1 [19:20] this terminated with status 1 doesnt look normal [19:21] and is also not happening each boot [19:21] so something strange is happening in the shutdown [19:22] doesn't seem to happen on a "normal" natty system either? [19:23] looks like something in the shutdown is killing the jobs while they are active [19:23] May 5 19:39:45 vdr init: irexec main process (2245) terminated with status 1 [19:23] May 5 19:39:45 vdr init: irexec main process (2246) terminated with status 1 [19:23] May 5 19:39:45 vdr init: irexec main process (2247) terminated with status 1 [19:23] if you look at this [19:24] i don't have a "normal" natty [19:25] but i can check that [19:25] i would rather debug whats happening [19:25] then trying empiric if it's my fault or ubuntus ;) [19:31] wait, I'm seeing things like "Apr 28 13:47:16 saeko init: plymouth-stop pre-start process (3747) terminated with status 1" too here [19:31] or maybe coming from the other side [19:32] if upstart is using dbus for handling the jobs, how can upstart shutdown dbus ? [19:32] upstart only uses dbus for communication with dbus clients [19:32] and it doesn't need the dbus daemon [19:33] for communication with upstart clients I mean [19:33] k , so initctl uses [19:33] things like initctl [19:33] something else [19:33] not dbus [19:34] dbus is a wire protocol, you can use dbus without a dbus daemon ;) [19:35] well on lucid i tried to send signals in init.d scripts and they got plain ignored back then [19:35] using initctl? [19:35] now it looks like runlevel [016] gets ignored [19:35] yes [19:36] which one gets ignored seems to be random/depending on time [19:36] that's weird [19:36] my requirement is to cleanly shutdown the daemon [19:37] nothing should kill it before it is finished [19:39] you have a pre-stop script for that? [19:40] no [19:40] only post start [19:42] default way to stop a job is to send SIGTERM, then after some time-out send SIGKILL, so if shutdown of your service takes longer, you'll need a pre-stop to handle this gracefully I think? [19:42] https://bugs.yavdr.com/projects/yavdr/repository/entry/trunk/base/yavdr-base/etc/init/vdr.conf [19:43] but pre-stop would wait until this is finished [19:43] before actually stopping it [19:45] pre-stop -> kill with SIGTERM vdr doesn't sound right to me [19:46] also it wouldnt help if something would kill it [19:46] from init.d [19:48] i can not believe that natty shutdown is so fucked up or handcrafted for the 5 known use cases [19:52] sry [20:05] I don't know what exactly goes wrong with your setup, but when using pre-stop for a job you can tell it to shut down and wait until it's ready, after that upstart will see no SIGTERM/SIGKILL is needed for that job anymore [20:06] but maybe you want to know what goes wrong first... [20:08] there are 2 issues [20:08] first is that runlevel is not coming or sendsigs is coming to fast [20:09] second is waiting for the daemon to finish [20:09] the pre-stop might be nice workaround [20:10] but worth nothing if rc and those sendsigs is killing the jobs [20:10] Hello, I have finally figured out how to handle a broken serial port and got console redirection working but I don't know where to put the fix. [20:11] on the other hand that should ignore everything which is handled by upstart [20:11] I have a ttyS0.conf in /etc/init that starts it for me, but before it starts it needs to be manually configured with setserial. [20:11] I was wondering where to put the setserial command. [20:11] create a setserial.conf [20:12] start on starting ttys0 [20:12] ttyS0 [20:12] Oh cool thanks. [20:13] https://bugs.yavdr.com/projects/yavdr/repository/entry/trunk/base/yavdr-base/etc/init/setserial-minimal.conf [20:13] Man upstart really has made GNU\Linux better in a big way for me. [20:14] Too complicated for me to follow. [20:14] its cool, but causing me headaches sometimes [20:14] Makes boot super fast. [20:15] if its just for you , just but the commands you need in the script section ;) [20:15] start on starting ttyS0 [20:15] will make it wait until that is finished [20:16] you might need to put task keyword also in [20:16] yes, otherwise it won't block properly [20:17] task makes it block until the job has completed the whole lifecycle [20:20] where does task go? [20:21] on its own line [20:21] anywhere tho [20:22] http://pastebin.com/AHPTn0GW [20:23] yes should work [20:23] rebeaut! [21:39] steffen_b: Thank you. That worked like a charm. [21:39] Because charms work well. [21:39] cool :) [21:39] Had an issue last night and couldn't console because previous admin couldn't figure it out.