crankharderI dont think .override files would work since there may not be an original service to override00:01
gQuigsis it planned to recommend removing the symlinks from /etc/init.d/  at some point?15:05
gQuigsIn 12.04,  the networking upstart service is almost nothing. while the init.d job is real,   then in raring it's a symlink to the upstart job.  then in saucy it appears to be back as a real init.d job...15:06
gQuigsbasically, I've seen a number of users confused by how to do simple stuff like restarting networking..15:09
ajpgetting weird message: initctl: Rejected send message, 1 matched rules; type="method_call", sender=":1.140" (uid=1000 pid=11332 comm="initctl start upstartPDF ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init")15:40
ajpwhen I try to run $: initctl start upstartPDF15:41
ajpcan anyone tell me why? script here: http://pastebin.com/uiXkd90115:42
jodhajp: did you try Google? http://upstart.ubuntu.com/cookbook/#strange-error-when-running-start-stop-restart-or-initctl-emit15:43
jodhajp: you need to be root.15:43
ajpoh duh, thanks i'm going to retry15:43
jodhajp: also, do you really need to run that job as root? if so, why does it live in a home directory? If it really must, you'll probably have to set 'env HOME=...' in the job. Better still, run it as a session job if you can.15:43
ajpthe upstart script calls a bash script in the home folder that monitors a samba shared folder and converts large PDFs to small PDFS15:45
ajp it's on a headless server that hosts our file share and scans from the printers15:46
ajpnot sure what you mean by session job15:46
ajpit was working at one point but now it doesn't work by default, not sure what's going on15:47
jodhajp: if you are running Ubuntu, you'll need to be using Raring or newer to make use of Session Jobs: http://upstart.ubuntu.com/cookbook/#session-jobs15:49
jodhajp: I'm just saying that running a program as root from a home directory is unusual. You may need to set variables (like $HOME) to make it work if that script calls other scripts for user matthew.15:50
ajpthere really is only one user, matthew. 15:52
ajphow am I running it as root? I don't see the line you are talking about "exec"?15:52
jodhajp: where does the .conf file live?15:53
xnoxgQuigs: in debian jessie and ubuntu saucy, indeed symlinks to upstart-jobs are no longer required. Instead update-rc.d and friends were updated to cope with upstart jobs.15:54
jodhajp: right, so you are running the job as root.15:54
ajpi see. 15:54
jodhajp: so to repeat, please be sure you need to run that job as the root user!15:55
gQuigsxnox: oh ok, so should I report bugs against packages that still have them?  (obviously low priority bugs..)15:55
jodhajp: if you don't and you can't use a Session Job, read http://upstart.ubuntu.com/cookbook/#run-a-job-as-a-different-user15:55
xnoxgQuigs: no bugs need to be reported.15:57
xnoxgQuigs: package that migrate away from installing symlinks, remove them as of when they do them.15:57
gQuigsxnox: didn't quite parse that last line...  if a package doesn't require the symlinks isn't that a bug?15:59
gQuigsxnox: or is there some other compat. that needs to be added first?16:00
xnoxgQuigs: that's not what i said.16:00
xnoxgQuigs: it's ok for symlinks to be there, but they do need trasition before symlinks can be removed. See https://wiki.ubuntu.com/UpstartCompatibleInitScripts and the matching thread started by slangasek on ubuntu-devel for further details.16:01
gQuigsxnox: oh.. so the symlinks are being replaced by sysV jobs.. that error out if run on a system with upstart as init... 16:18
gQuigsxnox: thanks that link / mailing list was very helpful16:18
xnoxgQuigs: kind of reverse, symlinks used to override sysv jobs, and now we are stopping to do so.16:21
gQuigsxnox: right, but those new sysv jobs better be set to Error out.. 16:24
gQuigsor we will really really confuse users.. 16:27
xnoxgQuigs: only if the user runs the job manually, all the tools were modified to run upstart job first (if exist) and not call sysv init job at all.....16:34
gQuigsxnox: AFAIK the only way in 12.04 to stop/start networking is via /etc/init.d/networking16:41
gQuigsxnox: the upstart command appears to do nothing at all, so this is a big change for users who do that16:41
xnoxgQuigs: you need to specify instance.16:42
gQuigsxnox: "networking" upstart job is always in stop/waiting on 12.04...  what do you mean about specifying an instance?16:50
xnoxgQuigs: sudo initctl list | grep network16:53
xnoxgQuigs: on saucy, networking is "start/running" and there are a bunch of other jobs "network-interface" with particular instances specified in (), e.g. (eth0)16:54
gQuigsxnox: yes on 12.04 I definitely get networking stop/waiting16:58
gQuigsbut I do see the other interfaces..  which via upstart you would have to go one by one?16:58
xnoxnot sure. maybe things have changed in ubuntu since 12.04.16:58
xnoxi mostly code upstart itself, and i didn't look into networking jobs much.16:59
gQuigsxnox: oh ok, thanks for your help!17:03
ajpjodh: it was working before for months and it just stopped working one day. any ideas why?17:21
ajpjodh: the bash script works fine by itself but when I try to integrate it into upstart, It doesn't do it's job17:45
jodhajp: http://upstart.ubuntu.com/cookbook/#checking-how-a-service-might-react-when-run-as-a-job, http://upstart.ubuntu.com/cookbook/#determining-why-your-service-fails-to-start, http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in18:03
ajpjodh: well I just read all that and I still don't understand why it would work for months then all of the sudden it doesn't work at all?18:18

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