You are not logged in.
Pages: 1
For the past month or so, my systemd service for dhcpcd has been failing to properly start on boot. However, I've noticed that this only occurs on a fresh start after a shutdown. It does not occur after a reboot.
I do not use any sort of connection manager such as: NetworkManager, netctl, connman, etc.. I am only using dhcpcd via systemd.
The command I've always used to create the service is:
# systemctl enable dhcpcd@enp4s0.service
# systemctl start dhcpcd@enp4s0.service
I've found some topics related to the issue from 2-3 years back, but they don't seem to be the exact same case from what I can tell.
Here is the output of systemctl --type=service --all: http://i.imgur.com/hqBZBoP.png
Here is the output of ip link show when the service is running:
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: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff
Does anything seem off in my service list? This issue is really nagging at me, and I don't know enough about systemd or networking to isolate it.
Last edited by BlueYoshi (2015-05-17 22:50:51)
Offline
What is in the journal after it fails to start?
Not a Sysadmin issue, moving to NC...
Offline
What is in the journal after it fails to start?
Not a Sysadmin issue, moving to NC...
Just checked, and it looks like it's starting services in a strange order. "PIA" is my service to start my VPN using the https://aur.archlinux.org/packages/priv … access-vpn package. I would think dhcpcd should be starting first?
journalctl: https://bpaste.net/raw/28fe88297a78
pia.service (if relevant):
[Unit]
Description=PIA
[Service]
Type=simple
ExecStart=/usr/bin/pia
Restart=always
[Install]
WantedBy=multi-user.target
Offline
You can order services, one of the strengths of systemd over the old ways, using: After=network.target and Wants=network.target.
Offline
Also, systemd is nice in that it will tell you what's going on with the service.
You get that with
systemctl status <service>
So if you replace the <service> with your dhcpcd command, it should give you the details of that service, including enabled/disabled, success/failure, etc....
Knute
Offline
You can order services, one of the strengths of systemd over the old ways, using: After=network.target and Wants=network.target.
Thank you, that seemed to solve it and led me to a few other discoveries to fix some other systemd issues. Now there's no more red in my journalctl.
Last edited by BlueYoshi (2015-05-17 21:49:08)
Offline
Pages: 1