[10:49] <bddy> Hi. 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?
[11:04] <AnrDaemon> bddy: If there's nothing suspicious in job definition file, it may have that functionality builtin. Check its documentation.
[11:05] <bddy> AnrDaemon: Yeah, I'm reading source code now. Unfortunately can't debug easily since this is init 1 pid
[11:05] <AnrDaemon> *facepalm*
[11:06] <bddy> AnrDaemon: What do you mean?
[11:06] <bddy> This is production server unfortunately and I can't kill it, neither reproduce :(
[11:06] <AnrDaemon> You have misbehaving application - and you are debugging init daemon?
[11:08] <bddy> AnrDaemon: chroot happens here: init forks, then it chroots, then execve()
[11:08] <AnrDaemon> What?
[11:08] <bddy> There is some chroot support in upstart - from the source code  Isee that it reads some xml stanza and gets "chroot" value from it
[11:09] <AnrDaemon> If you don't specify chroot in your job file, it won't do it.
[11:09] <AnrDaemon> And least of all it reads anything CML.
[11:09] <AnrDaemon> XML**
[11:09] <bddy> But it does it. :( see parse_job.c
[11:10] <bddy> ah, this is another stuff, you are right, this is not xml
[11:15] <bddy> hmm, 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:16] <AnrDaemon> Ok, first question: What OS version?
[11:51] <bddy> Sorry, was away, OS is Ubuntu 12.04 precise, upstart is 1.5
[11:52] <AnrDaemon> Then 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.)
[12:13] <bddy> Ok, it was solved by kill -TERM 1