Bug 85427 - systemd-networkd: Could not set transient hostname: Transport endpoint is not connected
Summary: systemd-networkd: Could not set transient hostname: Transport endpoint is not...
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: ARM Linux (All)
: medium normal
Assignee: Tom Gundersen
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-25 05:19 UTC by Piotr Jurkiewicz
Modified: 2016-02-13 18:58 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Piotr Jurkiewicz 2014-10-25 05:19:20 UTC 
With systemd 216 on Arch Raspberry Pi I get the following error on boot and while plugging/unplugging in Ethernet cable.

Oct 25 07:02:17 alarmpi systemd-networkd[118]: eth0            : gained carrier
Oct 25 07:02:17 alarmpi systemd-networkd[118]: eth0            : DHCPv4 address 192.168.1.129/24 via 192.168.1.1
Oct 25 07:02:17 alarmpi systemd-networkd[118]: eth0            : Could not set transient hostname: Transport endpoint is not connected
Oct 25 07:02:17 alarmpi systemd-networkd[118]: eth0            : Failed to set transient hostname to 'alarmpi'

However, hostnamed socket activation works fine. When I enter the `hostnamectl` command, it starts (and automatically closes after a while).
Comment 1 Daniel Mack 2015-06-05 13:09:07 UTC 
Can you still reproduce this in upstream git or v220? If so, please consider opening a new issue here: https://github.com/systemd/systemd/issues
Comment 2 Piotr Jurkiewicz 2016-02-13 18:57:48 UTC 
Just tested on v228 and the bug appears to be gone.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.