Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

mpd/systemd problem

165 views
Skip to first unread message

sp113438

unread,
Dec 16, 2014, 12:20:04 PM12/16/14
to
Hello,

I have a problem with updating mpd and/or systemd.


Preparing to unpack .../m/mpd/mpd_0.19.1-1.1_amd64.deb ...
Job for mpd.service canceled.
invoke-rc.d: initscript mpd, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit
status 1 dpkg: trying script from the new package instead ...
Job for mpd.service canceled.
invoke-rc.d: initscript mpd, action "stop" failed.
dpkg: error processing
archive /home/debmirror/pool/main/m/mpd/mpd_0.19.1-1.1_amd64.deb
(--unpack): subprocess new pre-removal script returned error exit
status 1


Also I can not remove mpd.

# apt-get remove mpd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
mpd
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 1,202 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 299439 files and directories currently installed.)
Removing mpd (0.19.1-1) ...
Job for mpd.service canceled.
invoke-rc.d: initscript mpd, action "stop" failed.
dpkg: error processing package mpd (--remove):
subprocess installed pre-removal script returned error exit status 1
Errors were encountered while processing:
mpd
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


Debian Jessie up-to-date, AMD64.

Arne


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141216175756.3057c112@fx4100

Andrei POPESCU

unread,
Dec 16, 2014, 6:30:06 PM12/16/14
to
On Ma, 16 dec 14, 17:57:56, sp113438 wrote:
> Hello,
>
> I have a problem with updating mpd and/or systemd.
>
>
> Preparing to unpack .../m/mpd/mpd_0.19.1-1.1_amd64.deb ...
> Job for mpd.service canceled.
> invoke-rc.d: initscript mpd, action "stop" failed.
> dpkg: warning: subprocess old pre-removal script returned error exit
> status 1 dpkg: trying script from the new package instead ...
> Job for mpd.service canceled.
> invoke-rc.d: initscript mpd, action "stop" failed.
> dpkg: error processing
> archive /home/debmirror/pool/main/m/mpd/mpd_0.19.1-1.1_amd64.deb
> (--unpack): subprocess new pre-removal script returned error exit
> status 1

Please post the output of

systemctl status mpd

I also noticed that mpd also has a .socket unit. If you something is
trying to use mpd it will get restarted via the socket.

Kind regards,
Andrei
--
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

sp113438

unread,
Dec 16, 2014, 9:10:04 PM12/16/14
to
On Wed, 17 Dec 2014 01:08:03 +0200
Andrei POPESCU <andreim...@gmail.com> wrote:

> On Ma, 16 dec 14, 17:57:56, sp113438 wrote:
> > Hello,
> >
> > I have a problem with updating mpd and/or systemd.
> >
> >
> > Preparing to unpack .../m/mpd/mpd_0.19.1-1.1_amd64.deb ...
> > Job for mpd.service canceled.
> > invoke-rc.d: initscript mpd, action "stop" failed.
> > dpkg: warning: subprocess old pre-removal script returned error exit
> > status 1 dpkg: trying script from the new package instead ...
> > Job for mpd.service canceled.
> > invoke-rc.d: initscript mpd, action "stop" failed.
> > dpkg: error processing
> > archive /home/debmirror/pool/main/m/mpd/mpd_0.19.1-1.1_amd64.deb
> > (--unpack): subprocess new pre-removal script returned error exit
> > status 1
>
> Please post the output of
>
> systemctl status mpd
>
> I also noticed that mpd also has a .socket unit. If you something is
> trying to use mpd it will get restarted via the socket.
>
> Kind regards,
> Andrei

The problem is solved by renaming /usr/bin/mpd , stop mpd and then update.

The following:

systemctl stop mpd.service
killall mpd
kill -9 *2600*
mpd --kill
/etc/init.d/mpd stop

all didn't succeed

I guess I have to blame systemd.

Thanks!





--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217024421.19320b03@fx4100

sp113438

unread,
Dec 16, 2014, 9:30:04 PM12/16/14
to
On Wed, 17 Dec 2014 02:44:21 +0100

Sorry,

The problem is solved by renaming /usr/bin/mpd , restart the
computer and then update.

(I found no other way of stopping mpd)

Thanks!


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217030655.0c8e9b2e@fx4100

sp113438

unread,
Dec 16, 2014, 9:50:04 PM12/16/14
to
On Wed, 17 Dec 2014 01:08:03 +0200
Andrei POPESCU <andreim...@gmail.com> wrote:
>
> Please post the output of
>
> systemctl status mpd

