[10:42] hi all, I'm getting into upstart for the first time, and I wonder if I've missed something… I'm trying to use upstart to keep monit running [12:02] hi all, I'm getting into upstart for the first time, and I wonder if I've missed something… I'm trying to use upstart to keep monit running (re-post, since I was D/C'ed) [12:46] codebeaker: what do you think you're missing? [12:46] if I kill monit, upstart doesn't bring it back [12:46] which I gathered was the point of upstart [12:46] ( in addition to actually starting it in the firstplace) [12:46] did you put the word 'respawn' in your job file? [12:47] no respawning isn't the only point of upstart.. its mostly just to be feature compatible w/ sysvinit [12:47] Its just a little smarter about it than sysvinit. :) [12:47] ok, I'll check - also what is the /correct/ place for upstart configs? [12:47] on my ubuntu 10.4 system they appear to live in /etc/init/ [12:47] but I've seen lots of talk online about using /etc/event.d/ [12:48] they must be in /etc/init since Ubuntu 9.10 [12:48] ok, good to know - thanks :) [12:48] *bow* [12:49] You may want to submit your monit job as a feature-request bug against the package if it works out for you. [12:50] not sure, it's 3 lines of code :) [12:50] (well, four now :)) [12:53] SpamapS: what's your personal opinion on Monit's place in a modern hosting env [12:53] I'm basically using monit to keep my services up, because I know it well enough [12:55] Its quite suited for that, especially since it is capable of deeper monitoring than upstart's "is the process alive" [13:02] ok, perfect… so upstart to keep the system running, and monit to keep things working at the application layer [13:04] Yeah [13:12] does anyone know if upstart 1.0 ist compatible wrt utmp handling when i use agetty? [13:12] the teminal sessions aren't decremented in issue output anymore since i upgraded to 1.0 [13:15] i'll try to switch to mingetty today to check it isn't an incompatibility with util-linux's agetty as mingetty was mentioned in some changelog... [13:15] doesn't login handle utmp maintenance? [13:17] looks like it doesn't if i read the changes that went in from plautrbach correctly... [13:18] mybe i have a wrong tty.conf in /etc/init [13:18] ahh I'm looking now.. ok.. utmp is indeed touched by init now [13:18] I say now like I know it didn't before.. maybe it did before.. :p [13:19] the problem was that issue incremented the open tty session counters but doesnt decremented it after the loginsession was closed and upstart respawned the getty ... [13:20] this bug was in upstart from the start i think [13:20] don't know how sysv handled it [13:20] wraiden: can you paste somewhere 'utmpdump /var/run/utmp' ? [13:20] right looks like now if a job process terminates upstart looks in utmp and fixes it [13:20] wraiden: afaik it should work regardless of used *getty [13:21] hello :) i'll open a session to the box an paste the things... [13:24] http://pastebin.com/LfDLA8hR [13:25] cant look at the issue output right now as i'm not in front of the box [13:33] this looks ok, what is concretely your problem? [13:35] if i login an a local tty the issue displays the logged in users ok but if i logout the logged in users stay the same and doesn't get decremented [13:36] this behavor war fixed in the first round of patches that you attached to the bugreport ... [13:37] i tested them and used them as patches against 0.6 but with the upgrade to version 1.0 i went back to the buggy behavior [13:38] i'll post another utmp dunp when i have access to the box again around 18:30 CET [13:39] in 1.0 is almost same patch [13:40] and utmp table says that there is 2 correctly restarted local tty session, 1 closed remote, and 1 active remote session [13:41] thats right [13:41] command 'w' should show one logged user [13:41] i rebooted the box [13:41] kernel upgrade... [13:41] the wrong behavior was befor the reboot [13:42] i'll repro the wron output and post an updated dump [13:42] should i mail it or crate a bug report? [13:43] mail to mailling list or bug report are fine, or you can first try to ping me here [13:43] k, will look here first [13:44] anyway, thanks for your work about utmp handling, this one bugged me a long time :) [13:44] i've just setup my fedora rawhide box to use aggety and it works ok [13:44] exec /sbin/agetty -I '\033(K' tty1 38400 [13:44] is what i use [13:44] maybe it's related to that [13:46] I use only /sbin/agetty /dev/tty6 38400 but -I should not affects that [13:48] i'll repro the problem tonight and post the details along the dump... [22:34] hello! [22:34] i'm binding slapd to an ip alias and it seems that aliases come up late on boot which causes slapd fail to start... can i start networking "syncronously" or something? [22:44] no, but you can have slapd start after networking [22:47] i think that's how it's configured... [22:47] or should i create /etc/init/slapd.conf for that? [22:48] you would need an /etc/init/slapd.conf or something in Upstart that starts slapd [22:48] i don't have that right now [22:48] just learning upstart [22:49] thought it was related to insserv [22:55] hmm [22:56] so slapd is not an upstart job right now [22:56] which means it's handled from /etc/init/rc.conf, right? [22:56] no, /etc/init.d/slapd [22:57] true :) i misspoke [22:57] atpa8a: only indirectly via /etc/init/rc.conf [22:57] right [22:57] that's what i meant [22:58] can i just add something like start on (net-device-up...) to /etc/init/rc.conf to make sure the networking is up before anything else? [23:01] or change /etc/init/rc-sysinit.conf from 'start on filesystem and net-device-up IFACE=lo' to 'start on filesystem and net-device-up' [23:03] basically i want *all* of the network up before slapd starts [23:14] that didn't help [23:15] any hints?