TVH on RPI crashes when "eth0: carrier lost" message appears in syslog

Wim K

Hi,

I'm a bit of a newbie here, so bare with me please.

Like the subject states, TVH on my RPI4 crashes when there's a message in syslog "eth0: carrier lost", which I think means the network connection is interrupted.

And obviously I am trying to figure out WHY network connection seems to be lost, but I'm not making much progress there and BESIDES THAT I would like to know if it's possible to make changes in my pi so that an interrupted network connection would not crash TVH. I'm clueless here, so I need your help.

This is the part in syslog that's relevant (after this, I restarted TVH).

Feb 13 07:25:44 raspberrypi dhcpcd[495]: eth0: carrier lost
Feb 13 07:25:44 raspberrypi kernel: [1937811.844321] bcmgenet fd580000.ethernet eth0: Link is Down
Feb 13 07:25:44 raspberrypi dhcpcd[495]: eth0: deleting address fe80::e68f:7149:c356:1755
Feb 13 07:25:44 raspberrypi avahi-daemon[420]: Withdrawing address record for fe80::e68f:7149:c356:1755 on eth0.
Feb 13 07:25:44 raspberrypi avahi-daemon[420]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::e68f:7149:c356:1755.
Feb 13 07:25:44 raspberrypi avahi-daemon[420]: Interface eth0.IPv6 no longer relevant for mDNS.
Feb 13 07:25:44 raspberrypi dhcpcd[495]: eth0: deleting route to 192.168.2.0/24
Feb 13 07:25:44 raspberrypi dhcpcd[495]: eth0: deleting default route via 192.168.2.254
Feb 13 07:25:44 raspberrypi avahi-daemon[420]: Withdrawing address record for 192.168.2.9 on eth0.
Feb 13 07:25:44 raspberrypi avahi-daemon[420]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.2.9.
Feb 13 07:25:44 raspberrypi avahi-daemon[420]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 13 07:25:45 raspberrypi tvheadend[5055]: mpegts: 266MHz in DVB-C Network - tuning on HDHomeRun DVB-C Tuner #0 (192.168.2.5)
Feb 13 07:25:45 raspberrypi tvheadend[5055]: tvhdhomerun: tuning to a8qam256-6900:266000000
Feb 13 07:25:48 raspberrypi dhcpcd[495]: eth0: carrier acquired
Feb 13 07:25:48 raspberrypi kernel: [1937816.004248] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Feb 13 07:25:48 raspberrypi dhcpcd[495]: eth0: IAID 32:7d:ba:35
Feb 13 07:25:48 raspberrypi dhcpcd[495]: eth0: adding address fe80::e68f:7149:c356:1755
Feb 13 07:25:48 raspberrypi avahi-daemon[420]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::e68f:7149:c356:1755.
Feb 13 07:25:48 raspberrypi avahi-daemon[420]: New relevant interface eth0.IPv6 for mDNS.
Feb 13 07:25:48 raspberrypi avahi-daemon[420]: Registering new address record for fe80::e68f:7149:c356:1755 on eth0.*.
Feb 13 07:25:48 raspberrypi dhcpcd[495]: eth0: rebinding lease of 192.168.2.9
Feb 13 07:25:48 raspberrypi dhcpcd[495]: eth0: probing address 192.168.2.9/24
Feb 13 07:25:48 raspberrypi dhcpcd[495]: eth0: soliciting an IPv6 router
Feb 13 07:25:53 raspberrypi dhcpcd[495]: eth0: leased 192.168.2.9 for 864000 seconds
Feb 13 07:25:53 raspberrypi avahi-daemon[420]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.9.
Feb 13 07:25:53 raspberrypi avahi-daemon[420]: New relevant interface eth0.IPv4 for mDNS.
Feb 13 07:25:53 raspberrypi dhcpcd[495]: eth0: adding route to 192.168.2.0/24
Feb 13 07:25:53 raspberrypi avahi-daemon[420]: Registering new address record for 192.168.2.9 on eth0.IPv4.
Feb 13 07:25:53 raspberrypi dhcpcd[495]: eth0: adding default route via 192.168.2.254
Feb 13 07:26:01 raspberrypi dhcpcd[495]: eth0: no IPv6 Routers available

DaveH

The log you show is all about the network; nothing about TVH failing? You seem to be using a network tuner so that's clearly not going to work whilst the network is down. So I'm not clear exactly what happened?

Some thoughts:
(1) Do you use IPv6? If not you can shut it down so it doesn't clutter the logs. Google will find how-tos.
(2) Why did eth0 go down? Did somebody pull the cable out or something?
(3) What type of network management are you using? (network manager, wicd or systemd?) It's possible to have more than one in operation and they conflict and can cause networks to drop.
(4) What operating system is installed on the pi, including version, and was it a fresh install or an upgrade?
(5) what's the hardware configuration?

Wim K

Hi Dave,

Thanks for responding!

(1) No I don't use IPv6. That is, my router has IPv6 disabled. Do you mean I should shut it down in the Pi?
(2) This happens randomly, no cable disconnected, nothing in the routers logs. But since my post I have been searching the web and I may have found the answer and solution to the disconnecting.
The ethernet might be going into "energy efficient" state
Found here: https://www.raspberrypi.org/forums/viewtopic.php?t=253398 (3) I have no clue what you mean here, sorry for being a newbie. I didn't make any tweaks regarding network after installing the OS
(4) Using raspberry pi imager, I installed Raspberry Pi OS. It was a fresh install. Date somewhere around november 2020 I think. Have been searching on and off for this problem.