# systemctl status mpd
● mpd.service - Music Player Daemon
Loaded: loaded (/lib/systemd/system/mpd.service; enabled)
Active: active (running) since Wed 2014-12-17 04:18:21 CET; 53min
left Main PID: 571 (mpd)
CGroup: /system.slice/mpd.service
└─571 /usr/bin/mpd --no-daemon


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217032805.627a2fc7@fx4100

sp113438

unread,
Dec 16, 2014, 10:30:05 PM12/16/14
to
On Wed, 17 Dec 2014 03:06:55 +0100
sp113438 <sp11...@telfort.nl> wrote:

> On Wed, 17 Dec 2014 02:44:21 +0100
>
> Sorry,
>
> The problem is solved by renaming /usr/bin/mpd , restart the
> computer and then update.
>
> (I found no other way of stopping mpd)
>
> Thanks!
>
This part remains unsolved:

systemd can not stop mpd.
Shutting down the computer takes one and a half minute.

This seems to be a fault in systemd.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217040555.3f163e37@fx4100

Don Armstrong

unread,
Dec 17, 2014, 12:40:04 AM12/17/14
to
On Wed, 17 Dec 2014, sp113438 wrote:
> On Wed, 17 Dec 2014 01:08:03 +0200
> Andrei POPESCU <andreim...@gmail.com> wrote:
> >
> > Please post the output of
> >
> > systemctl status mpd
>
> # systemctl status mpd
> ● mpd.service - Music Player Daemon
> Loaded: loaded (/lib/systemd/system/mpd.service; enabled)
> Active: active (running) since Wed 2014-12-17 04:18:21 CET; 53min
> left Main PID: 571 (mpd)
> CGroup: /system.slice/mpd.service
> └─571 /usr/bin/mpd --no-daemon

It's not clear to me why service mpd stop; isn't enough to stop this
particular one, but the following will stop mpd:

systemctl disable mpd.service; systemctl disable mpd.socket;

Please also file a bug against mpd.

--
Don Armstrong http://www.donarmstrong.com

I stared at the mountain rising over me. Empty. It was a pointless
thing to have done -- climb up it, across it, and down it. Stupid! It
looked perfect; so clean and untouched, and we had changed nothing.
[...] I had been on it too long, and it had taken everything.
-- Joe Simpson "Touching the Void" p117


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217052...@teltox.donarmstrong.com

Andrei POPESCU

unread,
Dec 17, 2014, 5:10:05 AM12/17/14
to
On Ma, 16 dec 14, 21:20:48, Don Armstrong wrote:
>
> It's not clear to me why service mpd stop; isn't enough to stop this
> particular one, but the following will stop mpd:

Works for me. Possibly more information about clients in use might help.
signature.asc

Darac Marjal

unread,
Dec 17, 2014, 5:40:03 AM12/17/14
to
Really? You "kill -9"ed the process, it failed to stop and you're
blaming systemd? I know systemd is the current whipping-boy but that
seems harsh to me.

