Cumulus Support

Strange problem !

If the log file (MXdiags) becomes larger than 20,000 kb, Cumulusmx will stop the FTP upload of the non-realtime files.
This has happened twice so far.
With a restart everything is back to normal.
A new log file is created in the MXdiags directory and the old log file is deleted.

Realtime upload 30 sec
Web Interval 10 min

Last time, before performing a reboot, I made a copy of this file.
This file is 21,342 kb in size

After the time of no more uploading, there is no more mention of the standard Data file

last upload time 2021-05-01 08:00

What could be going on?

Harm

The log file rolls over when it gets to that size - which is a mighty coincidence. It shouldn't be deleted. Do you have sufficient disk space?

freddie

The log file did not roll over and it was deleted when i restarted CMX. (i made first a copy if it)

Diskspace enough 110 GB and in use 16,6 GB

The realtime uploads continued teh non realtime (10min) stopped.
Harm

It's a strange one. There must be many other users with the same setup as you - yet no reports of this. I think I'll leave this one to @mcrossley.

I turned on debug and ftp logging to get to 20,000 earlier.
Harm

Odd one, there is nothing in the code to delete the last file, it deletes the oldest one if there are more than 10.

Log rollover is working for others as I've seen the log files posted.

Let's see what happens on the next rollover with debug logging enabled.

@Mark

There were 11 created missing log files with a date younger than the log file in the MXdiags directory.

Harm

Have you changed permissions on the MXdiags folder recently?

@Freddie

No change of permissions and CMX runs as administrator

Harm

The last rollover went normally with a size of 20,520 kb and the uploads continued as usual.
So I cannot reproduce the "error".
I will keep an eye on the progress.

But it remains a strange phenomenon why the realtime FTP just continued and the 10 min FTP stopped.

Harm