/srv/irclogs.ubuntu.com/2016/06/17/#upstart.txt

=== JanC is now known as Guest67075
=== JanC_ is now known as JanC
=== PaulePan1er is now known as PaulePanter
bddyHi. One of my /etc/init/somename.conf daemons keeps starting in a chroot for some reason. Is it possible to somehow understand - from where does it take the chroot path and how to make it not chroot?10:49
AnrDaemonbddy: If there's nothing suspicious in job definition file, it may have that functionality builtin. Check its documentation.11:04
bddyAnrDaemon: Yeah, I'm reading source code now. Unfortunately can't debug easily since this is init 1 pid11:05
AnrDaemon*facepalm*11:05
bddyAnrDaemon: What do you mean?11:06
bddyThis is production server unfortunately and I can't kill it, neither reproduce :(11:06
AnrDaemonYou have misbehaving application - and you are debugging init daemon?11:06
bddyAnrDaemon: chroot happens here: init forks, then it chroots, then execve()11:08
AnrDaemonWhat?11:08
bddyThere is some chroot support in upstart - from the source code  Isee that it reads some xml stanza and gets "chroot" value from it11:08
AnrDaemonIf you don't specify chroot in your job file, it won't do it.11:09
AnrDaemonAnd least of all it reads anything CML.11:09
AnrDaemonXML**11:09
bddyBut it does it. :( see parse_job.c11:09
bddyah, this is another stuff, you are right, this is not xml11:10
bddyhmm, for some reason when I do initctl reload-configuration, it goes to /home/name/chroot/etc/init/somename.conf and reads configuration file from there.11:15
AnrDaemonOk, first question: What OS version?11:16
bddySorry, was away, OS is Ubuntu 12.04 precise, upstart is 1.511:51
AnrDaemonThen what you did to it? I have same OS, and nothing extraordinary happens to it. Whatever I try. (And I've tried many weird things in the past two weeks.)11:52
bddyOk, it was solved by kill -TERM 112:13

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