[08:52] <elithrar> Looking 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:56] <xnox> elithrar: system jobs log to /var/log/upstart/*, user-session jobs log to $XDG_CACHE_HOME/upstart/ -> which typically is $HOME/.cache/upstart/
[08:56] <xnox> elithrar: so default behaviour is the same for both: stdout & stderr is collected & rotated into logs somewhere.
[08:59] <elithrar> xnox: 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.
[09:01] <xnox> elithrar: oh, well neither of those stanzas are correct -> job not recognised -> job not run =)
[09:02] <xnox> elithrar: "setuid" and "setgid" are correct stanzas -> note no space.
[09:02] <elithrar> Whoops, I typo'ed them in IRC. Not in the config.
[09:02] <xnox> elithrar: and that's a system level job, so log would be in /var/log/upstart/*
[09:02] <xnox> elithrar: can you run $ init-checkconf /etc/init/that-job.conf ?
[09:06] <elithrar> "failed to ask Upstart" (although it still writes it to /tmp/user/$UID/init-checkconf...
[09:07] <elithrar> I 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:11] <xnox> elithrar: ..... user jobs != user-session jobs != system job with setuid specified
[09:12] <elithrar> Upstart 1.5 here, so only user jobs.
[09:12] <xnox> elithrar: 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] <xnox> elithrar: well, read $ man 5 init, I don't think 1.5 had "console log" at all)
[09:13]  * xnox checks.
[09:13] <elithrar> It does, but only for system jobs - so you're right / my first comment was on the mark
[09:13] <elithrar> logged "Only applies to system jobs: if specified by user jobs, the job will be considered to have specified the value none."
[09:13] <elithrar> *log
[09:13] <xnox> elithrar: yeap =(
[09:14] <elithrar> Welp, 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:15] <xnox> elithrar: 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:16] <xnox> elithrar: ha, log-output is ubiquity internal -> so no, can't use it.
[09:16] <elithrar> Yeah, 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 limiting
[13:39] <six86> Hello. 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:48] <six86> anyone?
=== JanC_ is now known as JanC
[15:49] <sean_abbott> So as I understand it, just putting the conf file in /etc/init should let upstart know about the job
[15:49] <sean_abbott> So, then, I guess if it still claims to NOT know about my job, there's a problem with it.
[15:49] <sean_abbott> is that correct?
[16:04] <sean_abbott> here's what I dn't understand.  Your debug guide says if you get unknown job you have a configuration issue.
[16:04] <sean_abbott> use init-checkconf
[16:04] <sean_abbott> but init-checkconf doesn't work on servers
[16:04] <sean_abbott> and ya'll don't respond at all.
[16:07] <sean_abbott> ok, was finally able to run init-checkconf from my desktop and that got me there
[16:07] <sean_abbott> \quit