26 replies to this topic

[anudanan]

There are different situations for driver crashes, 2 or 3  times it was during channel switching. The last one was after selecting CutListEditor

 

A daily reboot may help. I´ve the same feeling. But it is difficult to do that automatically.

Do you know an automatic reboot methode which only reboots if no local timers are running/starting and also recordings from remote boxes are not running (my remote boxes make the recordings to the internal hdd in my main box in the living room). I think that is difficult. Actually manual reboot may work.

Edited by anudanan, 27 February 2018 - 21:19.

[Erik Slagter]

First fix above problem (which is not of a technical nature ), then either create a dummy timer that does a deep-standby afterwards, and another dummy recording that does the waking up. Or use a crontab with a "init 6" in it.

[anudanan]

But the Central box doesn‘t know If there remote box writes recordings to the hdd inside the Central Box. That is the Problem.

[Erik Slagter]

Which is not a technical problem, as I explained. If you want to reboot every night, you have to make sure in some time window no recordings are planned.

 

On the other, rebooting as a result of a crash will have the same effect, but then unplanned. I'd rather have it planned.

[anudanan]

You´re right, it is not a technical problem. It is a problem between the boxes an my wife ;-)

 

Actualy early in the  morning after standing up I check the timers our three boxes and if no one runs, I reboot the central box.

 

I will report to your team in future if the crashes with openpli 6.2 rc are there or not

[Erik Slagter]

VU+ has already updated their drivers, it seems that it contains improvements in robustness, but we can't include them in release-6.1, so please wait for 6.2.

[anudanan]

It is ok, I can wait for 6.2 rc.

 

Thank you for your great work