Welcome to the new home of the Cumulus Support forum.

Latest Cumulus release v1.9.4 (build 1099) - Nov 28 2014
Latest Cumulus MX release - v3.0.0 build 3044 7 December 2018. See the Wiki for download

MXDiags logged errors

Discussion of version 3 of Cumulus, which runs on Windows, Linux, and OS X. All Cumulus MX queries in here, please.

Moderator: mcrossley

Post Reply
Will-NZ
Posts: 15
Joined: Sat 15 Mar 2014 10:48 pm
Weather Station: WM-918
Operating System: windows 10
Location: Waitetuna, New Zealand

MXDiags logged errors

Post by Will-NZ » Thu 12 Apr 2018 10:20 pm

I had an issue with the batch file failing to activate after a forced windows10 upgrade where it just shuts the computer down.. found out that the com port was still open, had not been shut down so Cumulus batch file could not get to it, so uninstalled and reinstalled the com port and now fires upok.
Opened the last MXdigs file to figure out why and found reams of the following messages.. just an excerpt below, .zip attached.
I dont upload to WU anymore [disabled uploads in internet settings]as had many problems with them and did not receive any reply to my emails. Same issues and a few others as described in a thread on this forum.
Have gone through both station settings and internet settings and cant find anything which explains to my limited knowledge what/why these are here.
The gauges and other info seem to display fine on google chrome?

Anyone have an explanation and possible solution to the errors?

2018-04-12 15:42:04.163 Error connecting ftp - No connection could be made because the target machine actively refused it [fe80::208e:6786:8866:d379%6]:21
2018-04-12 15:42:05.169 Error uploading web\realtimegauges.txt to realtimegauges.txt : No connection could be made because the target machine actively refused it [fe80::208e:6786:8866:d379%6]:21
2018-04-12 15:42:34.160 Error connecting ftp - No connection could be made because the target machine actively refused it [fe80::208e:6786:8866:d379%6]:21
2018-04-12 15:42:35.167 Error uploading web\realtimegauges.txt to realtimegauges.txt : No connection could be made because the target machine actively refused it [fe80::208e:6786:8866:d379%6]:21
You do not have the required permissions to view the files attached to this post.

User avatar
mcrossley
Posts: 5231
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2
Operating System: Stretch Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: MXDiags logged errors

Post by mcrossley » Fri 13 Apr 2018 1:55 pm

Is your FTP server enabled for IPv6?

Will-NZ
Posts: 15
Joined: Sat 15 Mar 2014 10:48 pm
Weather Station: WM-918
Operating System: windows 10
Location: Waitetuna, New Zealand

Re: MXDiags logged errors

Post by Will-NZ » Fri 13 Apr 2018 6:00 pm

I am not trying to upload data to anywhere else, switched off data upload to WU in settings many months ago, data from weather station [old WM918] comes into my desktop via com1, stored/processed in there via MX, and is displayed via Chrome on same desktop.

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: MXDiags logged errors

Post by steve » Fri 13 Apr 2018 8:56 pm

Due to an error on my part, MX tries to upload the realtimegauges.txt file by default even if you don't have an ftp site configured. Go into the internet settings and turn off the ftp of the realtimegauges.txt file.
Steve

Will-NZ
Posts: 15
Joined: Sat 15 Mar 2014 10:48 pm
Weather Station: WM-918
Operating System: windows 10
Location: Waitetuna, New Zealand

Re: MXDiags logged errors

Post by Will-NZ » Mon 16 Apr 2018 8:07 pm

Ok, have switched off the option "realtimegauges.txt FTP", assume this is the one you were referring to? Will monitor and see if the messages disappear and report back. Thanks Steve.

Will-NZ
Posts: 15
Joined: Sat 15 Mar 2014 10:48 pm
Weather Station: WM-918
Operating System: windows 10
Location: Waitetuna, New Zealand

Re: MXDiags logged errors

Post by Will-NZ » Mon 16 Apr 2018 9:20 pm

Ok, seems to have worked, no more reams of error messages, thanks again Steve. 8-)

Post Reply