Your message dated Fri, 24 May 2019 08:48:50 +0200
with message-id <[email protected]>
and subject line Re: Bug#929462: systemd-journal-remote: systemd-journal-upload
user missing
has caused the Debian Bug report #929462,
regarding systemd-journal-remote: systemd-journal-upload user missing
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.)
--
929462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929462
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd-journal-remote
Version: 241-3
Severity: grave
Justification: renders package unusable
Tags: newcomer
Dear Maintainer,
we are maintaining a Debian live image that uses systemd-journal-remote to
send log files to a log collector. The systemd-journal-upload unit fails
to start on buster:
May 22 07:23:34 ceph06 systemd[1]: Starting Journal Remote Upload Service...
May 22 07:23:34 ceph06 systemd[40869]: systemd-journal-upload.service: Failed
to determine user credentials: No such process
May 22 07:23:34 ceph06 systemd[40869]: systemd-journal-upload.service: Failed
at step USER spawning /usr/local/bin/update-journal-configuration.sh: No such
process
It tries to run as user systemd-journal-upload which seems to be missing.
Fix is to add the user, mkdir /var/lib/systemd/journal-upload and chown
the dir to the new user.
It's entirely possible that we are doing something wrong when creating the
live image, but it's just a standard debootstrap followed by apt-get install
systemd-journal-upload in a chroot.
Virtually identical setups works for Stretch.
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd-journal-remote depends on:
ii adduser 3.118
ii libc6 2.28-10
ii libcurl3-gnutls 7.64.0-3
ii libgnutls30 3.6.6-2
ii libmicrohttpd12 0.9.62-1
ii systemd 241-3
systemd-journal-remote recommends no packages.
systemd-journal-remote suggests no packages.
-- Configuration Files:
/etc/systemd/journal-upload.conf changed [not included]
-- no debconf information
Thanks,
Paul Emmerich
--- End Message ---
--- Begin Message ---
Am 24.05.19 um 08:07 schrieb Michael Biebl:
> May 22 07:23:34 ceph06 systemd[40869]: systemd-journal-upload.service: Failed
> to determine user credentials: No such process
> May 22 07:23:34 ceph06 systemd[40869]: systemd-journal-upload.service: Failed
> at step USER spawning /usr/local/bin/update-journal-configuration.sh: No such
> process
Oh, this does not look like the default systemd-journal-upload.service:
/usr/local/bin/update-journal-configuration.sh
I bet you have an (outdate) copy of systemd-journal-upload.service in
/etc/systemd/system which does not use DynamicUser=true
Please update your copy systemd-journal-upload.service accordingly.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
