Continued problems with DVR server dropping offline?

Hey all..

I'm still having issues with my DVR server (Rpi) dropping off the network. I've assigned a static IP to the DVR server, both Apple TV units, and it will work ok for a day or so, then my router page says "Inactive" for the device, the DVR doesn't show up on the app, webpage/UI for the DVR won't connect. The only solution is to depower/repower the Rpi..

Really hoping to get this setup working properly! Thanks for any continued guidance..

P.S. My setup is Verizon Fios.. ONT-> FIOS Router -> Eeros pro wifi 6 (Bridge mode) --> Switch -> DVR server and multiple other devices which are not having issues dropping offline..

When you say you assigned a static ip address to the RPi, do you mean you set a dhcp reserved ip address in your FIOS Router settings for its ethernet MAC address?

When the RPi becomes unresponsive, have you tried pinging it to see if it replies?

Plug the Rpi into a monitor and keyboard/mouse so you can tell if the machine is still functioning when the DVR server goes down. In other words, is just the Channels DVR server crashing, or is the whole OS/computer dying? Or is it that everything appears to be running as it should and just the network interface is going down?

ChDVRuser,

Thanks for the assistance.. If it's not painfully obvious, networking is not my specialty! What I did was go into my FIOS router settings and DHCP leases section.. I then clicked EDIT for the DVR Server and checked the box for "Static Lease Type"..

I have not tried pinging the server via my routers page.. I will try that next and report back.. Thanks very much!

VTTom,

Thanks a lot for chiming in.. I'll have to research how to plug the Rpi into a keyboard mouse/tv monitor.. I've not hooked it up before to a monitor, so I"m not sure if it is crashing completely, or if it's just a network issue.. The basic issue is that when it 'drops' and I open the channels DVR app on my AppleTV it comes up with the screen asking if I"m home/away/ and says it's not connected.. So the AppleTV or my iPhone seems to not be waking it or making it 'active' on the network..

The Rpi has HDMI and USB ports on it, so you hook it up just like any other computer. When you hit a key, you should get a graphical screen with a login prompt.

Sounds like you have a switch hanging off a wireless bridge? I understand that other devices may be working fine off of it but you may want to consider hard wiring the pi to the fios router. Not saying that this is the solution, just saying it is worth troubleshooting.

If the issue still happens, and after you hook up a monitor and kbd to the pi, open up a terminal prompt and ping the gateway on your network, you can find it by I typing ifconfig. It will end in .1.See if you drop packets when the issue happens. If you do then you may have an issue with the pi or the pi's nic.

It's all about isolating the issue by ruling things out.

VTTom and Slapman,

Thanks very much.. Ordered a Micro HDMI to HDMI cable to hook it up to a monitor.. Slampman, will try connecting directly to the fios router next time, as well as changing switch ports, perhaps it's an issue with the port/switch? If I connect the Rpi to FIOS or "behind" the wireless Eero/ I suspect I won't be able to connect channels to apple TV's as they are connected via Eeros?

Thanks again gents..

Jonn

If your eero is in bridged mode your atvs should still be able to discover the channels sever. Even if you were I. A double nat config you could still manually specify the ip of the channels server.
Doubtful the port is an issue on the fios router but who knows.

Ok, few more data points for today! DVR Server dropped offline this afternoon and I was able to do some checking on some of the above questions..

  1. From the router's admin page, I was able to "Ping" the DVR server, and it said that it passed/completed. This did not however wake up the Server, or cause it to be able to used by the Channels DVR app. Also at that time, the Server was not available/contactable with the web interface.

  2. After the PING, I connected a monitor to the mini HDMI and got no output.. the screen went black for a moment as if it was going to display something, then went blue which normally means "I have no signal". I rebooted it at that point and watched a bunch of text / loading stuff come across the screen until it was all booted up.

  3. I then disconnected the server from the switch and connected directly to FIOS router... And as you said Slapman, due to Eeros being in bridge mode, I'm able to access the DVR now.. I'm not really sure how to ping the gateway from the Pi.. All I really have on there is a black screen with a command type prompt. I tried the ipconfig command at that prompt and was given asked for "login" info, which I"m not sure of.

  4. I'm curious if the "blue screen" is indicating that there is an issue with the pi just crashing?

