Your message dated Sat, 23 Jun 2018 11:06:17 +0200
with message-id <[email protected]>
and subject line Re: systemd-setup-tmpfiles startup error when /srv is on
read-only fs
has caused the Debian Bug report #868159,
regarding systemd-setup-tmpfiles startup error when /srv is on read-only fs
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.)
--
868159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868159
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 233-10
Severity: normal
When / is placed on read-only fs and therefore /srv is read-only during startup
the following error occures:
localhost systemd-tmpfiles[570]: Unable to fix SELinux security
context of /srv: Read-only file system
I tried remounting / rw and executing 'restorecon /srv' but it didn't help -
systemd wants to change the context during startup anyway.
As this is not really an error and does not affect system functionality in any
way this should not be treated as error but as a warning.
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (1000, 'testing'), (50, 'unstable'), (20, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to C.UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-3
ii libaudit1 1:2.7.7-1+b1
ii libblkid1 2.29.2-1
ii libc6 2.24-12
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-4
ii libgcrypt20 1.7.8-1
ii libgpg-error0 1.27-3
ii libidn11 1.33-1
ii libip4tc0 1.6.1-2
ii libkmod2 24-1
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.2+b1
ii libmount1 2.29.2-1
ii libpam0g 1.1.8-3.6
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3+b2
ii libsystemd0 233-10
ii mount 2.29.2-1
ii procps 2:3.3.12-3
ii util-linux 2.29.2-1
Versions of packages systemd recommends:
ii dbus 1.10.20-1
ii libpam-systemd 233-10
Versions of packages systemd suggests:
ii policykit-1 0.105-18
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.130
ii udev 233-9
-- Configuration Files:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd [Errno 13] Permission
denied: '/etc/dhcp/dhclient-exit-hooks.d/timesyncd'
/etc/systemd/journald.conf changed:
[Journal]
Storage=volatile
Compress=no
SplitMode=none
RateLimitIntervalSec=30s
RateLimitBurst=10000
ForwardToConsole=yes
ForwardToWall=no
TTYPath=/dev/tty3
MaxLevelStore=debug
MaxLevelSyslog=debug
MaxLevelKMsg=debug
MaxLevelConsole=warning
/etc/systemd/logind.conf changed:
[Login]
NAutoVTs=2
ReserveVT=2
KillUserProcesses=yes
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore
PowerKeyIgnoreInhibited=no
SuspendKeyIgnoreInhibited=no
HibernateKeyIgnoreInhibited=no
LidSwitchIgnoreInhibited=no
IdleAction=ignore
/etc/systemd/resolved.conf changed:
[Resolve]
LLMNR=no
DNSStubListener=no
-- no debconf information
Content-Disposition: attachment; filename="fstab"
/dev/mapper/test-root / ext4
noatime,nodiratime,nodev,ro 0 0
/dev/mapper/test-var /var ext4
noatime,nodiratime,nodev 0 0
PARTLABEL=test-efi /boot/efi vfat
noauto,umask=0077,ro,nodev,nosuid,noexec 0 0
/dev/mapper/test-home /home ext4
noatime,nodiratime,nodev,nosuid 0 0
/dev/mapper/test-swap none swap sw
0 0
tmpfs /tmp tmpfs
noatime,nodiratime,nodev,nosuid,noexec,size=15%,mode=1777,rootcontext=system_u:object_r:tmp_t:s0,fscontext=system_u:object_r:tmp_t:s0
0 0
tmpfs /var/tmp tmpfs
noatime,nodiratime,nodev,nosuid,noexec,size=15%,mode=1777,rootcontext=system_u:object_r:tmp_t:s0,fscontext=system_u:object_r:tmp_t:s0
0 0
--- End Message ---
--- Begin Message ---
Version: 239-1
On Wed, 12 Jul 2017 14:02:57 +0000 Alexander Barinov
<[email protected]> wrote:
> Package: systemd
> Version: 233-10
> Severity: normal
>
> When / is placed on read-only fs and therefore /srv is read-only during
> startup
> the following error occures:
> localhost systemd-tmpfiles[570]: Unable to fix SELinux security
> context of /srv: Read-only file system
> I tried remounting / rw and executing 'restorecon /srv' but it didn't help -
> systemd wants to change the context during startup anyway.
> As this is not really an error and does not affect system functionality in any
> way this should not be treated as error but as a warning.
>
This is supposed to be fixed in v239, closing the bug report accordingly.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
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
