Debian Bug report logs - #759740
--system --quiet ... still produces warnings and bad exit code

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andrew Patterson <andrew.patterson@hp.com>

To: submit@bugs.debian.org

Subject: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Fri, 29 Aug 2014 14:33:14 -0600

Package: apt-cache-ng
Version: 0.7.11-2
Severity: important
Tags: wheezy

I get the following error when trying to upgrade apt-cache-ng on wheezy:

Setting up apt-cacher-ng (0.7.11-2) ...
adduser: The user `apt-cacher-ng' already exists. Exiting.
dpkg: error processing apt-cacher-ng (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 apt-cacher-ng
E: Sub-process /usr/bin/dpkg returned an error code (1)

And the user does indeed already exist (as you would expect with an
upgrade):

$ grep apt-cacher-ng /etc/passwd
apt-cacher-ng:x:0:108::/var/cache/apt-cacher-ng:/bin/false
acng:x:0:108::/var/cache/apt-cacher-ng:/bin/false

-- Andrew

Message #8 received at 759740@bugs.debian.org (full text, mbox, reply):

From: Andrei POPESCU <andreimpopescu@gmail.com>

To: Andrew Patterson <andrew.patterson@hp.com>, 759740@bugs.debian.org

Cc: apt-cacher-ng@packages.debian.org

Subject: Re: Bug#759740: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Sun, 31 Aug 2014 20:16:17 +0300

[Message part 1 (text/plain, inline)]

Control: reassign -1 apt-cacher-ng 0.7.11-2

On Vi, 29 aug 14, 14:33:14, Andrew Patterson wrote:
> Package: apt-cache-ng
> Version: 0.7.11-2
> Severity: important
> Tags: wheezy
> 
> I get the following error when trying to upgrade apt-cache-ng on wheezy:
> 
> Setting up apt-cacher-ng (0.7.11-2) ...
> adduser: The user `apt-cacher-ng' already exists. Exiting.
> dpkg: error processing apt-cacher-ng (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  apt-cacher-ng
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> And the user does indeed already exist (as you would expect with an
> upgrade):
> 
> $ grep apt-cacher-ng /etc/passwd
> apt-cacher-ng:x:0:108::/var/cache/apt-cacher-ng:/bin/false
> acng:x:0:108::/var/cache/apt-cacher-ng:/bin/false
> 
> -- Andrew

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 759740@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: Andrei POPESCU <andreimpopescu@gmail.com>

Cc: Andrew Patterson <andrew.patterson@hp.com>, 759740@bugs.debian.org, apt-cacher-ng@packages.debian.org

Subject: Re: Bug#759740: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Sun, 31 Aug 2014 21:32:01 +0200

Control: forcemerge 706382 759740

> > I get the following error when trying to upgrade apt-cache-ng on wheezy:
> > 
> > Setting up apt-cacher-ng (0.7.11-2) ...
> > adduser: The user `apt-cacher-ng' already exists. Exiting.
> > dpkg: error processing apt-cacher-ng (--configure):
> >  subprocess installed post-installation script returned error exit status 1
> > Errors were encountered while processing:
> >  apt-cacher-ng
> > E: Sub-process /usr/bin/dpkg returned an error code (1)

Yeah, sorry, that was fixed back in 2013. Please use the backport version
or revert your users UID to the range which is accepted by adduser (see
the linked bugreport for details). That would also require a chown-R run
on your cache and log directories, of course.

Regards,
Eduard.

Message #24 received at 759740@bugs.debian.org (full text, mbox, reply):

From: Andrew Patterson <andrew.patterson@hp.com>

To: 759740@bugs.debian.org

Subject: Re: Bug#759740: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Tue, 02 Sep 2014 15:24:10 -0600

On Sun, 31 Aug 2014 21:32:01 +0200 Eduard Bloch <edi@gmx.de> wrote:
> Control: forcemerge 706382 759740
>
> > > I get the following error when trying to upgrade apt-cache-ng on wheezy:
> > >
> > > Setting up apt-cacher-ng (0.7.11-2) ...
> > > adduser: The user `apt-cacher-ng' already exists. Exiting.
> > > dpkg: error processing apt-cacher-ng (--configure):
> > > subprocess installed post-installation script returned error exit status 1
> > > Errors were encountered while processing:
> > > apt-cacher-ng
> > > E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Yeah, sorry, that was fixed back in 2013. Please use the backport version
> or revert your users UID to the range which is accepted by adduser (see
> the linked bugreport for details). That would also require a chown-R run
> on your cache and log directories, of course.
>
> Regards,
> Eduard.
>
>

I guess I don't understand. The current account seem perfectly valid, i.e., uid = 108. Why is the configure scripts trying to re-add the user if it already exists? I can re-add the user, but what ID should I use?

I tried running adduser by hand and got what I think are the expected results:

# adduser --quiet --system --group --no-create-home --home /var/cache/apt-cacher-ng apt-cacher-ng
adduser: The user `apt-cacher-ng' already exists. Exiting.

I am guessing I could delete the user, then rerun the configure script everything would fine.

-- Andrew

Message #29 received at 759740@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: Andrew Patterson <andrew.patterson@hp.com>, 759740@bugs.debian.org

Cc: control@bugs.debian.org, adduser@packages.debian.org

Subject: Re: Bug#759740: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Wed, 3 Sep 2014 19:13:46 +0200

reassign 759740 adduser
retitle 759740 --system --quiet ... still produces warnings and bad exit code
thanks

Hallo,
* Andrew Patterson [Tue, Sep 02 2014, 03:24:10PM]:

> I guess I don't understand. The current account seem perfectly valid, i.e., uid = 108. Why is the configure scripts trying to re-add the user if it already exists? I can re-add the user, but what ID should I use?
> 
> I tried running adduser by hand and got what I think are the expected results:
> 
> # adduser --quiet --system --group --no-create-home --home /var/cache/apt-cacher-ng apt-cacher-ng
> adduser: The user `apt-cacher-ng' already exists. Exiting.

Nope, those are not the expected results:

   Add a system user
       If called with one non-option argument and the --system option, adduser will  add  a
       system  user.  If  a  user with the same name already exists in the system uid range
       (or, if the uid is specified, if a user with that uid already exists), adduser  will
       exit with a warning. This warning can be suppressed by adding "--quiet".

Now I am also wondering what is going on. The last year's bug was clearly reproducible with UID being outside of the system UID range. Your problem apparently has a different reason, therefore I am reassigning this BR.

> I am guessing I could delete the user, then rerun the configure script everything would fine.

Yes and no... you would need to change the ownership of the the logdir/cachedir contents (chown -R...) but appart from that it should do the job.

Thanks,
Eduard.

Message #40 received at 759740@bugs.debian.org (full text, mbox, reply):

From: Andrew Patterson <andrew.patterson@hp.com>

To: 759740@bugs.debian.org

Subject: Re: Bug#759740: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Wed, 03 Sep 2014 12:53:32 -0600

[Message part 1 (text/plain, inline)]

On Wed, 3 Sep 2014 19:13:46 +0200 Eduard Bloch <edi@gmx.de> wrote:
> reassign 759740 adduser
> retitle 759740 --system --quiet ... still produces warnings and bad exit code
> thanks
>
> Hallo,
> * Andrew Patterson [Tue, Sep 02 2014, 03:24:10PM]:
>
> > I guess I don't understand. The current account seem perfectly valid, i.e., uid = 108. Why is the configure scripts trying to re-add the user if it already exists? I can re-add the user, but what ID should I use?
> >
> > I tried running adduser by hand and got what I think are the expected results:
> >
> > # adduser --quiet --system --group --no-create-home --home /var/cache/apt-cacher-ng apt-cacher-ng
> > adduser: The user `apt-cacher-ng' already exists. Exiting.
>
> Nope, those are not the expected results:
>
> Add a system user
> If called with one non-option argument and the --system option, adduser will add a
> system user. If a user with the same name already exists in the system uid range
> (or, if the uid is specified, if a user with that uid already exists), adduser will
> exit with a warning. This warning can be suppressed by adding "--quiet".
>
> Now I am also wondering what is going on. The last year's bug was clearly reproducible with UID being outside of the system UID range. Your problem apparently has a different reason, therefore I am reassigning this BR.
>
> > I am guessing I could delete the user, then rerun the configure script everything would fine.
>
> Yes and no... you would need to change the ownership of the the logdir/cachedir contents (chown -R...) but appart from that it should do the job.
>
> Thanks,
> Eduard.
>
>

I downloaded the deb source for apt-cacher-ng and found this in
apt-cacher-ng.postinst:

if [ "$1" = "configure" ]; then

   adduser --quiet --system --group --no-create-home --home $CDIR $NAME

   for x in $CDIR $LDIR ; do
      if [ ! -d "$x" ]; then
         install -d -g $NAME -o $NAME -m2755 "$x"
      fi
   done

So the script is not checking if the user exists before adding
it. Should configure be run when upgrading the package?

One possible complication I may be running into is that I am using
LDAP for user accounts with uid > 2000, which would fail if
apt-cacher-ng was trying to create a user in the range. But I think
the problem here is solely that the account already exists and the
code should be more like:


if [ "$1" = "configure" ]; then

   if getent passwd $NAME; then
      : # Or pehaps remove the user and re-add.
   else
      adduser --quiet --system --group --no-create-home --home $CDIR $NAME
   fi

-- Andrew

[Message part 2 (text/html, inline)]

Message #45 received at 759740@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: Andrew Patterson <andrew.patterson@hp.com>

Cc: 759740@bugs.debian.org

Subject: Re: Bug#759740: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Thu, 4 Sep 2014 07:10:39 +0200

Hallo,
* Andrew Patterson [Wed, Sep 03 2014, 12:53:32PM]:
> One possible complication I may be running into is that I am using
> LDAP for user accounts with uid > 2000, which would fail if
> apt-cacher-ng was trying to create a user in the range. But I think
> the problem here is solely that the account already exists and the
> code should be more like:
> 
> 
> if [ "$1" = "configure" ]; then
> 
>    if getent passwd $NAME; then
>       : # Or pehaps remove the user and re-add.
>    else
>       adduser --quiet --system --group --no-create-home --home $CDIR $NAME
>    fi

I don't know. And as I mentioned before, feel free to use the backport
version. It contains a quick workaround for a similar situation:

   # user should exist. adduser sometimes fails (system range issue) but that's ok
   adduser --quiet --system --group --no-create-home --home "$CDIR" $NAME || id $NAME

Regards,
Eduard.

Message #50 received at 759740@bugs.debian.org (full text, mbox, reply):

From: Andrew Patterson <andrew.patterson@hp.com>

To: Eduard Bloch <edi@gmx.de>

Cc: 759740@bugs.debian.org

Subject: Re: Bug#759740: apt-cache-ng: user apt-cacher-ng already exists error when upgrading

Date: Thu, 04 Sep 2014 10:40:03 -0600

[Message part 1 (text/plain, inline)]

>
> I don't know. And as I mentioned before, feel free to use the backport
> version. It contains a quick workaround for a similar situation:
>
>    # user should exist. adduser sometimes fails (system range issue) but that's ok
>    adduser --quiet --system --group --no-create-home --home "$CDIR" $NAME || id $NAME
>
> Regards,
> Eduard.

We used your backports work-around and everything is working fine now.

-- Andrew

[Message part 2 (text/html, inline)]

Message #53 received at 759740-submitter@bugs.debian.org (full text, mbox, reply):

From: Afif Elghraoui <afif@debian.org>

To: 759740-submitter@bugs.debian.org

Cc: edi@gmx.de

Subject: Re: Bug#759740: adduser: --system --quiet ... still produces warnings and bad exit code

Date: Sat, 26 Nov 2016 02:42:18 -0800

Hello,

On Wed, 3 Sep 2014 19:13:46 +0200 Eduard Bloch <edi@gmx.de> wrote:
> reassign 759740 adduser
> retitle 759740 --system --quiet ... still produces warnings and bad exit code
> thanks
> 
> Hallo,
> * Andrew Patterson [Tue, Sep 02 2014, 03:24:10PM]:
> 
> > I guess I don't understand. The current account seem perfectly valid, i.e., uid = 108. Why is the configure scripts trying to re-add the user if it already exists? I can re-add the user, but what ID should I use?
> > 
> > I tried running adduser by hand and got what I think are the expected results:
> > 
> > # adduser --quiet --system --group --no-create-home --home /var/cache/apt-cacher-ng apt-cacher-ng
> > adduser: The user `apt-cacher-ng' already exists. Exiting.
> 
> Nope, those are not the expected results:
> 
>    Add a system user
>        If called with one non-option argument and the --system option, adduser will  add  a
>        system  user.  If  a  user with the same name already exists in the system uid range
>        (or, if the uid is specified, if a user with that uid already exists), adduser  will
>        exit with a warning. This warning can be suppressed by adding "--quiet".
> 
> Now I am also wondering what is going on. The last year's bug was clearly reproducible with UID being outside of the system UID range. Your problem apparently has a different reason, therefore I am reassigning this BR.
> 

I think this is a case similar to #708073. The submitter reported [1]:

~~~
$ grep apt-cacher-ng /etc/passwd
apt-cacher-ng:x:0:108::/var/cache/apt-cacher-ng:/bin/false
acng:x:0:108::/var/cache/apt-cacher-ng:/bin/false
~~~

So the UID is not 108, but actually 0 (?!). I'm also confused as to why
there are two entries with identical UID/GIDs.

Weirdness aside, the default system UID/GID range is 100-999, so adduser
is considering anything outside of that as a regular user ID. I suppose
it should also check for existing entries in range 0-99.

Thanks and regards
Afif

1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759740#5

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Message #56 received at 759740-submitter@bugs.debian.org (full text, mbox, reply):

From: Afif Elghraoui <afif@debian.org>

To: 759740-submitter@bugs.debian.org

Subject: Bug#759740 in package adduser marked as pending

Date: Sat, 12 Aug 2017 20:14:08 +0000

Control: tag 759740 pending

Bug #759740 in package adduser reported by you has been fixed in
the adduser/adduser.git Git repository. You can see the changelog below, and
you can check the diff of the fix at:

    https://anonscm.debian.org/cgit/adduser/adduser.git/commit/?id=6400c67

---
commit 6400c67d621affb74d12079261e02e8d764b4775
Author: Afif Elghraoui <afif@debian.org>
Date:   Sat Aug 12 12:42:52 2017 -0400

    Update changelog

diff --git a/debian/changelog b/debian/changelog
index d72119d..924c1c6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+adduser (3.116) UNRELEASED; urgency=medium
+
+  * Advise installation of 'perl' rather than 'perl-modules'
+    (Closes: #840982)
+  * Improve distinction between informational and essential messages
+    (Closes: #763055)
+  * Improve message accompanying error code for creating system user
+    (Closes: #708073, #759740)
+  * testsuite: add current directory to module search path
+
+ -- Afif Elghraoui <afif@debian.org>  Sat, 12 Aug 2017 11:44:19 -0400
+
 adduser (3.115) unstable; urgency=medium
 
   [ Afif Elghraoui ]

Message #63 received at 759740-close@bugs.debian.org (full text, mbox, reply):

From: Afif Elghraoui <afif@debian.org>

To: 759740-close@bugs.debian.org

Subject: Bug#759740: fixed in adduser 3.116

Date: Sat, 12 Aug 2017 20:49:19 +0000

Source: adduser
Source-Version: 3.116

We believe that the bug you reported is fixed in the latest version of
adduser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 759740@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Afif Elghraoui <afif@debian.org> (supplier of updated adduser package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 12 Aug 2017 16:05:34 -0400
Source: adduser
Binary: adduser
Architecture: source
Version: 3.116
Distribution: unstable
Urgency: medium
Maintainer: Debian Adduser Developers <adduser-devel@lists.alioth.debian.org>
Changed-By: Afif Elghraoui <afif@debian.org>
Description:
 adduser    - add and remove users and groups
Closes: 708073 759740 763055 840982 845791
Changes:
 adduser (3.116) unstable; urgency=medium
 .
   * Advise installation of 'perl' rather than 'perl-modules'
     (Closes: #840982)
   * Improve distinction between informational and essential messages
     (Closes: #763055)
   * Improve message accompanying error code for creating system user
     (Closes: #708073, #759740)
   * testsuite: add current directory to Perl module search path
   * Use /usr/sbin/nologin instead of /bin/false for default system shell
     (Closes: #845791)
   * Bump Standards-Version to 4.0.1
Checksums-Sha1:
 649f82bad2d5234d899c126a19bb66bc7867a8f0 1740 adduser_3.116.dsc
 8cd86a573f8e9ede3cee2fd14a35287bf300eb68 212012 adduser_3.116.tar.xz
 30e561dae6a99add7c6d925b28129905493f7577 5767 adduser_3.116_source.buildinfo
Checksums-Sha256:
 50e4154d3101101a890864185a09478c182155dc13f73dbb465c4279213bfafa 1740 adduser_3.116.dsc
 72d811ad3ba17d2794b14d19acd1d6b57f9dd31d9250d51e786895dee2daeac0 212012 adduser_3.116.tar.xz
 a2c50a451d87ebac2e8007f55d7850afc581c2ce9d0a09d544a59a42132adabf 5767 adduser_3.116_source.buildinfo
Files:
 66a17b27890067707dbf9580814c7918 1740 admin important adduser_3.116.dsc
 e042a5842b8f24312d6f5a99a1af8f2c 212012 admin important adduser_3.116.tar.xz
 fee33cdea505963c2bbe2b6cbedd0e5b 5767 admin important adduser_3.116_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE6rcjomb2J+aAVWFfWbIwbzr53cEFAlmPYVMQHGFmaWZAZGVi
aWFuLm9yZwAKCRBZsjBvOvndwUd7D/4387QEKKi7MKVZqxiIEJnzGsE4OV7f5vZr
U1FQV2tQruYyMYOFg1Q2b4Dr639hSa0AJhw2Mr7Nb/zzxN7amIlJWcowM2fUWxKz
ulMLsizC5yISUE0AKqbIzHPHl55yJMjDLS89iPE1OO9Axdbss8wr2VZC4pVTejgW
+BIcZyHH0um+4cj2PTjFjVH7TpwsRY2kl+SW7tyxolaDdnVNY4YX37Jr4SOo3NcJ
ld5BNpCxjjqFl2T0AzZNv3kMrqs3/MvULP5aHt91mjdRAf59V2+HPg/jMm9UeEkJ
B4JguAbFibKnB8WdBkMzSNXUSUNla09p4dfEYFNPUcZYrUfC/MAwTzcf/rt6DxbQ
E6IRnhiw/KAEh4kK6DYpXBawwLokysfFA3yfGTH3tf7Ii5/9g6Ajwefswwt+pWqP
d10uh9TEY5QgLlDsC4dlgPFnD3UrmUGTdflAIx5DjsjDcrxVrwKDbiiork/LjcfE
pqiojmHJhyjbBUSmT+APp8QCPY7BC/is+mPQBYUH8coUEwPRhQ/cpVAKlS5yuuj6
xm95bp+I9CSoGZuBjBtlY7zFDndLy6FSY6Dfkr/w91avmDyOHsMF0RnaHSBlD5Q8
VbU/euaQlWdj1teShZRHwqx5K7h2V0k9WMW/UWZNKZFKK3Fj9nTj/zxYwzRZGySx
XhfTxIps3A==
=jUjJ
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.