FS#37074 - [systemd] some services depending on network.target fail to start after upgrade to systemd 207

Attached to Project: Arch Linux
Opened by Radu Potop (wooptoo) - Thursday, 26 September 2013, 14:10 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 26 September 2013, 19:59 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

After upgrading to systemd 207 some services that depend on network connectivity fail to start:


For example minidlna:

---
Sep 26 16:39:42 blue systemd[1]: Starting minidlna server...
Sep 26 16:39:42 blue minidlnad[458]: [2013/09/26 16:39:42] minidlna.c:528: No MAC address found. Falling back to generic UUID.
Sep 26 16:39:42 blue minidlnad[458]: [2013/09/26 16:39:42] minidlna.c:927: fatal: No IP address automatically detected!
Sep 26 16:39:42 blue systemd[1]: minidlna.service: control process exited, code=exited status=255
Sep 26 16:39:42 blue systemd[1]: Failed to start minidlna server.
---

No MAC address found? wtf?


Or transmission:

---
Sep 26 16:39:42 blue systemd[1]: Starting Transmission BitTorrent Daemon...
Sep 26 16:39:42 blue systemd[1]: Started Transmission BitTorrent Daemon.
Sep 26 16:39:42 blue transmission-daemon[446]: sendto: Network is unreachable
Sep 26 16:39:44 blue transmission-daemon[446]: [16:39:44.718] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:78)
Sep 26 16:39:44 blue transmission-daemon[446]: [16:39:44.719] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:89)
---

Network is unreachable. This one does start but it's not accepting any connections.


I use dhcpcd@eth0 service for network connectivity and the journal output seems fine:

---
Sep 26 16:39:38 blue systemd[1]: Starting dhcpcd on eth0...
Sep 26 16:39:38 blue dhcpcd[274]: version 6.0.5 starting
Sep 26 16:39:38 blue dhcpcd[274]: eth0: waiting for carrier
Sep 26 16:39:38 blue dhcpcd[274]: eth0: carrier acquired
Sep 26 16:39:38 blue dhcpcd[274]: eth0: soliciting an IPv6 router
Sep 26 16:39:38 blue dhcpcd[274]: eth0: rebinding lease of 192.168.1.2
Sep 26 16:39:40 blue dhcpcd[274]: eth0: Router Advertisement from fe80::6666:b3ff:fe9d:41bc
Sep 26 16:39:40 blue dhcpcd[274]: eth0: soliciting a DHCPv6 lease
Sep 26 16:39:40 blue dhcpcd[274]: eth0: deleted address fddf:a541:a2d5:0:222:15ff:fe95:8ca1/64
Sep 26 16:39:41 blue dhcpcd[274]: eth0: ADV 2a02:2f07:d010:3b00::e23/64 from fe80::6666:b3ff:fe9d:41bc
Sep 26 16:39:41 blue dhcpcd[274]: eth0: REPLY6 received from fe80::6666:b3ff:fe9d:41bc
Sep 26 16:39:41 blue dhcpcd[274]: eth0: adding address 2a02:2f07:d010:3b00::e23/64
Sep 26 16:39:41 blue dhcpcd[274]: eth0: renew in 1800 seconds, rebind in 2880 seconds
Sep 26 16:39:42 blue systemd[1]: Started dhcpcd on eth0.
Sep 26 16:39:43 blue dhcpcd[443]: eth0: leased 192.168.1.2 for 86400 seconds
Sep 26 16:39:43 blue dhcpcd[443]: eth0: adding host route to 192.168.1.2 via 127.0.0.1
Sep 26 16:39:43 blue dhcpcd[443]: eth0: adding route to 192.168.1.0/24
Sep 26 16:39:43 blue dhcpcd[443]: eth0: adding default route via 192.168.1.1
Sep 26 16:52:38 blue dhcpcd[443]: eth0: Router Advertisement from fe80::6666:b3ff:fe9d:41bc
Sep 26 16:52:38 blue dhcpcd[443]: eth0: fe80::6666:b3ff:fe9d:41bc: router expired
Sep 26 16:52:41 blue dhcpcd[443]: eth0: Router Advertisement from fe80::6666:b3ff:fe9d:41bc
Sep 26 16:52:41 blue dhcpcd[443]: eth0: fe80::6666:b3ff:fe9d:41bc router available
---


Any ideas?
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 26 September 2013, 19:59 GMT
Reason for closing:  Not a bug
Comment by Radu Potop (wooptoo) - Thursday, 26 September 2013, 19:57 GMT
Okay I found the issue. There's a problem with dhcpcd and IPv6. I'll use netctl for now which uses dhclient for IPv6.

Loading...