CumulusMX "Data input appears to have stopped"

n1iwv · Post by **n1iwv** » Mon 06 Jul 2015 5:47 pm

Hi All...This is my first post.
Firstly...Thank You for allowing me to participate in the Beta testing for CumulusMX.
My setup is a Raspberry PI 1 model B, Davis VantageVue with WeatherLinkIP data logger.
The Pi is static IP = 192.168.1.200
The WeatherLinkIP logger is static IP 192.168.1.19 ...latest firmware 1.1.1
I've been using Cumulus1 on my windows OS for the lasts several years with no problems and I love it!!
My goal is to move everything over to the Pi.
I have not tried to upload to my website yet. I want to make sure that things are stable.... running local before I try ftping to my site.
The problem that I am having is that very randomly the "last station update" arrow will point down and turns red. Sometimes it will come back to green. But after awhile it will turn red and stay that way. Data in the dashboard will not update and CumulusMX must be restarted to get things working again. I monitor things from my windows XP desktop using the Google Chrome browser pointing to http://192.168.1.200:8998.
I've attached the latest diag file showing the event.
I will continue to test and provide several diag files (in a zip folder) when I have more data.
I have tried several options on the station setup,but I can't get past a 24 hour period where things "lockup".
Is there anything you could suggest that I try?
I make it a point to try and get my answers from the forum before posting. That is why this is my first post because this forum has been such a valuable source of information.
Thanks
Ed

Post by **steve** » Mon 06 Jul 2015 6:13 pm

There's some kind of communication problem between the Pi and the logger, but it's very hard to say what the cause might be. In the run for the file you've uploaded, the problems started straight away - it couldn't download the archive data because it didn't get a response to the command to do that. If you turn on debug logging and data logging, the output in the diags file might throw some more light on it, but it may just confirm that it's not getting responses from the logger.

Just a thought - you're not running Cumulus 1 or some other software with the same station at the same time as MX?

n1iwv · Post by **n1iwv** » Mon 06 Jul 2015 6:39 pm

Hi Steve:
Thanks for the quick reply.
I have it running now..the next time I have to restart CumulusMX I'll enable data logger.
No..I've learned very early that you cannot have two programs trying to get data from WeatherlinkIp at the same time.
I'll keep you posted on my progress.
Ed

n1iwv · Post by **n1iwv** » Wed 08 Jul 2015 2:07 pm

CumulusMX crashed twice. Once yesterday after running most of the day and today after running just a few hours.
I an unable to just restart the program. I have to reboot the PI. If I just restart it, it complains about connecting to the Station.
I zipped up a couple of Diag files.
Ed

Post by **steve** » Wed 08 Jul 2015 2:36 pm

Could you expand on what you mean by "crashed"? A crash is when an unhandled exception occurs which causes the program to terminate unexpectedly. Cumulus will normally print a stack trace when this happens, but that doesn't seem to have happened here.

It looks like it was unable to close down properly, and on restart it was unable to start the HTTP listener for the web server because the address was already in use, so the old process was probably still running. It had successfully connected to the station. Did you look to see if there was a Cumulus process still running before you rebooted the Pi?

You don't seem to have turned the debug logging and data logging on, so it's hard to say what was going on.

n1iwv · Post by **n1iwv** » Sat 11 Jul 2015 3:50 pm

Problem continues. "Data input appears to have stopped"
I am now absolutely certain that I have enabled Debug Logging and Data Logging from the Station Settings/Options menus.
I've attached the latest Diag file. I didn't zip it because it relatively small.
Yesterday it ran almost all day and then stopped logging data from the station.
I didn't include that file because I wasn't certain that I enabled the Debug option/

Thanks
Ed

Post by **steve** » Sat 11 Jul 2015 4:00 pm

That's odd, there doesn't seem to be any extra logging in that file. The best way to turn on the debug and data logging would be by editing Cumulus.ini (with Cumulus stopped) as in this post - https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=12991

Could you also please try adding this line to the [Station] section in Cumulus.ini:

DavisIPResponseTime=1000

Philip, in this thread, found that it helped - https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=14012

n1iwv · Post by **n1iwv** » Sat 11 Jul 2015 6:36 pm

Hi Steve:
I've added those three lines to the [Station] section of the Cumulus.ini file and restated CMX.
Initial observation was that from the dashboard (192.168.1.200:8998), I noticed that the "last Cumulus Update" & the "Last Station Update" times are staying within a couple of seconds of each other and I see no red arrow next to the last Station Update time.
Also the Debug and Data Loggers now show "checked" in the settings menu
I'll let it run for the rest of the day and we'll see how it goes.

Thanks
Ed

n1iwv · Post by **n1iwv** » Sun 12 Jul 2015 4:40 pm

Hi Steve:

It looks like adding line "DavisIPResponseTime=1000" to the [Station] section on Cumulus.ini corrected the problem I was having with CMX and the WeatherLinkIP.
The program has been up and running since yesterday.
Before that, it wouldn't run for more than 8 hours.

I'll keep you posted if anything come up related to this.
I'm having some other minor issues, but I am attempting to see if I can solve them using the resources of the forum.
If I have any questions of these issues, I'll start another topic.

Thanks for all your help Steve.

n1iwv · Post by **n1iwv** » Sat 18 Jul 2015 3:21 pm

Data stopped yesterday 7/17/2015
In the command line on the pi
"_wapi_connect: error looking up socket handle 0X13
I was able to terminate and restart CMX.

Post by **steve** » Sat 18 Jul 2015 3:33 pm

Looks like the logger just stopped sending loop packets (34 out of 50 sent). The wapi error isn't related, it's a result of the WU update. It's not clear from a Google search whether this is a bug in Mono or whether it's just a warning.

Philip is very kindly sending me his WLIP; when it arrives I should be able to tune the MX code so that it works better with the WLIP.

n1iwv · Post by **n1iwv** » Tue 28 Jul 2015 6:40 pm

Screen shot_1.doc

Problem continues. Sometimes it will go several days with no problem and sometimes just a couple of hours.

Post by **steve** » Tue 28 Jul 2015 7:00 pm

This is with the latest build, yes? It's been running without a glitch for me for several days now, so I really thought I'd sorted it. If you zip up your latest MX diags file and attach it, I'll take a look.

n1iwv · Post by **n1iwv** » Tue 28 Jul 2015 8:01 pm

Thanks Steve:

CMX Build is 3025.

I'll double check to see if its the latest

n1iwv · Post by **n1iwv** » Tue 28 Jul 2015 8:10 pm

Hi Steve:
I should have checked the latest build before I posted, I see build 3026.
I'll install it an see how it goes.
Sorry.
Ed

Cumulus Support

CumulusMX "Data input appears to have stopped"

CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"

Re: CumulusMX "Data input appears to have stopped"