[buildd-tools-devel] buildd fails to start

[Roger Leigh]

On Fri, May 17, 2013 at 10:49:47PM +0100, peter green wrote:
> I'm running a debian derivative called raspbian and i'm trying to
> setup a new autobuilding system for raspbian jessie. The autobuilder
> i'm setting up is a boundary devices nitrogen6x with debian wheezy
> armhf as the "outer OS" and raspbian jessie in the build chroot.
> 
> I'm trying to use the packaged version of buildd from wheezy,
> unfortunately it silently fails to start.
> 
> Trying to start it under strace gave the following near the end.
> 
> stat64("'/etc/buildd/buildd.conf'", 0xc210d0) = -1 ENOENT (No such
> file or directory)
> stat64("'/home/buildd/.builddrc'", 0xc210d0) = -1 ENOENT (No such
> file or directory)
> open("/home/buildd/daemon.log",
> O_WRONLY|O_CREAT|O_APPEND|O_LARGEFILE, 0640) = 3
> _llseek(3, 0, [1847], SEEK_END)         = 0
> 
> Which seems very strange to me, where could those extra quotes
> possiblly be coming from?

I can reproduce this.  However... it's not in the main startup
stage:

stat("/etc/buildd/buildd.conf", {st_mode=S_IFREG|0644, st_size=8183, ...}) = 0
stat("/etc/buildd/buildd.conf", {st_mode=S_IFREG|0644, st_size=8183, ...}) = 0
stat("/home/rleigh/.builddrc", {st_mode=S_IFREG|0644, st_size=4917, ...}) = 0
stat("/home/rleigh/.builddrc", {st_mode=S_IFREG|0644, st_size=4917, ...}) = 0
stat("/etc/buildd/buildd.conf", {st_mode=S_IFREG|0644, st_size=8183, ...}) = 0
stat("/home/rleigh/.builddrc", {st_mode=S_IFREG|0644, st_size=4917, ...}) = 0
stat("'/etc/buildd/buildd.conf'", 0x118e138) = -1 ENOENT (No such file or directory)
stat("'/home/rleigh/.builddrc'", 0x118e138) = -1 ENOENT (No such file or directory)
stat("/usr/bin/buildd", {st_mode=S_IFREG|0755, st_size=2394, ...}) = 0

The only place I can see single quoting these filenames is in
Sbuild::ConfBase::read(), but that's for use inside an eval'd
bit of code, and I've confirmed that this works fine (it's used
by both sbuild and buildd to read their configs, so we'd know
if that was broken quite quickly).

We will certainly need to hunt down where this is done, but do note
that it's effectively harmless due to having already read in the
configuration earlier.

The actual cause of the failure isn't shown above; we successfully
open the log and seek to the end (which is 0 since it's empty).
Is there anything in the daemon.log?


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux    http://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-    GPG Public Key      F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800