Your message dated Sun, 24 May 2015 01:33:32 +0200
with message-id <[email protected]>
and subject line Re: Bug#786648: fails to change euid, wrong command line
has caused the Debian Bug report #786648,
regarding fails to change euid, wrong command line
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
786648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786648
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-18
Severity: important

Hello,

first, sorry for the severity but I consider an account handling bug
almost critical.

Repro steps:

 - install apt-cacher-ng from Sid (0.8.3-1). That works fine, runs the
   process with correct uid and parameters.
 - build the package from
   https://alioth.debian.org/anonscm/git/apt-cacher-ng/apt-cacher-ng.git/
   (debian/sid branch) or get apt-cacher-ng_0.8.4-1_amd64.deb from
   https://www.unix-ag.uni-kl.de/~bloch/acng/tmp/ .
 - Install the .deb with dpkg

And then weird things start happening, see below. First I was confused.
Then I saw the WRONG command line. Thich explains the startup failure,
Foreground=1 parameter is missing. And then I saw the wrong process
lurking around. User is "root" now for no apparent reason.

I also cannot just downgrade the package because that ghost process
occupies the port. And using "service stop apt-cacher-ng" (or whatever
is run from prerm) is not effective because systemd thinks, the process
is dead.

And I cannot spot a related difference between
apt-cacher-ng_0.8.3-1_amd64.deb and apt-cacher-ng_0.8.4-1_amd64.deb.

Preparing to unpack .../apt-cacher-ng_0.8.4-1_amd64.deb ...
Unpacking apt-cacher-ng (0.8.4-1) over (0.8.3-1) ...
Setting up apt-cacher-ng (0.8.4-1) ...
Job for apt-cacher-ng.service failed. See 'systemctl status 
apt-cacher-ng.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript apt-cacher-ng, action "start" failed.
dpkg: error processing package apt-cacher-ng (--install):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for doc-base (0.10.6) ...
Processing 1 changed doc-base file...
Registering documents with dwww...
Registering documents with scrollkeeper...
Processing triggers for systemd (215-18) ...
Errors were encountered while processing:
 apt-cacher-ng
zombie: ~/debian/dev/apt-cacher-ng $ sudo systemctl status apt-cacher-ng.service
● apt-cacher-ng.service - Apt-Cacher NG software download proxy
   Loaded: loaded (/lib/systemd/system/apt-cacher-ng.service; enabled)
   Active: failed (Result: start-limit) since Sun 2015-05-24 00:03:28 CEST; 3s 
ago
 Main PID: 13459 (code=exited, status=1/FAILURE)

May 24 00:03:28 zombie systemd[1]: Unit apt-cacher-ng.service entered failed 
state.
May 24 00:03:28 zombie systemd[1]: apt-cacher-ng.service holdoff time over, 
scheduling restart.
May 24 00:03:28 zombie systemd[1]: Stopping Apt-Cacher NG software download 
proxy...
May 24 00:03:28 zombie systemd[1]: Starting Apt-Cacher NG software download 
proxy...
May 24 00:03:28 zombie systemd[1]: apt-cacher-ng.service start request repeated 
too quickly, refusing to start.
May 24 00:03:28 zombie systemd[1]: Failed to start Apt-Cacher NG software 
download proxy.
May 24 00:03:28 zombie systemd[1]: Unit apt-cacher-ng.service entered failed 
state.
zombie: ~/debian/dev/apt-cacher-ng $ ps aux | grep apt-cacher-ng
...
root     13079  0.0  0.0  47464  1484 ?        Ss   00:03   0:00 
/usr/sbin/apt-cacher-ng -c /etc/apt-cacher-ng
zombie: ~/debian/dev/apt-cacher-ng $ grep Exec 
/lib/systemd/system/apt-cacher-ng.service
ExecStart=/usr/sbin/apt-cacher-ng SocketPath=/var/run/apt-cacher-ng/socket -c 
/etc/apt-cacher-ng ForeGround=1

I have a weid feeling that some voodoo in systemd decided to strip the
"assinment-looking" options and do root mode... but why? And what does
trigger this behavior?

Regards,
Eduard.

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-rc3.111cputssfix+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages systemd depends on:
ii  acl             2.2.52-2
ii  adduser         3.113+nmu3
ii  initscripts     2.88dsf-59.2
ii  libacl1         2.2.52-2
ii  libaudit1       1:2.4-1+b1
ii  libblkid1       2.26.2-5
ii  libc6           2.19-18
ii  libcap2         1:2.24-8
ii  libcap2-bin     1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.3-2
ii  libkmod2        20-1
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2
ii  libsystemd0     215-18
ii  mount           2.26.2-5
ii  sysv-rc         2.88dsf-59.2
ii  udev            215-18
ii  util-linux      2.26.2-5

Versions of packages systemd recommends:
ii  dbus            1.8.18-1
ii  libpam-systemd  215-18

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- no debconf information

-- 
<youam> RomanK: s/admins/menschen/, bitte :)
<Aqua> RomanK: schon versucht
<RomanK> youam: s/menschen/unmenschen/
<Aqua> hilft nix

--- End Message ---
--- Begin Message ---
Hallo,
* Michael Biebl [Sun, May 24 2015, 01:12:05AM]:

> > I also cannot just downgrade the package because that ghost process
> > occupies the port. And using "service stop apt-cacher-ng" (or whatever
> > is run from prerm) is not effective because systemd thinks, the process
> > is dead.
> 
> Are you absolutely sure you started this process via systemd? Could it
> be you started it manually? That would explain why the process is not
> tracked by systemd, has the wrong user and subsequent tries to start it
> via systemctl/service fail.

I was sure when I wrote the bug report but that has changed a couple of
minutes ago :-(

Sory, it's a self-made problem, will need to adapt postinst to some
upstream changes.

Sorry for the noise, have a good night and rest of the holidays.

Regards,
Eduard.

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to