Openhabian dhcpcd[353]: received SIGPIPE

Setup, Configuration and Use Runtime
1
  • Platform information:
    • Hardware: Raspberry Pi 4GB
    • OS: Openhabian 32-bit; approx 4 weeks old
    • Java Runtime Environment: I didn’t change, provided by openhabian
    • openHAB version: 3.2.0-1

On every reboot a zillion of lines is generated in /var/log/daemon.log:

openhabian dhcpcd[353]: received SIGPIPE

This has been occasionally mentioned in Openhabian topics - #5 by mstormi and Openhabian topics - #5 by mstormi ; but this time it’s impossible to say that my configuration is unsupported. Because my Raspberry is connected using a built-in ethernet and a lan cable.

By the way, i’ve configured my system to use a static IP, what is dhcpd even doing here ?

2

Well …

See openHABian | openHAB

3

I’ve read it. Well, this is kinda counterintuitive for me to use dpchd for static configuration, but this is in fact what i’ve done. I didn’t kill the dhcpcd; i simply wrote a static configuration in /etc/dhcpcd.conf, as was suggested on some debian or ubuntu forum:

interface eth0
static ip_address=192.168.0.17/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
static routers=192.168.0.1
static domain_name_servers=192.168.0.1

So i didn’t break openhabian.
But especially on your request i’ve just checked whether the behavior comes from my configuration. I disabled the static assignment and then rebooted. Then rotated logs to clean them up and rebooted again. No, the same:

Feb  2 23:49:34 openhabian dhcpcd[355]: eth0: carrier acquired
Feb  2 23:49:34 openhabian dhcpcd[355]: DUID 00:01:00:01:29:0f:e9:31:dc:a6:32:53:02:c7
Feb  2 23:49:34 openhabian dhcpcd[355]: eth0: IAID 32:53:02:c7
Feb  2 23:49:34 openhabian dhcpcd[355]: eth0: adding address fe80::fdc3:898:cdc9:95eb
Feb  2 23:49:34 openhabian dhcpcd[355]: received SIGPIPE
Feb  2 23:49:34 openhabian dhcpcd[355]: received SIGPIPE
Feb  2 23:49:34 openhabian dhcpcd[355]: received SIGPIPE
Feb  2 23:49:34 openhabian dhcpcd[355]: received SIGPIPE
... etc ...
4

Another idea came to my mind. I don’t have wlan configured because i’m not using it, so it’s “blocked by rfkill”. I thought it could originate from wlan0 interface. But nope. Disabled it using “denyinterfaces wlan0”, didn’t help.

5

I’ve added “debug” line to dhcpcd.conf and retried. It only kinda confirms that the problem comes from the ethernet interface:

Feb  3 00:11:30 openhabian dhcpcd[355]: eth0: carrier acquired
Feb  3 00:11:30 openhabian dhcpcd[355]: DUID 00:01:00:01:29:0f:e9:31:dc:a6:32:53:02:c7
Feb  3 00:11:30 openhabian dhcpcd[355]: eth0: IAID 32:53:02:c7
Feb  3 00:11:30 openhabian dhcpcd[355]: eth0: adding address fe80::fdc3:898:cdc9:95eb
Feb  3 00:11:30 openhabian dhcpcd[355]: eth0: probing address 192.168.0.17/24
Feb  3 00:11:30 openhabian dhcpcd[355]: received SIGPIPE
Feb  3 00:11:30 openhabian dhcpcd[355]: received SIGPIPE
Feb  3 00:11:30 openhabian dhcpcd[355]: received SIGPIPE
[skip]
Feb  3 00:11:35 openhabian dhcpcd[355]: received SIGPIPE
Feb  3 00:11:35 openhabian dhcpcd[355]: received SIGPIPE
Feb  3 00:11:35 openhabian dhcpcd[355]: received SIGPIPE
Feb  3 00:11:35 openhabian dhcpcd[355]: eth0: using static address 192.168.0.17/24
Feb  3 00:11:35 openhabian dhcpcd[355]: eth0: adding route to 192.168.0.0/24
Feb  3 00:11:35 openhabian dhcpcd[355]: eth0: adding default route via 192.168.0.1

(yes, i’m back to static assignment, because why not)

6

I’d think you did as it does not happen on unmodified openHABian.
Again, well … openHABian | openHAB

7

Well, especially for hardcore non-believers i’ve disabled the static config again and rebooted.

Feb  3 00:21:37 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:37 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:37 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:37 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:37 openhabian dhcpcd[356]: received SIGPIPE
[skip]
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: received SIGPIPE
Feb  3 00:21:42 openhabian dhcpcd[356]: eth0: DAD completed for 192.168.0.17
Feb  3 00:21:42 openhabian bthelper[698]: Raspberry Pi BDADDR already set
Feb  3 00:21:42 openhabian dhcpcd[356]: eth0: using static address 192.168.0.17/24
Feb  3 00:21:42 openhabian dhcpcd[356]: eth0: adding IP address 192.168.0.17/24 broadcast 192.168.0.255
Feb  3 00:21:42 openhabian dhcpcd[356]: eth0: adding route to 192.168.0.0/24
Feb  3 00:21:42 openhabian dhcpcd[356]: eth0: ARP announcing 192.168.0.17 (1 of 2), next in 2.0 seconds
Feb  3 00:21:42 openhabian dhcpcd[356]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks' STATIC
8

I believe you’re seeing this but as I said it does not happen on unmodified openHABian so I’d guess it’s because you didn’t fully undo everything you modified in the first place, but only you yourself can know what that could be.
That’s right that kind of cumbersome game I (and most of us) don’t want to spend our time on playing.
I suggest you install from scratch using latest image, strictly mind the prerequisites this time and see if the problem persists.

9

Well, i’ve got your “fuck off, the problem doesn’t exist”. I’ll try doing what you’ve suggested tomorrow or the day after tomorrow. Thank you very much for your kind support, it’s 00:35 AM here. :disappointed_relieved: