Your message dated Mon, 27 Apr 2015 14:20:35 +0200
with message-id <[email protected]>
and subject line Re: Bug#783462: systemd-sysctl does not apply config at boot
has caused the Debian Bug report #783462,
regarding systemd-sysctl does not apply config 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.)
--
783462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783462
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-17
Severity: normal
Hi,
I have a custom config in /etc/sysctl.d/, but systemd
does not seem to apply it at boot:
[ ~ ] $ sudo sysctl -a | grep sack
net.ipv4.tcp_dsack = 1
net.ipv4.tcp_sack = 1
It says that the service run fine though:
[ ~ ] $ systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
Active: active (exited) since lun 2015-04-27 10:06:48 CEST; 23min ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 444 ExecStart=/lib/systemd/systemd-sysctl (code=exited,
status=0/SUCCESS)
Main PID: 444 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/systemd-sysctl.service
However when I rerun it when the system is running, my custom config
*is* applied:
[ ~ ] $ sudo systemctl stop systemd-sysctl.service
[ ~ ] $ sudo systemctl start systemd-sysctl.service
[ ~ ] $ sudo sysctl -a | grep sack
net.ipv4.tcp_dsack = 1
net.ipv4.tcp_sack = 0
I suspect that it may have to do with the fact that I have a LUKS-encrypted
main partition.
Still, /etc/ as at the same partition as / and so if systemd-sysctl executes
then /etc/
should be available.
I think I'll solve it by manually adding dependency of systemd-sysctl to some
later target,
but I think that there still is a bug.
Cheers,
Tomasz
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-6
ii libc6 2.19-18
ii libcap2 1:2.24-8
ii libcap2-bin 1:2.24-8
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.3-2
ii libkmod2 20-1
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-17
ii mount 2.25.2-6
ii sysv-rc 2.88dsf-59
ii udev 215-17
ii util-linux 2.25.2-6
Versions of packages systemd recommends:
ii dbus 1.8.16-1
ii libpam-systemd 215-17
Versions of packages systemd suggests:
pn systemd-ui <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On 27/04/15 14:11, Michael Biebl wrote:
> Am 27.04.2015 um 10:48 schrieb Tomasz Buchert:
> > (cont.)
> > as suspected adding "After=network.target" in
> > /lib/systemd/system/systemd-sysctl.service
> > actually helps
>
> It seems more likely, that /etc/init.d/networking changes the sysctl
> knobs when it starts.
> Can you investigate, if this is the case?
>
Ok, thanks to your suggestion I got it:
[ /etc ] $ sudo grep -r tcp_sack
sysctl.d/local.conf:net.ipv4.tcp_sack = 0
ufw/sysctl.conf:# normally allowing tcp_sack is ok, but if going through
OpenBSD 3.8 RELEASE or
ufw/sysctl.conf:net/ipv4/tcp_sack=1
So it is a conflict with ufw firewall.
Sorry for traffic,
Tomasz
signature.asc
Description: Digital signature
--- End Message ---
