=== rm_work is now known as rm_work|away | ||
=== rm_work|away is now known as rm_work | ||
=== rm_work is now known as rm_work|away | ||
=== rm_work|away is now known as rm_work | ||
=== rm_work is now known as rm_work|away | ||
=== rm_work|away is now known as rm_work | ||
=== rm_work is now known as rm_work|away | ||
=== rm_work|away is now known as rm_work | ||
Mariano9 | guys, anyone willing to check out my upstart script and see why it's respawning for ever? https://gist.github.com/Mariano-gon/8941403 | 18:52 |
---|---|---|
Mariano9 | I think this is a env issue, as If I cd into newrelic plugin directory and run bundle exec .. it'll start without any issues; but it won't from anywhere else | 18:52 |
Mariano9 | I tried with env and export stanzas, nothing seems to work | 18:53 |
ion | Do you see its output in /var/log/upstart? | 18:57 |
Mariano9 | in /var/log/messages it's mine. https://gist.github.com/Mariano-gon/8941660 | 19:01 |
Mariano9 | and this same will repeat ten times and then stop | 19:02 |
ion | But do you see the *output* of the process in /var/log/upstart? | 19:04 |
Mariano9 | there's no upstart folder in /var/log.. | 19:04 |
ion | Ok. In that case you can add manual logging to the job. | 19:17 |
ion | script | 19:17 |
ion | exec >>/tmp/blah.out 2>&1 | 19:18 |
ion | set -x | 19:18 |
ion | exec sudo -u root … | 19:18 |
ion | end script | 19:18 |
Mariano9 | but doesn't the first exec (or the second) shut off the other one? | 19:35 |
smallfoot- | Debian went with systemd | 20:05 |
smallfoot- | they could have went with upstart | 20:05 |
smallfoot- | and probably would have if it weren't for upstart being under CLA | 20:05 |
smallfoot- | you guys lost Debian thanks to your CLA | 20:06 |
smallfoot- | now if there were anyone using upstart they will migrate to systemd | 20:06 |
smallfoot- | if there was anyone who considered upstart, they wont anymore, now everyone will be adopting systemd | 20:06 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!