First of all, see why mpd is unresponsive (it may be in the 'D' state,
which usually indicates that it's waiting for I/O - if that's the case,
the process doesn't even notice the kill signal). If you can't kill it,
then don't expect systemd to be able to, either.
signature.asc

Henrique de Moraes Holschuh

unread,
Dec 17, 2014, 7:10:04 AM12/17/14
to
On Tue, 16 Dec 2014, Don Armstrong wrote:
> It's not clear to me why service mpd stop; isn't enough to stop this
> particular one, but the following will stop mpd:

Because our support for systemd socket activation in invoke-rc.d is broken
(as in invoke-rc.d stop _does not_ stop socket-activated units, just the
main unit). Every package that has socket activation is affected.

There's a bunch of bugs against invoke-rc.d about it, and I might even get
around to fixing the issue out of general annoyance soon[1], but it would be
best if someone that actually runs systemd did it and submitted a tested
patch.

[1] I expected to have done it already, but I got sidetracked and my Debian
time is greatly reduced right now.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217114...@khazad-dum.debian.net

Henrique de Moraes Holschuh

unread,
Dec 17, 2014, 7:30:04 AM12/17/14
to
On Wed, 17 Dec 2014, Henrique de Moraes Holschuh wrote:
> On Tue, 16 Dec 2014, Don Armstrong wrote:
> > It's not clear to me why service mpd stop; isn't enough to stop this
> > particular one, but the following will stop mpd:
>
> Because our support for systemd socket activation in invoke-rc.d is broken
> (as in invoke-rc.d stop _does not_ stop socket-activated units, just the
> main unit). Every package that has socket activation is affected.

Sorry, my answer was misleading and likely incorrect for this situation.
"service" _is_ quite capable of doing the right thing, so if it doesn't stop
mpd, the issue is in the mpd package.

OTOH, "invoke-rc.d" really is buggy in that regard, so if the issue shows up
during package updates/removals, it is invoke-rc.d's fault for not stopping
the socket service.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217120...@khazad-dum.debian.net

sp113438

unread,
Dec 17, 2014, 8:20:04 AM12/17/14
to
On Tue, 16 Dec 2014 21:20:48 -0800
Don Armstrong <d...@debian.org> wrote:

> On Wed, 17 Dec 2014, sp113438 wrote:
> > On Wed, 17 Dec 2014 01:08:03 +0200
> > Andrei POPESCU <andreim...@gmail.com> wrote:
> > >
> > > Please post the output of
> > >
> > > systemctl status mpd
> >
> > # systemctl status mpd
> > ● mpd.service - Music Player Daemon
> > Loaded: loaded (/lib/systemd/system/mpd.service; enabled)
> > Active: active (running) since Wed 2014-12-17 04:18:21 CET; 53min
> > left Main PID: 571 (mpd)
> > CGroup: /system.slice/mpd.service
> > └─571 /usr/bin/mpd --no-daemon
>
> It's not clear to me why service mpd stop; isn't enough to stop this
> particular one, but the following will stop mpd:
>
> systemctl disable mpd.service; systemctl disable mpd.socket;
>
> Please also file a bug against mpd.
>
This:
systemctl disable mpd.service; systemctl disable mpd.socket;
is not able to stop mpd

Thanks!


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217135711.561df8a7@fx4100

Don Armstrong

unread,
Dec 17, 2014, 11:40:04 AM12/17/14
to
On Wed, 17 Dec 2014, sp113438 wrote:
> systemctl disable mpd.service; systemctl disable mpd.socket;
> is not able to stop mpd

What is the output of systemctl status mpd.{socket,status}; after you
have disabled the service?

Both should be loaded, disabled, and inactive.

--
Don Armstrong http://www.donarmstrong.com

If you have the slightest bit of intellectual integrity you cannot
support the government. -- anonymous


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217161...@teltox.donarmstrong.com

sp113438

unread,
Dec 17, 2014, 12:10:04 PM12/17/14
to
On Wed, 17 Dec 2014 08:16:04 -0800
Don Armstrong <d...@debian.org> wrote:

> On Wed, 17 Dec 2014, sp113438 wrote:
> > systemctl disable mpd.service; systemctl disable mpd.socket;
> > is not able to stop mpd
>
> What is the output of systemctl status mpd.{socket,status}; after you
> have disabled the service?
>
> Both should be loaded, disabled, and inactive.
>
# systemctl disable mpd.service; systemctl disable mpd.socket;
Synchronizing state for mpd.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d mpd defaults
insserv: warning: current start runlevel(s) (empty) of script `mpd'
overrides LSB defaults (2 3 4 5). insserv: warning: current stop
runlevel(s) (0 1 2 3 4 5 6) of script `mpd' overrides LSB defaults (0 1
6). Executing /usr/sbin/update-rc.d mpd disable insserv: warning:
current start runlevel(s) (empty) of script `mpd' overrides LSB
defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3
4 5 6) of script `mpd' overrides LSB defaults (0 1 6).

# systemctl status mpd.{socket,status};
● mpd.socket
Loaded: loaded (/lib/systemd/system/mpd.socket; disabled)
Active: inactive (dead)
Listen: /run/mpd/socket (Stream)
[::]:6600 (Stream)

● mpd.status.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

Thanks!


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217174502.6a8342d8@fx4100

Don Armstrong

unread,
Dec 17, 2014, 12:40:03 PM12/17/14
to
On Wed, 17 Dec 2014, sp113438 wrote:
> On Wed, 17 Dec 2014 08:16:04 -0800
> Don Armstrong <d...@debian.org> wrote:
>
> > On Wed, 17 Dec 2014, sp113438 wrote:
> > > systemctl disable mpd.service; systemctl disable mpd.socket;
> > > is not able to stop mpd

[...]

