Page 1 of 1

Huge MXDiags file

Posted: Sun 10 Sep 2017 4:02 pm
by t951
My PC gave me a running out of space error. Some research found that my Diags folder held the file causing the issue. It is too big to open...any ideas?
cumulus.PNG
cumulus2.PNG
I don't know if the file stopped at 31.9Gb due to HDD space, or some other limitation.

Any ideas?

Thanks!
t

Re: Huge MXDiags file

Posted: Sun 10 Sep 2017 4:15 pm
by steve
As that's an old file, you could just delete it, unless anyone has any suggestions for viewing it. Note that as it's an old file, it wouldn't have been increasing in size, so it's not clear how it could have been the cause of you running low on disk space at this time.

There is an issue with the latest build as I made uploading of the realtimegauges file a default operation without checking whether ftp is enabled. If you are not uploading to your own website, this will cause lots of error messages to be logged, perhaps this is the cause. If so, you should turn it off in your internet settings.

Re: Huge MXDiags file

Posted: Sun 10 Sep 2017 10:06 pm
by ConligWX
in linux you could split the file into more readable sizes. it is large to say the least, do you have debugging enabled?

Re: Huge MXDiags file

Posted: Tue 12 Sep 2017 1:31 am
by jlmr731
Toxic17 wrote:in linux you could split the file into more readable sizes. it is large to say the least, do you have debugging enabled?
in linux you could also use vim (vi) it works fine for me with large files and you can easily skip lines

but as far as the size had to be an issue like Steve said or maybe connection issues but as long all is working good now delete it.

Re: Huge MXDiags file

Posted: Tue 12 Sep 2017 6:44 am
by ConligWX
Personally I wouldn't delete a file that big without understanding what was going on with the system. Just guessing what the issue was doesn't fix it, or even allow you to understand what went wrong in the first place.

Re: Huge MXDiags file

Posted: Tue 12 Sep 2017 9:04 pm
by t951
Sorry for the slow response....Just got back our power from Irma!

I am going to move it out of the directory and see if anything breaks. If not, I will delete it.

I don't think this will be a system related issue, more of an app related, but I could be wrong. It doesn't seem to be used by the program anymore, so I will most likely just delete it. My concern was it happening again and not understanding the root cause.

Thanks everyone.

t.