/srv/irclogs.ubuntu.com/2014/07/18/#upstart.txt

elithrarLooking at the Upstart cookbook (updated 2014-07-17) can I assume that user jobs aren't able to log to /var/log/upstart/* (i.e. I'd need to manage my own logging solution)?08:52
xnoxelithrar: system jobs log to /var/log/upstart/*, user-session jobs log to $XDG_CACHE_HOME/upstart/ -> which typically is $HOME/.cache/upstart/08:56
xnoxelithrar: so default behaviour is the same for both: stdout & stderr is collected & rotated into logs somewhere.08:56
elithrarxnox: Alright, thanks. Having issues when using `set uid $USER` and `set gid $USER` where the job fails to start. No useful logging information from Upstart.08:59
xnoxelithrar: oh, well neither of those stanzas are correct -> job not recognised -> job not run =)09:01
xnoxelithrar: "setuid" and "setgid" are correct stanzas -> note no space.09:02
elithrarWhoops, I typo'ed them in IRC. Not in the config.09:02
xnoxelithrar: and that's a system level job, so log would be in /var/log/upstart/*09:02
xnoxelithrar: can you run $ init-checkconf /etc/init/that-job.conf ?09:02
elithrar"failed to ask Upstart" (although it still writes it to /tmp/user/$UID/init-checkconf...09:06
elithrarI asked all of this as the Upstart docs indicate "User jobs cannot currently take advantage of job logging. If a user job does specify console log, it is considered to have specified console none. Logging of user jobs is planned for the next release of Upstart."09:07
xnoxelithrar: ..... user jobs != user-session jobs != system job with setuid specified09:11
elithrarUpstart 1.5 here, so only user jobs.09:12
xnoxelithrar: we used to have (now deprecated) user jobs, where jobs are read from $HOME/.init/ and are run under the user jobs.09:12
elithrar(running 12.04 - I should have clarified. Only just noticed that 1.7 brought session jobs)09:12
xnoxelithrar: well, read $ man 5 init, I don't think 1.5 had "console log" at all)09:12
* xnox checks.09:13
elithrarIt does, but only for system jobs - so you're right / my first comment was on the mark09:13
elithrarlogged "Only applies to system jobs: if specified by user jobs, the job will be considered to have specified the value none."09:13
elithrar*log09:13
xnoxelithrar: yeap =(09:13
elithrarWelp, I'm rebuilding this box as a 14.04 LTS machine so I'll use session jobs and test in Vagrant. Thanks for helping diagnose though—more incentive to upgrade.09:14
xnoxelithrar: you should be able to use something like "log-output" or something like that. Or otherwise redirect stdout/stderr to a file you can write to as that user.09:15
xnoxelithrar: ha, log-output is ubiquity internal -> so no, can't use it.09:16
elithrarYeah, I was trying to avoid that since I then need to write a logrotate config. Which isn't a challenge, but it's just less incentive to migrate from supervisord. I prefer to use the "included tools" but older versions of Upstart are a bit limiting09:16
six86Hello. I have a problem with upstart. I want to start a software when two can interfaces are available. But "start on (net-device-up IFACE=can0 and net-device-up IFACE=can1)13:39
six86" does not work. Am I doing something wrong here?!13:39
six86anyone?13:48
=== JanC_ is now known as JanC
sean_abbottSo as I understand it, just putting the conf file in /etc/init should let upstart know about the job15:49
sean_abbottSo, then, I guess if it still claims to NOT know about my job, there's a problem with it.15:49
sean_abbottis that correct?15:49
sean_abbotthere's what I dn't understand.  Your debug guide says if you get unknown job you have a configuration issue.16:04
sean_abbottuse init-checkconf16:04
sean_abbottbut init-checkconf doesn't work on servers16:04
sean_abbottand ya'll don't respond at all.16:04
sean_abbottok, was finally able to run init-checkconf from my desktop and that got me there16:07
sean_abbott\quit16:07

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!