[buildd-tools-devel] Bug#684607: Bug#684607: Chroot setup failed: stage=setup-start

Roger Leigh rleigh at codelibre.net
Sat Aug 11 19:00:07 UTC 2012


On Sat, Aug 11, 2012 at 08:23:28PM +0200, Christoph Egger wrote:
>   Nothing changed in config for almost a year, schroot fails to set up
> a chroot now. Log attached.

> D(2): run_parts: executing 50chrootname, setup-start, ok
> I: Executing ‘50chrootname setup-start ok’
> I: 50chrootname: Setting chroot name to unstable-amd64-sbuild
> D(2): run_parts: 50chrootname failed with status 1
> D(3): Chroot setup scripts, exec scripts or session failed

OK, so it's the 50chrootname script failing here.  The only change
to that script in the last year has been the addition of a single
line:

  d04e32dd etc/setup.d/50chrootname       (Roger Leigh 2012-04-03 23:29:40 +0100 24) . "$SETUP_DATA_DIR/common-config"

  http://anonscm.debian.org/gitweb/?p=buildd-tools/schroot.git;a=commitdiff;h=d04e32dd3cc39ea641fc2848957292fe94751925

However, as you can see by looking at the diff, that line was added
to all the other scripts as well, and you should have the script here:

  % ls /usr/share/schroot/setup 
  common-config  common-data  common-functions

Since you get the "Setting chroot name..." message, the only other line
in the file which can fail is:

  echo "${CHROOT_NAME}" > "${CHROOT_PATH}/etc/debian_chroot"

Which would imply that this failed.  It doesn't give an error why--did
your debug log also capture stderr?  If not, a copy with stderr included
would be useful here.  All the variables like CHROOT_NAME and
CHROOT_PATH look correct.  SETUP_DATA_DIR is likewise correct for
sourcing the shell scripts at the top.  Is /etc/debian_chroot writable
by the setup script?  / and /etc must be writable by root.

So it would be very useful to know
- the stderr (e.g. run with script or 2>&1)
- if you can check the filesystem permissions or anything else that
  might interfere with writing (e.g. free blocks/inodes)


I'm not sure the grave severity is justified here.  From what you've
shown, this can only be a single line in the 50chrootname setup script
failing.  All the values set in the script are correct AFAICT, so it's
most likely down to a filesystem issue or some other problem making
that single echo statement fail.


Thanks,
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



More information about the Buildd-tools-devel mailing list