Your message dated Tue, 27 May 2014 19:50:13 +0200
with message-id <[email protected]>
and subject line Re: Bug#749330: systemd: The sysctl service is not started
correctly at boot
has caused the Debian Bug report #749330,
regarding systemd: The sysctl service is not started correctly at boot
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.)
--
749330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749330
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 208-1
Severity: normal
Dear Maintainer,
I have a file
> /etc/sysctl.d/98-save-power.conf
containing the line
> vm.dirty_writeback_centisecs = 1500
which is used as an example to describe the bug in the following.
After boot,
> cat /proc/sys/vm/dirty_writeback_centisecs
returns
> 500,
although
> systemctl status systemd-sysctl.service
returns
> systemd-sysctl.service - Apply Kernel Variables
> Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
> Active: active (exited) since Mo 2014-05-26 14:22:00 CEST; 4min 49s ago
> Docs: man:systemd-sysctl.service(8)
> man:sysctl.d(5)
> Process: 295 ExecStart=/lib/systemd/systemd-sysctl (code=exited,
> status=0/SUCCESS)
> Main PID: 295 (code=exited, status=0/SUCCESS)
>
> Mai 26 14:22:00 mmm systemd[1]: Started Apply Kernel Variables.
> Mai 26 14:24:48 mmm systemd[1]: Started Apply Kernel Variables.
i.e. the service seems to be loaded correctly.
After manually executing
> systemctl restart systemd-sysctl.service
> cat /proc/sys/vm/dirty_writeback_centisecs
the result is
> 1500.
Executing
> systemctl status systemd-sysctl.service
again results in the same information as before (beside the dates)
> systemd-sysctl.service - Apply Kernel Variables
> Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
> Active: active (exited) since Mo 2014-05-26 14:27:27 CEST; 15s ago
> Docs: man:systemd-sysctl.service(8)
> man:sysctl.d(5)
> Process: 2531 ExecStart=/lib/systemd/systemd-sysctl (code=exited,
> status=0/SUCCESS)
> Main PID: 2531 (code=exited, status=0/SUCCESS)
I wasn't sure if this is a systemd problem, but as the printed status does not
change although the state of the system clearly changed, I do not have another
explanation.
Please note, that this problem also occured with versions 204-8 and 204-10. I
think it worked on some reboots, so a race condition might be involved, but I
cannot get it to work anymore during the last reboots, so this might be
incorrect.
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'stable'), (500,
'testing-proposed-updates'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-1
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53
ii libacl1 2.2.52-1
ii libaudit1 1:2.3.6-1
ii libblkid1 2.20.1-5.7
ii libc6 2.18-7
ii libcap2 1:2.22-1.2
ii libcap2-bin 1:2.22-1.2
ii libcryptsetup4 2:1.6.4-4
ii libdbus-1-3 1.8.2-1
ii libgcrypt11 1.5.3-4
ii libkmod2 16-2
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3
ii libselinux1 2.3-1
ii libsystemd-daemon0 208-1
ii libsystemd-journal0 208-1
ii libsystemd-login0 208-1
ii libudev1 204-8
ii libwrap0 7.6.q-25
ii sysv-rc 2.88dsf-53
ii udev 204-8
ii util-linux 2.20.1-5.7
Versions of packages systemd recommends:
ii libpam-systemd 208-1
Versions of packages systemd suggests:
pn systemd-ui <none>
-- Configuration Files:
/etc/systemd/system.conf changed:
[Manager]
DefaultControllers=cpu memory blkio
-- no debconf information
[OVERRIDDEN] /etc/systemd/system/vsftpd.service → /lib/systemd/system/vsftpd.service
Files /lib/systemd/system/vsftpd.service and /etc/systemd/system/vsftpd.service are identical
[OVERRIDDEN] /run/systemd/system/session-1.scope.d/90-SendSIGHUP.conf → /run/systemd/system/session-c1.scope.d/90-SendSIGHUP.conf
Files /run/systemd/system/session-c1.scope.d/90-SendSIGHUP.conf and /run/systemd/system/session-1.scope.d/90-SendSIGHUP.conf are identical
[OVERRIDDEN] /run/systemd/system/session-1.scope.d/90-TimeoutStopUSec.conf → /run/systemd/system/session-c1.scope.d/90-TimeoutStopUSec.conf
Files /run/systemd/system/session-c1.scope.d/90-TimeoutStopUSec.conf and /run/systemd/system/session-1.scope.d/90-TimeoutStopUSec.conf are identical
[OVERRIDDEN] /run/systemd/system/session-1.scope.d/90-KillMode.conf → /run/systemd/system/session-c1.scope.d/90-KillMode.conf
Files /run/systemd/system/session-c1.scope.d/90-KillMode.conf and /run/systemd/system/session-1.scope.d/90-KillMode.conf are identical
[OVERRIDDEN] /run/systemd/system/session-1.scope.d/90-After-systemd-user-sessions\x2eservice.conf → /run/systemd/system/session-c1.scope.d/90-After-systemd-user-sessions\x2eservice.conf
Files /run/systemd/system/session-c1.scope.d/90-After-systemd-user-sessions\x2eservice.conf and /run/systemd/system/session-1.scope.d/90-After-systemd-user-sessions\x2eservice.conf are identical
[OVERRIDDEN] /run/systemd/system/session-1.scope.d/90-Description.conf → /run/systemd/system/session-c1.scope.d/90-Description.conf
--- /run/systemd/system/session-c1.scope.d/90-Description.conf 2014-05-26 14:22:02.461714724 +0200
+++ /run/systemd/system/session-1.scope.d/90-Description.conf 2014-05-26 14:22:07.373714869 +0200
@@ -1,2 +1,2 @@
[Unit]
-Description=Session c1 of user lightdm
+Description=Session 1 of user pat
[OVERRIDDEN] /run/systemd/system/session-1.scope.d/90-Slice.conf → /run/systemd/system/session-c1.scope.d/90-Slice.conf
--- /run/systemd/system/session-c1.scope.d/90-Slice.conf 2014-05-26 14:22:02.461714724 +0200
+++ /run/systemd/system/session-1.scope.d/90-Slice.conf 2014-05-26 14:22:07.373714869 +0200
@@ -1,2 +1,2 @@
[Scope]
-Slice=user-117.slice
+Slice=user-1000.slice
[EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/90-SendSIGHUP.conf
[EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/90-TimeoutStopUSec.conf
[EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/90-KillMode.conf
[EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/90-After-systemd-user-sessions\x2eservice.conf
[EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/90-Description.conf
[EXTENDED] /run/systemd/system/session-1.scope → /run/systemd/system/session-1.scope.d/90-Slice.conf
[EXTENDED] /run/systemd/system/session-c1.scope → /run/systemd/system/session-c1.scope.d/90-SendSIGHUP.conf
[EXTENDED] /run/systemd/system/session-c1.scope → /run/systemd/system/session-c1.scope.d/90-TimeoutStopUSec.conf
[EXTENDED] /run/systemd/system/session-c1.scope → /run/systemd/system/session-c1.scope.d/90-KillMode.conf
[EXTENDED] /run/systemd/system/session-c1.scope → /run/systemd/system/session-c1.scope.d/90-After-systemd-user-sessions\x2eservice.conf
[EXTENDED] /run/systemd/system/session-c1.scope → /run/systemd/system/session-c1.scope.d/90-Description.conf
[EXTENDED] /run/systemd/system/session-c1.scope → /run/systemd/system/session-c1.scope.d/90-Slice.conf
19 overridden configuration files found.
systemctl-dump.txt
Description: inode/empty
==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/ssh.service
/etc/systemd/system/sshd.service
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/ssh.socket
==> /var/lib/systemd/deb-systemd-helper-enabled/lm-sensors.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/lm-sensors.service
==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket
==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/binfmt-support.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/binfmt-support.service
==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/netfilter-persistent.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/netfilter-persistent.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/lm-sensors.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/binfmt-support.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/netfilter-persistent.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/vsftpd.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/avahi-daemon.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/atd.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/atd.service
==> /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/anacron.service
==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/avahi-daemon.service
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket
/etc/systemd/system/dbus-org.freedesktop.Avahi.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.Avahi.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/pppd-dns.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/pppd-dns.service
==> /var/lib/systemd/deb-systemd-helper-enabled/vsftpd.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/vsftpd.service
--- End Message ---
--- Begin Message ---
Am 27.05.2014 19:44, schrieb Michael Biebl:
> Am 26.05.2014 20:50, schrieb Patrick Häcker:
>>>>> vm.dirty_writeback_centisecs = 1500
>>>> which is used as an example to describe the bug in the following.
>>>>
>>>> After boot,
>>>>> cat /proc/sys/vm/dirty_writeback_centisecs
>>>> returns
>>>> 500,
>>>
>>> Do you use any power management tools, like acpi-support,
>>> laptop-mode-tools or pm-utils? If so, one of those might be setting that
>>> value on ac/battery changes.
>> acpi-support and laptop-mode-tools are not installed, but pm-utils is
>> installed (version 1.4.1-14). A search through the results of
>
> See /usr/lib/pm-utils/power.d/laptop-mode
>
> I suspect if you override that file via
> sudo touch /etc/pm/power.d/laptop-mode
>
> your vm.* settings are no longer overwritten.
Specifically see
write_values 0 10 5 500
where the 4 values are assigned to vmfiles = laptop_mode dirty_ratio
dirty_background_ratio dirty_writeback_centisecs
Closing the bug report, not a bug in systemd.
It can be argued that this might be a bug in pm-utils, but then again
pm-utils is supposed to handle the power management settings.
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]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
