Your message dated Sat, 27 Jul 2019 04:08:29 +0000
with message-id <e1hre0t-0002bb...@fasolo.debian.org>
and subject line Bug#933144: fixed in shairport-sync 3.3.2-1
has caused the Debian Bug report #933144,
regarding shairport-sync: Daemon failed to start - shairport-sync was built
without libdaemon, so does not support daemonisation using ...
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 ow...@bugs.debian.org
immediately.)
--
933144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shairport-sync
Version: 3.3.1-1
Severity: important
Tags: patch
Dear Maintainer,
I did on my testing machine my first full-upgrade after buster got
stable. I got the new shairport-sync 3.1-1 installed. Maybe something
else has changed - systemd got definitely updated too.
My problem
===========
The shairport-sync daemon does not start.
I found a solution see below.
Analys
========
I found in
,---- [ /var/log/syslog ]
| Jul 26 22:23:16 osprey systemd[1]: Starting ShairportSync AirTunes receiver...
| Jul 26 22:23:16 osprey shairport-sync[2164]: shairport-sync was built without
libdaemon, so does not support daemonisation using the -d, --d
| eamon, -j or --justDaemoniseNoPIDFile options
| Jul 26 22:23:16 osprey systemd[1]: shairport-sync.service: Can't open PID
file /run/shairport-sync/shairport-sync.pid (yet?) after start: No
| such file or directory
| Jul 26 22:23:16 osprey systemd[1]: shairport-sync.service: Failed with result
'protocol'.
| Jul 26 22:23:16 osprey systemd[1]: Failed to start ShairportSync AirTunes
receiver.
`----
The package has a service file with the following line:
,---- [ /lib/systemd/system/shairport-sync.service ]
| ExecStart=/usr/bin/shairport-sync --daemon $DAEMON_ARGS
`----
In the man page one can read:
,---- [ man shairport-sync ]
| --daemon Instruct shairport-sync to demonise itself. [...] Only
| available if shaiport-sync has been compiled with libdaemon support.
`----
And in the source code file "configure.ac":
,---- [ https://github.com/mikebrady/shairport-sync/blob/master/configure.ac ]
| --with-libdaemon = include support for daemonising in non-systemd systems
`----
My conclusion is that imho the option "--daemon" should not be in the
service file so I removed it.
Without this option the daemon starts fine but gets killed from systemd
after a minute or so. I crosschecked with the service file in the
source code
(https://github.com/mikebrady/shairport-sync/blob/master/scripts/shairport-sync.service.in)
and removed from the debian service file the line
,---- [ /lib/systemd/system/shairport-sync.service ]
| Type=forking
`----
Solution
==========
After a "systemctl daemon-reload" to reread the changed service file I
was able to start the daemon which show as "active (running)" in
systemctl status shairport-sync.
I append my patch which removes the option and the Type-line from the
service file.
Hope this helps :-).
Tom
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages shairport-sync depends on:
ii adduser 3.118
ii avahi-daemon 0.7-4+b1
ii init-system-helpers 1.57
ii libasound2 1.1.8-1
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libc6 2.28-10
ii libconfig9 1.5-0.4
ii libgcc1 1:9.1.0-10
ii libpopt0 1.16-12
ii libpulse0 12.2-4
ii libsndfile1 1.0.28-6
ii libsoxr0 0.1.2-3
ii libssl1.1 1.1.1c-1
ii libstdc++6 9.1.0-10
shairport-sync recommends no packages.
shairport-sync suggests no packages.
-- Configuration Files:
/etc/init.d/shairport-sync changed [not included]
-- no debconf information
---------- patch 8< ----------------------------------
--- orig/shairport-sync.service 2019-07-17 21:14:16.000000000 +0200
+++ new/shairport-sync.service 2019-07-26 22:34:24.350961711 +0200
@@ -8,10 +8,9 @@
After=avahi-daemon.service
[Service]
-Type=forking
Restart=on-failure
EnvironmentFile=-/etc/default/shairport-sync
-ExecStart=/usr/bin/shairport-sync --daemon $DAEMON_ARGS
+ExecStart=/usr/bin/shairport-sync $DAEMON_ARGS
User=shairport-sync
Group=shairport-sync
PIDFile=/run/shairport-sync/shairport-sync.pid
---------- end patch >8 ------------------------------
--- End Message ---
--- Begin Message ---
Source: shairport-sync
Source-Version: 3.3.2-1
We believe that the bug you reported is fixed in the latest version of
shairport-sync, 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 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Boot <bo...@debian.org> (supplier of updated shairport-sync 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 27 Jul 2019 00:23:22 -0300
Source: shairport-sync
Architecture: source
Version: 3.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Boot <bo...@debian.org>
Changed-By: Chris Boot <bo...@debian.org>
Closes: 885893 925577 933144
Changes:
shairport-sync (3.3.2-1) unstable; urgency=medium
.
* New upstream release:
- Fixes a crash when using a customised service name. (Closes: #925577)
* New features:
- enable JACK audio backend support.
- enale D-Bus, MPRIS, and MQTT metadata and/or remote control support.
* d/shairport-sync.init: fix restart subcommand, which would appear to hang.
This only affected init systems using this script such as sysvinit, but
not systemd. (Closes: #885893)
* d/rules:
- ensure libdaemon support is always enabled. (Closes: #933144)
- configure dh_missing to fail if missing files are detected.
* d/patches/typo-fixes.patch: refresh with more typo fixes.
* Remove /usr/share/doc/shairport-sync/shairport-sync.html: the HTML is no
longer being generated correctly and is simply an HTML version of the man
page. Please refer to shairport-sync(7) instead.
Checksums-Sha1:
01616d8c2368b03bf0d6fe78761c8953278bbe43 2360 shairport-sync_3.3.2-1.dsc
dce7d102538d34b0f229bc10d011be884ae49a95 411875
shairport-sync_3.3.2.orig.tar.gz
a24effca09610e07c4d07b2a0986dd95d8408d67 17276
shairport-sync_3.3.2-1.debian.tar.xz
Checksums-Sha256:
1ffef460feb1429447a6837bbd26d3be943e8a5fc6632fa259a23886eb078b1c 2360
shairport-sync_3.3.2-1.dsc
a8f580fa8eb71172f6237c0cdbf23287b27f41f5399f5addf8cd0115a47a4b2b 411875
shairport-sync_3.3.2.orig.tar.gz
620f27afc2d11390d97f0abccfcfd05034ad574c26ad701b7fbbbe9cff629731 17276
shairport-sync_3.3.2-1.debian.tar.xz
Files:
ee753f15932be2a589bed3693bd961c7 2360 sound optional shairport-sync_3.3.2-1.dsc
80278eed6bb1391bcbafe80c0e566d1b 411875 sound optional
shairport-sync_3.3.2.orig.tar.gz
b906e67a8053135caa5d62e45d4852a1 17276 sound optional
shairport-sync_3.3.2-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQKlBAEBCgCPFiEEakxNgo23DDPFqbsY1o29Dt2gqWQFAl07x9ZfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDZB
NEM0RDgyOERCNzBDMzNDNUE5QkIxOEQ2OERCRDBFRERBMEE5NjQRHGJvb3RjQGRl
Ymlhbi5vcmcACgkQ1o29Dt2gqWRU0w//e5Fis6jwedJ7DkiJbwDYDFASqf2r3dSr
GROUSLDEx9UhEVR5hXpeF6KVlv3tz6Ah9/fLbKX6PkbJYGinf4JV54GQoZIxC87D
MNd9KYlsdtnjIiW6NTrbjCqLF976i3KTPKMB7MQijOEfwtMweIODC23TNY8+n+Nl
8A4Anuo8VB0PuHvJp60R93pmaImJLFfwIt3ah8Ssx9/7mpVsUF/ppGIEHTIGwAsq
RAPdihtK+DC8eu8JXZQp5V+Ts63qrVaxDlpvHc8ITsX6u7wJW/raKFtTuDe3Ni/u
b9vcDcLGdDQqLI67/GAUltxoWPocFbtaw9WSCG5mm7XLUHkIGA9n120UlYdoq9Yt
0vTq1vZw2nSXs2bxiMyxU52tLrp4C6ongnBknpVWyoUWbXRwUmcQB6Ddevy+CVtc
E7R/ZKw/AA6roz21MLgtjhf2dvllThRru0fqPswLbooXWk35ELsXVV7B6nBAj77E
BJaLwWrSkZqA/OgMpBhkVptMUoqjFjJf6JNvObxI7gUt0ho6uKpTnyH15i2r6kx5
z2CxZP9+cSOsHWcyEyUkGiXj30cl2EQgKBSMd2jJbecNjduze9MOMrDOmo28VIWm
z0KZZlrbT6OFD83+nWJiowfJ77/BRlZ/lV0rCk42itSzJurkATZ+ZP3v4ozwUW1h
L4HNmzTIZbI=
=M/RY
-----END PGP SIGNATURE-----
--- End Message ---