You are not logged in.
He all
I have set up netctl-auto on my laptop to manage wifi. This has been working for months now. But suddenly without changing anything
it started to fail every now and then on boot. I am not quire sure what causes this. The journal tells me that the interface is already up:
-- Reboot --
Aug 01 19:11:42 poseidon systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Aug 01 19:11:43 poseidon systemd[1]: netctl-auto@wlp7s0.service: Control process exited, code=exited status=1
Aug 01 19:11:44 poseidon netctl-auto[310]: The interface 'wlp7s0' is already up
Aug 01 19:11:43 poseidon systemd[1]: Failed to start Automatic wireless network connection using netctl profiles.
Aug 01 19:11:43 poseidon systemd[1]: netctl-auto@wlp7s0.service: Unit entered failed state.
Aug 01 19:11:43 poseidon systemd[1]: netctl-auto@wlp7s0.service: Failed with result 'exit-code'.
Any hints or some help on that would be highly appreciated.
Last edited by ctpfaff (2018-02-21 08:03:43)
Offline
This is one of the tragic failings of netctl; something as innocuous as the interface already being “up” causes it to fatally error.
This is also a perfect opportunity to move to a network manager that does not behave so poorly in the face of overwhelming normality. Might I recommend networkd+resolved+wpa_supplicant? It has been working wonders for me since it was available.
If you are determined to stick with netctl, then the next step is to figure out what is setting the interface “up”. The most likely thing is that another network manager is doing it for you and causing conflicts. Did you recently -Syu or anything? Can you please post the output of `systemctl status` in code blocks?
All the best,
-HG
Last edited by HalosGhost (2017-08-29 18:57:59)
Offline
He
With "nothing changed" I mean of course in the netctl configuration. Sorry for being so imprecise. Of course I changed the system around it. I updated packages and installed new ones. I will check out and read into how to use the combination of tools you suggested. However it would be really good to find out what actually is the cause of trouble now as I am curious. I am not sure. But I think there is no other network manager on my system. At least from reading through the output of "systemctl --type=service --all" does not show any. The status command does show this here (no failed units here as networking was working fine on this boot):
sysctl status
● host
State: running
Jobs: 0 queued
Failed: 0 units
Since: Tue 2017-08-29 21:27:05 CEST; 1h 2min ago
CGroup: /
├─user.slice
│ └─user-1000.slice
│ ├─user@1000.service
│ │ ├─pulseaudio.service
│ │ │ └─2841 /usr/bin/pulseaudio --daemonize=no
│ │ ├─at-spi-dbus-bus.service
│ │ │ ├─3354 /usr/lib/at-spi2-core/at-spi-bus-launcher
│ │ │ ├─6351 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
│ │ │ └─6353 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
│ │ ├─dbus.service
│ │ │ ├─1613 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
│ │ │ └─3347 /usr/lib/GConf/gconfd-2
│ │ ├─gpg-agent.service
│ │ │ └─1008 /usr/bin/gpg-agent --supervised
│ │ └─init.scope
│ │ ├─718 /usr/lib/systemd/systemd --user
│ │ └─719 (sd-pam)
│ └─session-c1.scope
│ ├─ 455 login -- user
│ ├─ 750 -zsh
│ ├─ 1036 ssh-agent
│ ├─ 2734 /bin/sh /usr/bin/startx
│ ├─ 2757 xinit /home/user/.xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -auth /tmp/serverauth.xlb7qoJnuI
│ ├─ 2758 /usr/lib/xorg-server/Xorg -nolisten tcp :0 vt1 -auth /tmp/serverauth.xlb7qoJnuI
│ ├─ 2763 xf86-video-intel-backlight-helper intel_backlight
│ ├─ 2769 i3
│ ├─ 2808 redshift
│ ├─ 2814 i3bar --bar_id=bar-0 --socket=/run/user/1000/i3/ipc-socket.2769
│ ├─ 2816 i3status
│ ├─ 5973 /usr/bin/zsh
│ ├─ 5989 cat
│ ├─10924 systemctl status
│ └─31645 -zsh
├─init.scope
│ └─1 /sbin/init
└─system.slice
├─systemd-timesyncd.service
│ └─342 /usr/lib/systemd/systemd-timesyncd
├─preload.service
│ └─348 /usr/bin/preload --foreground --verbose 1
├─dbus.service
│ └─349 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
├─system-netctl\x2dauto.slice
│ └─netctl-auto@wlp7s0.service
│ ├─450 wpa_supplicant -q -B -P /run/wpa_supplicant-wlp7s0.pid -i wlp7s0 -D nl80211,wext -c/run/netctl/wpa_supplicant-wlp7s0.conf -W
│ └─452 wpa_actiond -p /run/wpa_supplicant -i wlp7s0 -P /run/netctl/wpa_actiond-wlp7s0.pid -a /usr/lib/netctl/auto.action
├─systemd-logind.service
│ └─355 /usr/lib/systemd/systemd-logind
├─rtkit-daemon.service
│ └─2851 /usr/lib/rtkit/rtkit-daemon
├─polkit.service
│ └─2872 /usr/lib/polkit-1/polkitd --no-debug
├─system-netctl\x2difplugd.slice
│ └─netctl-ifplugd@enp9s0.service
│ └─358 /usr/bin/ifplugd -i enp9s0 -r /etc/ifplugd/netctl.action -bfIns
├─systemd-udevd.service
│ └─179 /usr/lib/systemd/systemd-udevd
├─ananicy.service
│ ├─ 359 /bin/bash /usr/bin/ananicy start
│ └─10602 sleep 15
├─spamassassin.service
│ ├─453 /usr/bin/perl -w /usr/bin/vendor_perl/spamd -l -u spamd -g spamd
│ ├─910 spamd child
│ └─916 spamd child
├─systemd-journald.service
│ └─163 /usr/lib/systemd/systemd-journald
└─dhcpcd.service
└─390 /usr/bin/dhcpcd -q -b
All the best.
Last edited by ctpfaff (2017-08-29 20:48:05)
Offline
You have dhcpcd.service enabled as well as netctl, you should only have one networking service enabled otherwise they will conflict.
Disable dhcpcd.service.
Last edited by Slithery (2017-08-29 20:49:29)
Offline
He
Thanks. That seems to be the right answer. It is working again.
All the best
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
Done
Offline