[07:28] <vanguarde9> Hello does anybody have experience with upstart and red hat based distros ? Is it posible to start automaticaly upstart service after start of systemV service , without addig any code (etc. initctl emit sometnig) into systemV script ?
[07:29] <vanguarde9> I mean for example Centos as Red Hat based linux distro
[15:51] <jgornick> Hey guys, I'm running Ubuntu 12.04 and for some reason, I can't get initctl to recognize my job conf file I've created in /etc/init. Thoughts?
[15:52] <xnox> jgornick:  init-checkconf /etc/init/myjob.conf ?
[15:53] <xnox> does that say anything useful?
[15:53] <jgornick> xnox: ERROR: failed to ask Upstart to check conf file
[15:54] <jgornick> xnox: sudo?
[15:54] <jgornick> Nope :)
[15:55] <jodh> jgornick: are you running at the console? If so, you'll need to start a dbus-daemon for init-checkconf to work.
[15:56] <jodh> jgornick: dbus autostart changed its behaviour. newer init-checkconf versions handle this.
[15:56] <jgornick> jodh: Yes, it's a headless server. How do I start the dbus-daemon?
[15:56] <jgornick> jodh: To be specific it's the 12.04 Amazone AMI.
[15:56] <jgornick> s/Amazone/Amazon
[15:56] <jodh> jgornick:  eval `dbus-launch --sh-syntax`
[15:57] <jgornick> The program 'dbus-launch' is currently not installed.  You can install it by typing: sudo apt-get install dbus-x11
[15:57] <jgornick> Shall I do that?
[15:57] <jodh> jgornick: if you are able to. if not, just pastebin your job so we can see it
[15:57] <jodh> jgornick: ... or copy the job to a desktop system and run init-checkconf there of course :)
[15:58] <jgornick> jodh: I'll get a copy of the conf file.
[16:09] <jgornick> jodh: https://gist.github.com/jgornick/32e8e17c75d64cbacc37
[16:13] <jodh> jgornick: the job is valid. I wonder if /etc is on some sort of overlay filesystem maybe?
[16:15] <jgornick> jodh: I can't imagine. It is the basic Ubuntu 12.04 Server instance offered from Amazon with official support from Canonical.
[16:16] <jodh> jgornick: 'mount|grep overlay' ?
[16:16] <jgornick> Nothing echo'd/
[16:21] <jodh> jgornick: hmm. when you say initctl does not recognise the job, what do you mean exactly?
[16:22] <jgornick> jodh: sudo initctl status bulkqr initctl: Unknown job: bulkqr
[16:22] <jgornick> jodh: That's after I do a sudo initctl reload-configuration
[16:22] <jgornick> Just to make sure it's loading in the conf file.
[16:24] <jodh> jgornick: try "sudo initctl log-priority debug; touch /etc/init/yourjob.conf" and look at dmesg / /var/log/syslog to see what upstart messages you get relating to that job.
[16:25] <jodh> jgornick: that'd be "sudo touch" :)
[16:26] <jgornick> jodh: We're getting somewhere: https://gist.github.com/jgornick/32e8e17c75d64cbacc37#file-gistfile2-txt
[16:34] <jodh> jgornick: odd. it's complaining about line 24 and the file only has 23 lines. Have you got some stray extended characters in that job file maybe? \r rather than \n? if not, try commenting out each stanza/block and seeing where the problem lies.
[16:37] <jgornick> jodh: That was it.
[16:37] <jgornick> jodh: Some bad character or whatever. Probably a copy paste through terminal that made it happen.
[16:38] <jgornick> jodh: Thanks for helping debug that.