High Write Load appeared with no changes

[Rob_in]

Hi all,

So this morning our MS has started giving the "High Write Load" warning message.

This has to be rubbish because I haven't changed anything (added more stats, whatever) for a long time. This warning has just appeared and now won't go away when acknowledged.

The SD card isn't close to full. All our stats are on 5 minute average or more (certainly no per-second or per-change stuff going on). Even so, I removed a few stats that weren't super interesting to see if that would clear the issue. It did not.

So my question is... has anyone else seen this and if so, how did you get rid of it?

Cheers,

Robin

[Jakob Ventzel]

Hi Robin

I have not seen this. A snapshot of my Loxone Monitor looks like this, if that can help you determina what is off for your installation?

[Rob_in]

Hi,

Thanks for the tip. Indeed, the monitor does show when stat files are updated. Eg:

00000836 10.1.1.20       10:31:57.443 11:31:59.305 FS append /stats/115b59a3-006a-73c5-fffff62eeb38b63d.201911 10us  16 bytes ([Climate] Heating On_Off (Status))

I left this running for a long time but only saw writes every 5 minutes as one would expect (5 minutes is the minimum statistics time I have setup).

37 stats written every 5 minutes = just over 10,000 writes per day. This doesn't sound excessive.

When I run project validation it reports 21,888 statistics entries per day, which is twice as many as are actually being written as can be seen from watching the monitor.

Looks to me there's a bug in the code that decides when to issue this warning or not. I have opened a ticket with Loxone support and will report back.

Robin

[Jakob Ventzel]

You could be right about a bug being present. Yesterday I needed to disconnect my internet connection for three hours. During that time Loxone began notifying me that it has lost internet connection and was unable to send notifications for events (e.g. my basement door opening and closing). This was of course expected, but upon reconnecting the Internet, I could not get the mini server to detect that Internet connectivity had been restored. I tried rebooting a multitude of times and flipping the offline mode on and off, but nothing helped. So an hour ago I checked for firmware updates and (luckily) found one which I installed and this update seems to have set the mini server right again.

If you haven't done so already, you should check if a firmware update is available and consider installing that.

Kind regards Jakob

[Rob_in]

There are plenty of bugs in the current Loxone firmware. Currently my Miniserver says it's on version 10.2.3.26 and Loxone Config says that's the latest (no update available).

Side note: Just to check I told Loxone Config to Update the Miniserver firmware. Which it did. However, the web interface reports version 10.2.3.26. So bravo Loxone - looks like your update process doesn't bother to check that this actually will be an update before going ahead!

Regarding online status: the Miniserver determines it's online status by pinging various hosts (you can get a network sniffer out and look at what it's connecting to). However, the ping requests sent out have two issues: the sequence number is always zero and it does not include any payload data. I have discovered that my ISP blocks ping requests that have a payload under 12 bytes and therefore these don't get replies and our Miniserver thinks it is offline even when it is not. Because the Miniserver thinks it's offline push notifications do not work as it doesn't bother sending them (because it thinks it's offline).

I was told in June that there would be a new release 'soon' that would fix this problem but am still waiting for that.

Robin

[Julián Medrano Silvestre]

You can update to 10.3.9.6.

May be it solves the problem

[Rob_in]

I'd love an update, but Loxone Config says none is available. How are you able to get 10.3.9.6?

[Rob_in]

Hi,

So... ask (Loxone support) and you shall receive - I'm now on 10.3.7.30. I asked for beta so I'm guessing 10.3.9.x are alpha only?

This does fix the ping issue (my Miniserver thinks it's back online after months) but not the spurious stats warning. Oh well... I continue to discuss with them.

Cheers,

Robin