You are not logged in.
Hello!
After some months i switched back to netctl. I set netctl-auto for wireless and ethernet. My client is dhclient, dhcpcd is not on my system.
Now - the thing is that my connection is working most of the time. But the weird thing is that systemctl --failed always show:
● ifplugd@eth0.service loaded failed failed Daemon which acts upon network cable insertion/removal
● netctl-auto@wlan0.service loaded failed failed Automatic wireless network connection using netctl profiles
no matter if the connection is working or not.
Here is systemctl --type=service --no-pager:
UNIT LOAD ACTIVE SUB DESCRIPTION
cronie.service loaded active running Periodic Command Scheduler
dbus.service loaded active running D-Bus System Message Bus
getty@tty1.service loaded active running Getty on tty1
● ifplugd@eth0.service loaded failed failed Daemon which acts upon network cable insertion/removal
kdm.service loaded active running K Display Manager
kmod-static-nodes.service loaded active exited Create list of required static device nodes for the current
lm_sensors.service loaded active exited Initialize hardware monitoring sensors
● netctl-auto@wlan0.service loaded failed failed Automatic wireless network connection using netctl profiles
netctl-ifplugd@eth0.service loaded active running Automatic wired network connection using netctl profiles
netctl@wlan0\x2dSASO.service loaded active exited Networking for netctl profile wlan0-SASO
polkit.service loaded active running Authorization Manager
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service
systemd-backlight@backlight:acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of backlight:acpi_vide
systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight:intel_bac
systemd-backlight@leds:asus::kbd_backlight.service loaded active exited Load/Save Screen Backlight Brightness of leds:asus::kbd_back
systemd-fsck@dev-disk-by\x2duuid-2585aca7\x2d3acd\x2d4732\x2dae84\x2d5593efab8b7b.service loaded active exited File System Check on /dev/disk/by-uuid/2585aca7-3acd-4732-ae
systemd-fsck@dev-disk-by\x2duuid-9cab353d\x2d0fef\x2d423d\x2dab1c\x2d99ecd655489f.service loaded active exited File System Check on /dev/disk/by-uuid/9cab353d-0fef-423d-ab
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-rfkill@rfkill0.service loaded active exited Load/Save RF Kill Switch Status of rfkill0
systemd-rfkill@rfkill1.service loaded active exited Load/Save RF Kill Switch Status of rfkill1
systemd-rfkill@rfkill2.service loaded active exited Load/Save RF Kill Switch Status of rfkill2
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
udisks2.service loaded active running Disk Manager
ufw.service loaded active exited CLI Netfilter Manager
upower.service loaded active running Daemon for power management
user@1004.service loaded active running User Manager for UID 1004
Do you have any ideas why this failed messages come up?
thx
Last edited by Shark (2014-04-28 11:42:10)
If you have built castles in the air, your work need not be lost; that is where they should be. Now put foundations under them.
Henry David Thoreau
Registered Linux User: #559057
Offline
Your eth0 service file is not prefixed with 'netct-'. The wiki says something else. But this is just an observation, it *seems* to work okay.
Second, your interfaces are still named by the kernel. And not by the udev persistent rules. Is that okay?
Could you provide the output of the following command?
as root:
systemctl status netctl-auto@wlan0.service
systemctl status ifplugd@eth0.service
ip link show
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
Your eth0 service file is not prefixed with 'netct-'. The wiki says something else. But this is just an observation, it *seems* to work okay.
I have followed wiki. Should i renamed it?
I have reboot once again and now the "failed status" has only ifplugd service. Wlan0 is ok. I suppose the reason behind this is that i have removed one old service file of netctl.
As long as i know my networks have always been wlan0 and eth0.
systemctl status netctl-auto@wlan0.service:
● netctl-auto@wlan0.service - Automatic wireless network connection using netctl profiles
Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled)
Active: active (running) since Mon 2014-04-28 10:27:43 CEST; 3min 38s ago
Docs: man:netctl.special(7)
Process: 322 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wlan0.service
├─368 wpa_supplicant -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/run/network/wpa_supplicant_wlan0.conf -W
├─370 wpa_actiond -p /run/wpa_supplicant -i wlan0 -P /run/network/wpa_actiond_wlan0.pid -a /usr/lib/network/auto.action
└─413 dhclient -4 -q -e TIMEOUT=30 -pf /run/dhclient4-wlan0.pid wlan0
Apr 28 10:27:45 saso-laptop netctl-auto[322]: Included profile 'wlan0-mac'
Apr 28 10:27:45 saso-laptop netctl-auto[322]: Included profile 'wlan0linksys'
Apr 28 10:27:45 saso-laptop netctl-auto[322]: Included profile 'wlan0-shadow'
Apr 28 10:27:45 saso-laptop netctl-auto[322]: Included profile 'wlan0-TP-LINK_49A368'
Apr 28 10:27:45 saso-laptop netctl-auto[322]: Included profile 'wlan0-SASO'
Apr 28 10:27:46 saso-laptop dhclient[403]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Apr 28 10:27:46 saso-laptop dhclient[403]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Apr 28 10:27:46 saso-laptop dhclient[403]: DHCPOFFER from 192.168.1.1
Apr 28 10:27:46 saso-laptop dhclient[403]: DHCPACK from 192.168.1.1
Apr 28 10:27:46 saso-laptop dhclient[403]: bound to 192.168.1.100 -- renewal in 3107 seconds.
systemctl status ifplugd@eth0.service:
● ifplugd@eth0.service - Daemon which acts upon network cable insertion/removal
Loaded: loaded (/usr/lib/systemd/system/ifplugd@.service; enabled)
Active: failed (Result: exit-code) since Mon 2014-04-28 10:27:41 CEST; 4min 24s ago
Process: 320 ExecStart=/usr/bin/ifplugd-daemon %i (code=exited, status=255)
Apr 28 10:27:45 saso-laptop ifplugd-daemon[320]: Daemon failed with error condition #255. See syslog for details
ip link show:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether 90:e6:ba:16:49:24 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 00:25:d3:81:7e:0c brd ff:ff:ff:ff:ff:ff
I can't connect automatically or manaually to ethernet. In my interfaces folder i set for eth0 and wlan0 dhclient instead of dhcpcd. If i try to use ethernet via ifplugd i get this from journal -xn:
- Logs begin at Sat 2013-11-16 22:16:24 CET, end at Mon 2014-04-28 10:42:32 CEST. --
Apr 28 10:41:44 saso-laptop kernel: ATL1E 0000:03:00.0 eth0: NIC Link is Down
Apr 28 10:41:44 saso-laptop ifplugd(eth0)[2269]: Link beat lost.
Apr 28 10:41:44 saso-laptop ifplugd[321]: Link beat lost.
Apr 28 10:41:50 saso-laptop ifplugd[321]: Executing '/etc/ifplugd/netctl.action eth0 down'.
Apr 28 10:41:50 saso-laptop ifplugd[321]: Program execution failed, return value is 1.
Apr 28 10:41:55 saso-laptop ifplugd(eth0)[2269]: Executing '/etc/ifplugd/ifplugd.action eth0 down'.
Apr 28 10:41:55 saso-laptop ifplugd(eth0)[2269]: Program execution failed, return value is 1.
Apr 28 10:42:12 saso-laptop kernel: [UFW BLOCK] IN=wlan0 OUT= MAC=01:00:5e:00:00:01:f8:d1:11:43:f2:4a:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32
Apr 28 10:42:32 saso-laptop systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Apr 28 10:42:32 saso-laptop systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
Last edited by Shark (2014-04-28 08:53:39)
If you have built castles in the air, your work need not be lost; that is where they should be. Now put foundations under them.
Henry David Thoreau
Registered Linux User: #559057
Offline
Yeah, rename the service file and try again please.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
I have renamed it but the problem still persist. Here is the journalctl -xn:
-- Logs begin at Sat 2013-11-16 22:16:24 CET, end at Mon 2014-04-28 12:56:05 CEST. --
Apr 28 12:56:05 saso-laptop ifplugd[7974]: client: Reading profile 'wlan0-SASO'
Apr 28 12:56:05 saso-laptop ifplugd[7974]: client: Reading profile 'eth0-domace'
Apr 28 12:56:05 saso-laptop ifplugd[7974]: client: Starting network profile 'eth0-domace'...
Apr 28 12:56:05 saso-laptop dhclient[8259]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Apr 28 12:56:05 saso-laptop dhclient[8259]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Apr 28 12:56:05 saso-laptop dhclient[8259]: DHCPOFFER from 10.143.64.1
Apr 28 12:56:05 saso-laptop dhclient[8259]: DHCPACK from 10.143.64.1
Apr 28 12:56:05 saso-laptop dhclient[8259]: bound to xx.xx.xx.xx -- renewal in 989908 seconds.
Apr 28 12:56:05 saso-laptop ifplugd[7974]: client: Started network profile 'eth0-domace'
Apr 28 12:56:05 saso-laptop ifplugd[7974]: Program executed successfully
If you have built castles in the air, your work need not be lost; that is where they should be. Now put foundations under them.
Henry David Thoreau
Registered Linux User: #559057
Offline
Ok, here is the thing. "Problem" solved. When i was trying ethernet my router was up and so i was connected to touter while i was trying to connect to ethernet. So when i disconnect from router my ethernet started to work just fine.
Thanks for the help.
If you have built castles in the air, your work need not be lost; that is where they should be. Now put foundations under them.
Henry David Thoreau
Registered Linux User: #559057
Offline