You are not logged in.
hi,
since last kernel's upgrade
$ uname -r
4.20.0-arch1-1-ARCH
nmap spitted warnings
# nmap -sn -PR -oG - 192.168.1.1
# Nmap 7.70 scan initiated Tue Jan 1 17:30:58 2019 as: nmap -sn -PR -oG - 192.168.1.1
WARNING: eth_send of ARP packet returned -1 rather than expected 42 (errno=22: Invalid argument)
WARNING: eth_send of ARP packet returned -1 rather than expected 42 (errno=22: Invalid argument)
# Nmap done at Tue Jan 1 17:30:58 2019 -- 1 IP address (0 hosts up) scanned in 0.49 seconds
so I downgraded the kernel to linux-4.19.9.arch1-1-x86_64
pacman -U /var/cache/pacman/pkg/linux-4.19.9.arch1-1-x86_64.pkg.tar.xz
, but then at boot I've got this error : failed to start Apply Kernel Variables
what did I miss ?
Last edited by N_BaH (2019-01-01 20:21:06)
Offline
maybe mkinicpio -p linux?
Offline
it looks like pacman does by itself :
(1/3) Updating linux module dependencies...
(2/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.19.9-arch1-1-ARCH
-> Running build hook: [base]
...
BTW,
# 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 Tue 2019-01-01 19:00:06 CET; 2min 35s ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 273 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
Main PID: 273 (code=exited, status=1/FAILURE)
janv. 01 19:00:05 android-e895142523210972 systemd[1]: Starting Apply Kernel Variables...
janv. 01 19:00:06 android-e895142523210972 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
janv. 01 19:00:06 android-e895142523210972 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
janv. 01 19:00:06 android-e895142523210972 systemd[1]: Failed to start Apply Kernel Variables.
Last edited by N_BaH (2019-01-01 18:03:41)
Offline
What variable is it failing to set? The locations for the files it sources for variables from are listed in the Docs entry of the output you posted.
See `man 8 sysctl` to check set the variables manually.
Edit:
or try
# SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-sysctl
Last edited by loqs (2019-01-01 19:00:27)
Offline
it seems to be coming from /etc/sysctl.d/99-sysctl.conf, which was containing a single 1, who is told to be not an assignment.
this half solves the problem, because nmap still outputs warning as I've upgraded kernel "back" to 4.2.0.0
do I open a new thread for it?
Last edited by N_BaH (2019-01-01 19:22:23)
Offline
See https://bugs.archlinux.org/task/61219 for the nmap issue.
Offline
ok, I'll keep an eye on that.
thank you.
Offline
as stated at the end of nmap bug report, upgrading to kernel 4.20.1 solved the issue.
Offline