Cumulus Support

This morning around 7h30 my CMX stopped working and can't be restarted.
The GW1100 is still working properly and can be accessed. Ecowitt.net is updated. Sensor and battery statuses are normal.

So you think it is the local network? but the RPi3 can be accessed like normal, both via the terminal and via WinSCP.
There seems to be no (network) problem at all but CMX suddenly can't connect anymore to the GW1100.

The MXdiags are attached, the oldest is the one where it starts failing, the newest where I switched DEBUG logging on and refused to restart.
Can't connect to the GW1100.

1) The GW1100 has been restarted: did not help
2) My Test env with a second GW1100 on the same network keeps running perfectly

Any suggestions?

Reverting to b3269 does not help.

GW1100 firmware is 2.2.9

At 9:56 it started working again (CMX reverted to 3269).
Logfile attached.

And it works again with 3278...

Storm in a glass of water, sorry.

I suspect the clocks to be not synchronised between CMX and the GW1100.
Any parameter? Where do I set that?

@freddie, I guess this threat should be in the Ecowitt forum: why should it stop receiving requests on the API?
Are there more who experience that?

Hans, I was reading a thread on wxforum about decreasing free memory on the GW1000/2000. users also reporting them restarting from anywhere between every 8 days and a month, But, significantly, also reports that the gateway becomes unresponsive for a "period" before it reboots.

Thnx Mark, I'll start reading there.

OK, there seemed to be an issue with firmware 2.2.8 which has been rapidly replaced with 2.2.9

As I have Automatically upgrade firmware enabled, the GW1100 upgraded immediately to 2.2.9 and hopefully the issue does not happen again.
Apparently there definitely was an issue.

@freddie: this thread really belongs to the Ecowitt forum.

My GW1100 is on firmware version 2.3.0 ...

Cortmalaw wrote: ↑Sun 14 Jan 2024 2:06 am My GW1100 is on firmware version 2.3.0 ...

indeed it is