| rjr | I'm running upstart 1.5 on Ubuntu Precise. I created a job in /etc/init. It showed up in initctl show-config and things seemed to be working ok for a few minutes, and then I noticed it was no longer picking up changes (e.g. no matter what I set 'start on' and 'stop on' to, initctl show-config still used the old values) | 00:51 |
|---|---|---|
| rjr | I've removed the files from /etc/init and they still show up in show-config (and when I query dbus directly with com.ubuntu.Upstart0_6.GetAllJobs) | 00:52 |
| rjr | or rather, one of the files I removed no longer shows up, but the other one still does. | 00:52 |
| rjr | I've added and removed other files just to verify the inotify job is still picking things up. It just won't get rid of this one entry. | 00:53 |
| rjr | I suspect it had to do with setting the 'expect fork/daemon' setting wrong as I've seen a few other reports of similar issues | 00:54 |
| rjr | got it. It was https://bugs.launchpad.net/upstart/+bug/406397 I resolved my issue by spawning a process with the right pid and letting upstart reap it. | 01:04 |
| rjr | Always fun when someone reinvents the wheel and makes it square instead. | 01:06 |
| checkers | hi, I'd like to run mkfs on a particular device before local filesystems are mounted. Is the Right Way to implement this as an upstart job that has 'start on starting local-filesystems'? | 05:30 |
| checkers | I feel like this one-time command is a bit of a weird fit for a job-based system, is there some 'just run this script' thing I can do without needing to modify OS dist files? | 05:31 |
| om26er | Hi! I need help with this upstart job http://bazaar.launchpad.net/~phablet-team/address-book-service/trunk/view/head:/upstart/address-book-service.conf | 14:57 |
| om26er | initctl seems to not be able to stop the service on my phone, it does print that the service stopped but it actually keeps running | 14:57 |
| jodh | om26er: what does 'status address-book-service' show? maybe the binary is forking and therefore not being tracked correctly by upstart. Anything in ~/.cache/upstart/address-book-service.log? | 14:58 |
| xnox | om26er: which of the two upstarts are you stopping it with? and which upstart is the job running on? | 14:59 |
| xnox | om26er: compare $ adb shell status address-book-service | 14:59 |
| xnox | om26er: with $ adp shell sudo -u phablet -i status address-book-service | 14:59 |
| om26er | xnox, the one as phablet user reports the other just says 'Unknown job' | 15:03 |
| xnox | om26er: so, try stopping with e.g. $ adb shell sudo -u phablet -i stop address-book-service | 15:04 |
| xnox | om26er: if it keeps running, then either the job<->daemon are buggy. | 15:04 |
| xnox | om26er: or the service is otherwise activated e.g. direct invocation or like via dbus | 15:05 |
| om26er | xnox, yeah it says 'address-book-service stop/waiting' but the service keeps running with the same pid | 15:05 |
| om26er | also address-book-service.log doesn't have anything | 15:06 |
| om26er | jodh, ^ | 15:06 |
| om26er | xnox, on desktop where upstart job is not used, the service does get started when its dbus interface it poked | 15:07 |
| xnox | om26er: probably the job never started via upstart... | 15:08 |
| xnox | om26er: try this -> kill the address-book-service, check that none are running. | 15:08 |
| om26er | xnox, it respawns instantly | 15:08 |
| xnox | om26er: start via upstart and stop via upstart, and verify that service is running and stops. | 15:08 |
| xnox | om26er: kill it harder =) e.g. kill -9 | 15:09 |
| xnox | om26er: and e.g. remove the dbus activation service file, to prevent things from spawning it. | 15:10 |
| om26er | xnox, kill -9 and -3 respawns, I can try removing the dbus service file to check | 15:10 |
| om26er | since the service only supports one instance, initctl thinks it was able to start the service after I stop and start it but in reality only the old instance keeps running | 15:11 |
| om26er | xnox, yes, deleting the dbus activation service file did the trick | 15:16 |
| om26er | now start/stop works with upstart | 15:17 |
| xnox | om26er: well you need to choose one or the other. | 15:17 |
| xnox | om26er: a few services that tedg wrote do "$ start job" in their dbus activation file. | 15:17 |
| xnox | om26er: such that it's always run under upstart. | 15:17 |
| xnox | om26er: when ubuntu transitions to systemd that race will be gone, as dbus activated services are running as systemd units - just like the rest of the jobs. | 15:18 |
| om26er | xnox, ok, I'll take this to the address-book-service developer and figure out a solution with him | 15:18 |
| om26er | xnox, is there any example project where tedg did that ? | 15:18 |
| xnox | om26er: i can't remember of the top of my head. just browse dbus activation files on the phone and look those that launch wrappers that ultimately call $ start job | 15:19 |
| om26er | xnox, alright, thanks | 15:21 |
| === JanC_ is now known as JanC | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!