Your message dated Sun, 28 Jan 2018 22:11:32 +0000
with message-id <e1efvai-0008mt...@fasolo.debian.org>
and subject line Bug#887343: fixed in systemd 236-4
has caused the Debian Bug report #887343,
regarding systemd-timesyncd does not start with DynamicUser=yes
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.)
--
887343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 236-3
Severity: normal
File: systemd-timesyncd.service
Hi,
on a newly installed (without installing recommends) system¹ systemd-timesyncd
fails to start like
$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-01-15 08:58:10 UTC; 8min
ago
Docs: man:systemd-timesyncd.service(8)
Process: 563 ExecStart=/lib/systemd/systemd-timesyncd (code=exited,
status=1/FAILURE)
Main PID: 563 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Jan 15 08:58:10 foo systemd[1]: systemd-timesyncd.service: Service has no
hold-off time, scheduling restart.
Jan 15 08:58:10 foo systemd[1]: systemd-timesyncd.service: Scheduled restart
job, restart counter is at 5.
Jan 15 08:58:10 foo systemd[1]: Stopped Network Time Synchronization.
Jan 15 08:58:10 foo systemd[1]: systemd-timesyncd.service: Start request
repeated too quickly.
Jan 15 08:58:10 foo systemd[1]: systemd-timesyncd.service: Failed with result
'exit-code'.
Jan 15 08:58:10 foo systemd[1]: Failed to start Network Time Synchronization.
and the log has
Jan 15 08:58:09 foo systemd-timesyncd[563]: Cannot resolve user name
systemd-timesync: No such process
Jan 15 08:58:10 foo systemd[1]: systemd-timesyncd.service: Main process exited,
code=exited, status=1/FAILURE
Jan 15 08:58:10 foo systemd[1]: systemd-timesyncd.service: Failed with result
'exit-code'.
Jan 15 08:58:10 foo systemd[1]: Failed to start Network Time Synchronization.
This seems to be caused by the fact that libnss-systemd is not a hard
dependency of systemd. I'm not sure what the best solution is? Having a
service that is enabled by fails to start looks weird though. Maybe
providing a static user isn't that bad?
This might be the same as:
https://lists.debian.org/msgid-search/cao6p2qqx7zghfxgpdpqfzcasnz2wv+b0rntfhkvrxtfbfp7...@mail.gmail.com
Cheers,
-- Guido
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 236-4
We believe that the bug you reported is fixed in the latest version of
systemd, 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 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <bi...@debian.org> (supplier of updated systemd 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: SHA256
Format: 1.8
Date: Sun, 28 Jan 2018 22:29:32 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump systemd-tests libpam-systemd libnss-myhostname
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 236-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
libnss-myhostname - nss module providing fallback resolution for the current
hostname
libnss-mymachines - nss module to resolve hostnames for local container
instances
libnss-resolve - nss module to resolve names via systemd-resolved
libnss-systemd - nss module providing dynamic user and group name resolution
libpam-systemd - system and service manager - PAM module
libsystemd-dev - systemd utility library - development files
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
systemd - system and service manager
systemd-container - systemd container/nspawn tools
systemd-coredump - tools for storing and retrieving coredumps
systemd-journal-remote - tools for sending and receiving remote journal logs
systemd-sysv - system and service manager - SysV links
systemd-tests - tests for systemd
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 882629 887343
Changes:
systemd (236-4) unstable; urgency=medium
.
[ Felipe Sateler ]
* Allow systemd-timesyncd to start when libnss-systemd is not installed.
Pick upstream patch requiring the existence of the systemd-timesync user
only when running as root, which is not the case for the system unit.
(Closes: #887343)
.
[ Nicolas Braud-Santoni ]
* debian/copyright: Refer to the CC0 license file (Closes: #882629)
.
[ Michael Biebl ]
* Add Build-Depends on python3-evdev <!nocheck>
This is used by hwdb/parse_hwdb.py to perform additional validation on
hwdb files.
Checksums-Sha1:
ccde0477d32387a89140ced3892191b7b1b72ed8 4861 systemd_236-4.dsc
c8c25854dffc5441fb6dc735141cc6a30b94885c 135368 systemd_236-4.debian.tar.xz
ed3b3dbd84a13bdbbfe7c2ed95d3fb4b1e0ad523 9976 systemd_236-4_source.buildinfo
Checksums-Sha256:
11ff5ca35160b5ab614f774c553c7641d0052a9e30976fc5eebc24c56384e23a 4861
systemd_236-4.dsc
2d5208003e1716b9472f17f52adff1f0345e65d620e90f4d4f59279b6d71e7bc 135368
systemd_236-4.debian.tar.xz
b08065cb0c5124953f5ee3754b082bfeee0b640981c670e16052a47a24641d08 9976
systemd_236-4_source.buildinfo
Files:
480b5f8a9b5dab540a08f3a5cffb5c48 4861 admin optional systemd_236-4.dsc
83b43fbafe3b2ea0374139f486461fca 135368 admin optional
systemd_236-4.debian.tar.xz
d3334d114611763c878d2e25de0b3079 9976 admin optional
systemd_236-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlpuRHEACgkQauHfDWCP
ItyKcg//eR+KgnUsSFrBgjJu/kshN6CC4hWgFELQHxvPPSyRl08C4+VCfgs7oT3w
PmkMU82XiZwyZRHrP4IqzGhXUsH8vEclbGe1beGDtH7dW3t6jmpAewicz1jIX5Yn
z4PkhpKJdv/wNNmdoxiubpl1tmr8oXA63tiqzV/DdDw3yvzWLG5sjTroLqS0hdpS
Dbdtm/BfI7SbpnN97OSyNWwMaokC09H4zfP7TOGiVFL4JBi6f89/owlBAveSlm+3
XxtT3nejIJjHXtJtfZGA6oHm8K1+dSqgTjOA/0egJCKsbsZxSEwERAnI8FeaqMHt
+OfR7ua7GjbjZAWzlXG6XcTUx/TD3HDAKQxijkFiBvKhWu9hTbJBJkt3tgaq/hUJ
ZJQYQ4gYVdiQ/vxRRdHTVnjMrZY8GwFdTHv0X9HN1LkOfJLdakKMhZSOIHgwEgxP
0wz5exkEC5DD/IyjGSsYozYng8+ogPRUiZeEWiVCno8yywd3izJuKlHsOfxufugF
KX2V46HpLyaU8wTcSpUBgU/VTdqHkPZV/Ay/MBPlrTXXfBnofVQiUC0RYenKDMgP
OS/zRWcQhne3aRWjiLIggAvMdQ97JsVoNtU1ThtJ3HcVozCoXITRVgqLhDUwpIWZ
p/JqYGyiFFcV2WbAUAK0z+naGlBpml2gCGFfDaW1vlwD49Azm2E=
=a81i
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
