| mlindsay | So registering a new session job appears to require more than just the presence of a file in $HOME/.config/upstart/myupstartjob.conf | 16:48 |
|---|---|---|
| mlindsay | True? | 16:48 |
| mlindsay | I’m running upstart 1.12.1 on trusty 14.04 | 16:49 |
| jodh | mlindsay: no - that is sufficient. Is your job valid ('init-checkconf $HOME/.config/upstart/myupstartjob.conf')? | 16:49 |
| mlindsay | s3-router.conf: syntax ok | 16:50 |
| mlindsay | the reason I think it’s not running is ps aux | grep js returns nothing | 16:51 |
| mlindsay | and no corrosponding log file in /var/log/upstart | 16:51 |
| mlindsay | it’s all put together under a brand new user | 16:51 |
| mlindsay | so I created the .config/upstart dirs myself | 16:52 |
| jodh | mlindsay: /var/log/upstart is for *system* jobs, not session-level jobs. For those, look in $HOME/.cache/upstart/myupstarjob.log. | 16:52 |
| jodh | mlindsay: .config/upstart must exist before the session init starts (inotify limitation). | 16:52 |
| jodh | mlindsay: if that isn't the case, you should be able to run 'start re-exec' (non-root) to have the job picked up. | 16:53 |
| jodh | mlindsay: (and avoid having to log out). | 16:53 |
| mlindsay | jodh: do I have to create the .cache dir? | 16:53 |
| mlindsay | jodh: thanks for helping out, and sorry for any stupid questions, but when I ‘start re-exec’ I get start: Unknown job: re-exec | 17:13 |
| mlindsay | on a more general note, I’m setting this up as a session job for security reasons only, Is that appropriate? If not I’m working too hard | 17:22 |
| jodh | mlindsay: yes, you need to create the .cache dir if you want job output to be logged (it's not an error if it doesn't exist, but upstart will discard all job output). | 18:01 |
| jodh | mlindsay: are you running 'start re-exec' as a non-root user? | 18:01 |
| mlindsay | yes | 18:01 |
| mlindsay | nodejs-runner@ip-###-###-###-###:/home/ubuntu$ start re-exec | 18:03 |
| mlindsay | start: Unknown job: re-exec | 18:03 |
| mlindsay | funny thing is, with ~/.config/upstart/s3-router.conf present, service s3-router status says s3-router: unrecognized service | 18:08 |
| === mlindsay_ is now known as mlindsay | ||
| === jhford_ is now known as jhford | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!