(5) I'm using a Raspberry Pi 4B, 8 GB and a hdhomerun 4DC and a smargo card reader.

As far as I know this never happened before (nov 2020) with a RPI3B, with the Pi4 it happens now and then. Maybe once a week.
In syslog nothing about tvh. But TVH just doesn't work, nor does the webif. And if I stop and start again, the problem is solved.

I am hoping to have solved the issue with the solution in (2) and I understand that when the connection to the HDHR is lost, TVH can't produce a tv-signal but what about the webif then? So this made me think TVH hangs completely.

EDIT:

I did make a change regarding network, in config.txt I disabled wifi: dtoverlay=disable-wifi

DaveH

Wim K wrote:

> (1) No I don't use IPv6. That is, my router has IPv6 disabled. Do you mean I should shut it down in the Pi?

You don't have to but it just removes noise from the logs.

> (2) This happens randomly, no cable disconnected, nothing in the routers logs. But since my post I have been searching the web and I may have found the answer and solution to the disconnecting.
> The ethernet might be going into "energy efficient" state

> Found here: https://www.raspberrypi.org/forums/viewtopic.php?t=253398

That sounds hopeful. Well found. Hope it works out.

> (3) I have no clue what you mean here, sorry for being a newbie. I didn't make any tweaks regarding network after installing the OS

OK, if you haven't changed anything there shouldn't be a problem.

> (4) Using raspberry pi imager, I installed Raspberry Pi OS. It was a fresh install. Date somewhere around november 2020 I think. Have been searching on and off for this problem.

> (5) I'm using a Raspberry Pi 4B, 8 GB and a hdhomerun 4DC and a smargo card reader.

OK, thanks.

> As far as I know this never happened before (nov 2020) with a RPI3B, with the Pi4 it happens now and then. Maybe once a week.
> In syslog nothing about tvh. But TVH just doesn't work, nor does the webif. And if I stop and start again, the problem is solved.

> I am hoping to have solved the issue with the solution in (2) and I understand that when the connection to the HDHR is lost, TVH can't produce a tv-signal but what about the webif then? So this made me think TVH hangs completely.

Do you know about TVH's logging? You can see the log at the bottom of the webif window (the button with two up-arrows). You can send the log to the journal (see https://tvheadend.org/projects/tvheadend/wiki/Debugging ). BTW, there's a difference between a 'crash' and a 'hang'; it's worth learning the difference to provide accurate problem reports.

> EDIT:

> I did make a change regarding network, in config.txt I disabled wifi: dtoverlay=disable-wifi

Wim K

Dave H wrote:
> Wim K wrote:
> > (1) No I don't use IPv6. That is, my router has IPv6 disabled. Do you mean I should shut it down in the Pi?
>
> You don't have to but it just removes noise from the logs.
>
> > (2) This happens randomly, no cable disconnected, nothing in the routers logs. But since my post I have been searching the web and I may have found the answer and solution to the disconnecting.
> > The ethernet might be going into "energy efficient" state
> > Found here: https://www.raspberrypi.org/forums/viewtopic.php?t=253398 >
> That sounds hopeful. Well found. Hope it works out.
I'll report back if this solves my problem or not, can be a week or sooner if it happens earlier.
>
> > (3) I have no clue what you mean here, sorry for being a newbie. I didn't make any tweaks regarding network after installing the OS
>
> OK, if you haven't changed anything there shouldn't be a problem.
>
> > (4) Using raspberry pi imager, I installed Raspberry Pi OS. It was a fresh install. Date somewhere around november 2020 I think. Have been searching on and off for this problem.
> > (5) I'm using a Raspberry Pi 4B, 8 GB and a hdhomerun 4DC and a smargo card reader.
>
> OK, thanks.
>
> > As far as I know this never happened before (nov 2020) with a RPI3B, with the Pi4 it happens now and then. Maybe once a week.
> > In syslog nothing about tvh. But TVH just doesn't work, nor does the webif. And if I stop and start again, the problem is solved.
> > I am hoping to have solved the issue with the solution in (2) and I understand that when the connection to the HDHR is lost, TVH can't produce a tv-signal but what about the webif then? So this made me think TVH hangs completely.
>
> Do you know about TVH's logging? You can see the log at the bottom of the webif window (the button with two up-arrows). You can send the log to the journal (see https://tvheadend.org/projects/tvheadend/wiki/Debugging ). BTW, there's a difference between a 'crash' and a 'hang'; it's worth learning the difference to provide accurate problem reports.
I know the difference between crash and hang but accidently used the wrong term, sorry about that. Yes I know about the logging option in the webif but I thought I could only use that when I'm in the webif in my pc and the pc shuts down every night, so I had to start that every morning to keep on sending those logs to the journal. I now found out I can do that within the pi (through VNC) so that's a simple option for me.
I know it's better to use a debug-package but in the past I had trouble doing that correct since I had to manually build the package. So this time I installed TVH simply with "sudo apt-get install tvheadend". This isn't possible for debug-packages wright?
>
> > EDIT:
> > I did make a change regarding network, in config.txt I disabled wifi: dtoverlay=disable-wifi
>

> OK

Wim K

Dave,

So far, so good with this issue. Will report if it turns up again.

Thanks,

Wim

Wim K

Still no problem. I consider it solved.