| afournier | morning! | 09:18 |
|---|---|---|
| afournier | is there a reason why upstart 1.6.1 installs upstart-socket-bridge.conf but does not install upstart-udev-bridge.conf | 09:22 |
| afournier | btw upstart-udev-bridge is not compiled/installed either, could be a udev dependency problem ? | 09:23 |
| afournier | that was it, too bad the configure is not more verbose when it cannot find udev | 09:26 |
| errordeveloper | hi | 11:07 |
| errordeveloper | hava used an infinite task as a place holder for a multi-instance service | 11:08 |
| errordeveloper | have 4 conf files svc.conf, svc-instance.conf, svc-stop-task.conf and svc-start-task.conf | 11:08 |
| errordeveloper | so start and stop tasks are doing a loop around starting and stoping service instance with PORT being the instance variable | 11:09 |
| errordeveloper | all works good and I can `/sbin/stop svc` and `/sbin/start svc`, but `/sbin/restart svc` doesn't affect anything | 11:10 |
| errordeveloper | the stop and start task use `start on stopped svc` and `start on started svc` respectively | 11:11 |
| errordeveloper | i'm happy to add svc-restart-task.conf, but don't know what to put in it ... | 11:11 |
| xnox | errordeveloper: http://upstart.ubuntu.com/cookbook/#restarting-jobs-with-complex-conditions ? | 11:21 |
| errordeveloper | nevermind, I fixed it by using `start on {stopping,starting} svc` in the svc-{start,stop}-task.conf | 11:33 |
| errordeveloper | so on restart of an infinite task you don't seem to get stopped->started, but you do get stopping->starting | 11:35 |
| errordeveloper | :) | 11:35 |
| === maco__ is now known as maco | ||
| vekexasia | hello all | 15:50 |
| vekexasia | I'm trying to undestand why i can stop/start my instance | 15:50 |
| vekexasia | but not restart | 15:50 |
| vekexasia | someone that could help me ' | 15:53 |
| vekexasia | noone? | 16:10 |
| xnox | vekexasia: did you read the cookbook about restart? can you please pastebin your job? | 16:21 |
| vekexasia | i read it not much about restart section is "for me" | 16:22 |
| vekexasia | http://paste.ubuntu.com/1452670/ | 16:23 |
| vekexasia | upstart start nodejs-instance FOLDERNAME="Example" | 16:24 |
| vekexasia | triggers pre-start and post-start | 16:24 |
| vekexasia | "stop" triggers pre-stop and post-stop | 16:24 |
| vekexasia | "restart" triggers only pre-stop and does not stop the instance at all | 16:24 |
| vekexasia | it's not a big deal i cannot restart my instances but i wanted to know if there's something i can do. | 16:25 |
| vekexasia | any idea xnox ? | 16:27 |
| vekexasia | ping xnox :) | 16:36 |
| xnox | vekexasia: change log priority to debug, start/stop your instance and then restart & compare the events / transitions. | 16:37 |
| xnox | http://upstart.ubuntu.com/cookbook/#change-the-log-priority | 16:37 |
| vekexasia | ok | 16:37 |
| xnox | vekexasia: i am not sure if post-stop is suppose to be run or not when doing "restart" | 16:38 |
| vekexasia | xnox I thought that too. Problem is instance is not getting stopped :( | 16:38 |
| vekexasia | sorry for the dumb question but /var/log/syslog is not reporting anything | 16:40 |
| vekexasia | am I looking in the wrong place? | 16:40 |
| xnox | should be correct place. | 16:41 |
| vekexasia | nothing is printed in there | 16:41 |
| vekexasia | neither with initctl log-priority debug | 16:41 |
| xnox | vekexasia: does restart work correctly without respawn? | 16:41 |
| vekexasia | well should i get something with start/stop in the log ? | 16:41 |
| vekexasia | cause even with start/stop i do not get anything | 16:42 |
| xnox | have you check dmesg / daemon.log as well? | 16:44 |
| vekexasia | nothing on dmesg | 16:44 |
| vekexasia | daemon.log | 16:44 |
| vekexasia | does not even exist | 16:44 |
| vekexasia | and no, it does not work even withouth respawn | 16:45 |
| vekexasia | xnox ? | 18:39 |
| vekexasia | still no luck | 18:39 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!