> # systemctl disable mpd.service; systemctl disable mpd.socket;

[...]

> # systemctl status mpd.{socket,status};
> ● mpd.socket
> Loaded: loaded (/lib/systemd/system/mpd.socket; disabled)
> Active: inactive (dead)
> Listen: /run/mpd/socket (Stream)
> [::]:6600 (Stream)

Err, that should have been {socket,service}, not {socket,status}.

But in any event, it looks like they're both disabled, and not running.
So I'm not sure why you said that it was unable to stop mpd.

--
Don Armstrong http://www.donarmstrong.com

"She decided what she wished to happen and then assumed that reality
would bend to her wishes." [...] "Reality doesn't indulge wishes."
-- Terry Goodkind _Phantom_ p133


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217172...@teltox.donarmstrong.com

sp113438

unread,
Dec 17, 2014, 2:00:06 PM12/17/14
to
On Wed, 17 Dec 2014 09:20:45 -0800
Don Armstrong <d...@debian.org> wrote:

> On Wed, 17 Dec 2014, sp113438 wrote:
> > On Wed, 17 Dec 2014 08:16:04 -0800
> > Don Armstrong <d...@debian.org> wrote:
> >
> > > On Wed, 17 Dec 2014, sp113438 wrote:
> > > > systemctl disable mpd.service; systemctl disable mpd.socket;
> > > > is not able to stop mpd
>
> [...]
>
> > # systemctl disable mpd.service; systemctl disable mpd.socket;
>
> [...]
>
> > # systemctl status mpd.{socket,status};
> > ● mpd.socket
> > Loaded: loaded (/lib/systemd/system/mpd.socket; disabled)
> > Active: inactive (dead)
> > Listen: /run/mpd/socket (Stream)
> > [::]:6600 (Stream)
>
> Err, that should have been {socket,service}, not {socket,status}.
>
> But in any event, it looks like they're both disabled, and not
> running. So I'm not sure why you said that it was unable to stop mpd.
>
While mpd is running:

systemctl status mpd.{socket,service};
● mpd.socket
Loaded: loaded (/lib/systemd/system/mpd.socket; disabled)
Active: inactive (dead)
Listen: /run/mpd/socket (Stream)
[::]:6600 (Stream)

● mpd.service - Music Player Daemon
Loaded: loaded (/lib/systemd/system/mpd.service; disabled)
Active: inactive (dead)

Dec 17 17:40:20 fx4100 systemd[1]: [/lib/systemd/system/mpd.service:17]
Unknown lvalue 'ControlGroup' in section 'Service' Dec 17 17:40:20
fx4100 systemd[1]: [/lib/systemd/system/mpd.service:20] Unknown lvalue
'ControlGroupAttribute' in section 'Service' Dec 17 17:41:06 fx4100
systemd[1]: [/lib/systemd/system/mpd.service:17] Unknown lvalue
'ControlGroup' in section 'Service' Dec 17 17:41:06 fx4100 systemd[1]:
[/lib/systemd/system/mpd.service:20] Unknown lvalue
'ControlGroupAttribute' in section 'Service' Dec 17 17:43:26 fx4100
systemd[1]: [/lib/systemd/system/mpd.service:17] Unknown lvalue
'ControlGroup' in section 'Service' Dec 17 17:43:26 fx4100 systemd[1]:
[/lib/systemd/system/mpd.service:20] Unknown lvalue
'ControlGroupAttribute' in section 'Service' Dec 17 19:37:33 fx4100
systemd[1]: [/lib/systemd/system/mpd.service:17] Unknown lvalue
'ControlGroup' in section 'Service' Dec 17 19:37:33 fx4100 systemd[1]:
[/lib/systemd/system/mpd.service:20] Unknown lvalue
'ControlGroupAttribute' in section 'Service' Dec 17 19:37:33 fx4100
systemd[1]: [/lib/systemd/system/mpd.service:17] Unknown lvalue
'ControlGroup' in section 'Service' Dec 17 19:37:33 fx4100 systemd[1]:
[/lib/systemd/system/mpd.service:20] Unknown lvalue
'ControlGroupAttribute' in section 'Service'

Hope this helps,
Thanks!


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20141217193912.7dbf2fb4@fx4100

Javier Prats

unread,
Dec 17, 2014, 3:10:07 PM12/17/14
to

That error looks like a known bug related to cgroups that's popped up on many distros.  See below.  Removing that related control group should solve the issue.



0 new messages