Cumulus Support

mcrossley

Definitely upgrade to v4.0.1, you could also try setting the Concurrent Uploads to 1 in the connection Advanced settings. It may be a max number of connected sessions per client thing on your server - straw grasping.

mcrossley

All the Ecowitt stations use a common bit of code to perform the historic catch-up. This is interesting (along with the requested log file)... If you are seeing zeroes only on extra sensors data, but main sensors are ok, then we probably would need a log file of the startup, and at least data loggin...

mcrossley

OK, I found the problem. It occurs when you enable FTP, the logger is only initialised on start-up of the MX. So if you restart MX the error should not occur.

I have fixed it for the next build, so the logger is initialised when you enable FTP as well as at start-up.

mcrossley

Please attach the MXdiags log file for a run that "hangs"

mcrossley

It looks like a problem with FTP logging, I'll have a look at it later today. If you still have the v4 instance available it would be interesting to see if the error went away when FTP logging was enabled in Program Settings

mcrossley

Ah, OK. Great that you found the problem.

mcrossley

Can you post your dayfile.txt please

mcrossley

You would be best avoiding whole hours as well as that is when the log gets written, database updated, ini files updated etc, if your logging interval is say 5 minutes, then make it reboot at 2 or 3 minutes past the hour.

mcrossley

Confirmed, not working, and fixed for next build.

mcrossley

ConligWX wrote: ↑Fri 17 May 2024 10:37 am I noticed I have started to get more WUnderground errors showing in the log file since 4023

Yes, Rapid Fire did not log any errors in previous versions, I have enabled some logging, but it shouldn't be that chatty, what should be a debug message is being logged as a warning.

mcrossley

Thanks, found the problem, a missing comma in the JSON if Sum0 is the only selection

mcrossley

As above diags please. But note, midnight is the worst possible time to reboot, Cumulus will be in the middle of its overnight processing.

mcrossley

Edit the file using a decent text editor eg Notepad++, any deviant editor will normally show the line numbers.

Even the old Windows Notepad, though it did not show line numbers had a Goto Line option.

mcrossley

If you think the passwords have been altered, then just restore a copy of Cumulus.ini that you used with V3. On first run v4 will then encrypt the passwords again.

Do not alter passwords by editing the Cumulus.ini yourself.

mcrossley

That's OK - well it's not, but nor is anything to worry about.

The script that generates the hash file has started ignoring my list of ignore files!

Now fixed, so should be OK for the next build.

A newly created hash file created with the amended script attached.

Cumulus Support

Search found 11548 matches

Re: V4 b4022 - HTTPS Error

Re: Ecowitt cloud vs. http.

Re: b4023 realtime.txt upload issue

Re: CumulusMX v4 updating

Re: b4023 realtime.txt upload issue

Re: Version 4 Historic Graphs starting at wrong date

Re: Version 4 Historic Graphs starting at wrong date

Re: Crashing every couple of days

Re: Cumulus MX V4 Build Webtags Not working.

Re: CMX v4 - b4023

Re: Temp Sum Chart in CMX console

Re: Crashing every couple of days

Re: Minimum/Maximum Display of Pressure Gauge

Re: Some trouble with new installation

Re: CMX v4 - b4023