[systemd-bugs] [Bug 85427] New: systemd-networkd: Could not set transient hostname: Transport endpoint is not connected
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Oct 24 22:19:20 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=85427
Bug ID: 85427
Summary: systemd-networkd: Could not set transient hostname:
Transport endpoint is not connected
Product: systemd
Version: unspecified
Hardware: ARM
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: general
Assignee: systemd-bugs at lists.freedesktop.org
Reporter: piotr.jerzy.jurkiewicz at gmail.com
QA Contact: systemd-bugs at lists.freedesktop.org
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).
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141025/60c38626/attachment.html>
More information about the systemd-bugs
mailing list