Can't thank you all enough for helping out a stranger!

Cheers!

If channels pi is is raspian based the user login is pi the password is raspberry

And it’s iFconfig not iPconfig

no. if you mean the Channels Image for the pi.

the Channels Image is using Home Assistant as it base OS. not raspian.

Search the forms here, and there are posts on how to use the image via ssh or to login, or do network commands.

Speedingcheetah,

Thanks for the suggestion.. I've looked and looked for how to do SSH commands to no avail. DVR crashed this morning again, connected to FIOS router. When I connect to a monitor I'm getting blue "no signal" type screen. In the fios router page, I'm able to ping the device however.. This is the result..

Status: Test Succeeded
Packets: 4/4 transmitted, 4/4 received, 0% loss
Round Trip Time: Minimum = 0.41 ms

Maximum = 0.69 ms

Average = 0.52 ms|

I had just recorded a program a little bit before it droppped offline/crashed. Could it be related to commercial detection?

Thinking out loud.. Thanks for your help!

Do you also have a keyboard connected? Have not used the "Home Assistant" OS variation, but Rasperian will blank the screen after a period of non-activity. After plugging in the monitor, you typically need to press a key for video to resume. Found a reference claiming adding "consoleblank=0" to cmdline.txt will disable (such that plugging in the monitor without a keyboard will work), but have not tried it personally.

Are you using a quality power supply? That has historically been the biggest cause of inconsistent RPi behavior. Should you manage to get keyboard/monitor access working, dmesg can provide some interesting info. Best of luck.

1 Like

Does the monitor work when you plug it in before boot? Make sure it works in the first place before trying it during the breakage.

So opinions are like you know what... Everyone has one.... IMHO I would rather use an old PC, install ubuntu Linux on it and use that as a channels server. So you might want to consider that if you end up in a situation where you have to replace the pi.

I know the die hard rpi folks on this forum will want to debate me on this but in my opinion the pi is not powerful or reliable enough. Give me an old repurposed pc any day...

Gents..

Thanks for hanging in here with me..

Vraz: Yes, I have a keyboard that I can connect, although I hadn't tried connecting while having the blue screen. Quality power supply? Yes, I think so. I made a change this am to connecting it to a UPS to ensure consistent power and still having the crashing issue when connected to the UPS.

tmm1: Yessir, the monitor is working during initial boot. This afternoon, I let it boot up, and left monitor connected. After a few hours, it had crashed and I still have 'things' going on with the monitor/display. Screen shots below. I can't currently connect to the server via Channels Apps, but I am able to ping the device from router page:

Status: Test Succeeded
Packets: 4/4 transmitted, 4/4 received, 0% loss
Round Trip Time: Minimum = 0.53 ms

Maximum = 1.63 ms

Average = 0.83 ms|

Slampman: Thanks for the suggestion! The issues that I really don't have a spot to place an old pc, nor do I have one lying around.. I've also probably invested 250 dollars in the Pi, and as of now, 2 portable drives for it.. One of which was aparently not fast enough, so I've not connected a new 1TB Samsung T7. Hate to reverse course after dropping all of this money on the pi server (at least not yet)

Screen shot of current errors:

I/O errors are not a good sign. That does explain why the system stops responding though.

What usb-c power supply are you using with the Pi?

What kind of drive is it? Is it inside an enclosure? Is it plugged into the Pi directly or via a hub?

Tmm1,

The power supply is the one listed on the 'shopping list' on the channels Pi/DVR page..

The drive I'm using right now is a Samsung T7 SSD. It is plugged directly into the Pi via the USB port on the back of the Rpi. (Blue colored USB's)

Rpi is enclosed in this case. Max temps I'm seeing is 42deg..

I also have this drive that I originally bought for the setup. I swapped it for the SSD as my wife wasn't thrilled with the FF/RW speeds while actively recording.. I honestly can't recall if It was suffering random crashes with the WD drive, before the swap.

Thank you again! We'll get this straight at some point!