On Mon, 17 Jul 2023 17:40:42 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 23:08 schrieb Lew Wolfgang:
On 7/16/23 12:01, Daniel Bauer wrote: ...
It is strange that it always happens Saturday nights, but maybe its coincidence.
Hi Daniel,
I have no idea if this is related, but I've got a couple of Reolink PoE cameras now, and they automatically reboot themselves every every Sunday morning by default. I think they do this to make sure that any malware collected during the week is completely removed. It probably improves overall reliability too. The timing of the reboot can be changed, and it can be turned off. Does your system have such a feature? Could it be related somehow to your problem?
Regards, Lew
That was the right hint. Thank you Lew!
In fact my cameras (also Reolink) are set to reboot every Sunday morning at 02am.
So I logged in directly to the web-interface of one of the cameras from the mini-PC and clicked "reboot". The camera disappeared and the "waiting symbol" was shown - for ever. The camera didn't come back and wasn't reachable per ping.
So this part of the problem is clear now. The cameras want to reboot on Sunday morning and then don't boot...
What firmware version is in the cameras? Is it up to date?
BUT:
Switching the cable again to the laptop, the camera booted.
Also, I then went to the web interface of the same camera, but this time from the laptop, clicked "reboot". It rebooted immediately.
I repeated several times:
I go to the web interface of the camera from the mini-pc: reboot does /not/ work. I do the same from the laptop: camera reboots immediately and connection is re-established automatically.
Note: the only thing I changed was unplugging the eth-cable that connects mini-pc and switch on the side of the pc and plugged it into the laptop. All the rest is the same, untouched.
Question:
- Why does the reboot of the camera work if it is connected to the laptop, but not when connected to the pc?
There must be something wrong on the pc's side, but what? Does OS 15.5 (pc) handle eth connections differently than 15.3 (laptop)? How can I come even closer to the solution?