Miniserver frequently rebooting (Warning 503). Possible SD Card Damage?

[Rob_in]

Hi all,

This evening our Miniserver has started rebooting randomly. Many, many times. While I do 'tweak' things regularly haven't changed anything for days.

The only clue is a 'Warning 503' message in def.log. Everything else looks normal.

Anyone know what 'Warning 503' means?

I also notice earlier today getting some SDC errors:

2020-03-18 12:01:00.006;SDC number of errors: 1

2020-03-18 18:00:00.003;SDC number of errors: 2

I assume this means the Miniserver thinks there are SD Card faults? These only happened at those timestamps, and not every time the Miniserver started.

Hitting /dev/sys/sdtest returns the below which doesn't really shed any light:

	<?xml version="1.0" encoding="utf-8"?>
	<LL control="dev/sys/sdtest" value="SD Performance: Read: 389kB/s, Write: 226kB/s, No error (0 0), ManufacturerId: 2, Date 2016/3, CardType 2, BlockSize 512, Erase 0, MaxTransferRate 25000000, RwFactor 2, ReadSpeed 22222222Hz, WriteSpeed 22222222Hz, MaxReadCurrentVDDmin 3, MaxReadCurrentVDDmax 5, MaxWriteCurrentVDDmin: 5, MaxWriteCurrentVDDmax: 1, Usage: 9.13%" Code="200"/>

That said, reading other reports in this forum it could be the SD Card is corrupt so I will look at ordering a new 'High Endurance' card. The larger the better to spread wear on the card (am thinking a 64GB Sandisk Max Endurance).

With a new card one can just format in Loxone Config (doesn't matter if the card is larger than the 8GB standard one, right?) and insert into Miniserver for a 'brand new from the factory' appearance, yes? Then I just upload my config and job done?

Thanks for your help,

Robin

[Rob_in]

Hi all,

To follow up on this. I raised a ticket with Loxone and yet to hear a response.

The Miniserver seemed to stabilise later that evening without any changes being made. The next day I made some tweaks to further remove some SD card writes and it was running OK until around 8pm where it rebooted again.

Just to try, I disconnected incoming requests from the internet (port 80 through our router) as perhaps, just perhaps something dodgy could have been coming through there. Don't know if that was co-incidence or not but no reboots since. If some idiot was scanning port 80 on our ISP's address range then hit the Miniserver many times when they found that port open...? Well, it's possible that could cause it to crash I guess. Luckily we have a VPN back to home but it's slightly annoying to have to fire that up on your phone before opening the Loxone app.

Anyhow, I'm hoping when Loxone eventually get round to replying they can shed some light. Will reply here if/when that happens.

Robin

[Rob_in]

On Monday, 23 March 2020 17:03:03 UTC+1, Rob_in wrote:

Just to try, I disconnected incoming requests from the internet (port 80 through our router) as perhaps, just perhaps something dodgy could have been coming through there. Don't know if that was co-incidence or not but no reboots since. If some idiot was scanning port 80 on our ISP's address range then hit the Miniserver many times when they found that port open...? Well, it's possible that could cause it to crash I guess. Luckily we have a VPN back to home but it's slightly annoying to have to fire that up on your phone before opening the Loxone app.

Just in case malicious network activity was causing this (and for a bit of for 'fun') instead of forwarding port 80 of our router direct to the Miniserver I have put an nginx reverse proxy in the way and enabled rate limiting on it. Works perfectly so TBH, would probably advise this kind of setup just for safety.

For the details: our router is a TP-Link C7 1750 with OpenWRT running on it. It's not trivial, but not overly complicated either to get this nginx proxy running on the router (ie. didn't need any other hardware as this is very lightweight).

I could have turned off port 80 access altogether and used our VPN but I find it annoying while out and about to have to fire up the VPN connection just to check something quickly on the Miniserver.

Robin