FS#51522 - systemd-sysctl.service failed at start

Attached to Project: Arch Linux
Opened by Juan Simón (j1simon) - Monday, 24 October 2016, 17:11 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 24 October 2016, 22:55 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Every time I start Arch Linux, systemd-sysctl.service failed.

$ sudo systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since lun 2016-10-24 19:00:42 CEST; 8min ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 301 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
Main PID: 301 (code=exited, status=1/FAILURE)

If I execute "sudo /usr/lib/systemd/systemd-sysctl" it doesn't fail.

If I execute "sudo sysctl --system" it doesn't fail:

$ sudo sysctl --system
* Applying /etc/sysctl.d/40-disable-ipv6.conf ...
net.ipv6.conf.all.disable_ipv6 = 1
* Applying /usr/lib/sysctl.d/50-coredump.conf ...
kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %e
* Applying /usr/lib/sysctl.d/50-default.conf ...
kernel.sysrq = 16
kernel.core_uses_pid = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.all.promote_secondaries = 1
net.core.default_qdisc = fq_codel
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
* Applying /etc/sysctl.d/50-tcp_fastopen_key.conf ...
net.ipv4.tcp_fastopen_key = e9cf0c8a-31858f2e-dd468838-69443a3b
* Applying /etc/sysctl.d/99-local.conf ...
fs.inotify.max_user_watches = 524288
kernel.sysrq = 1
net.core.default_qdisc = pfifo_fast
net.core.netdev_max_backlog = 9000
net.core.rmem_max = 11960320
net.core.somaxconn = 512
net.core.wmem_max = 11960320
net.ipv4.ipfrag_high_thresh = 544288
net.ipv4.ipfrag_low_thresh = 393216
net.ipv4.tcp_dsack = 0
net.ipv4.tcp_fack = 0
net.ipv4.tcp_fastopen = 3
net.ipv4.tcp_fin_timeout = 30
net.ipv4.tcp_keepalive_intvl = 20
net.ipv4.tcp_keepalive_probes = 4
net.ipv4.tcp_keepalive_time = 1000
net.ipv4.tcp_max_syn_backlog = 8192
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_retries2 = 6
net.ipv4.tcp_rmem = 4096 524288 11960320
net.ipv4.tcp_sack = 0
net.ipv4.tcp_synack_retries = 3
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_wmem = 4096 524288 11960320
vm.vfs_cache_pressure = 50
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 24 October 2016, 22:55 GMT
Reason for closing:  Not a bug
Additional comments about closing:  User requested: user error
Comment by Juan Simón (j1simon) - Monday, 24 October 2016, 17:12 GMT
linux-ck-nehalem 4.8.4-1

systemd 231
+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
Comment by Dave Reisner (falconindy) - Monday, 24 October 2016, 17:34 GMT
This implies some sort of ordering dependency. You'll need to narrow down the specific setting. Probably running `journalctl _PID=301` will get you something interesting.
Comment by Juan Simón (j1simon) - Monday, 24 October 2016, 18:27 GMT
Thanks for the advise.
'journalctl _PID=301' was very useful.

Loading...