Cumulus Support

Help! What have I done?
I have recently migrated my setup to run from a Raspberry Pi 2 running CumulusMX and everything seemed to be working great bar a few minor niggles. One of which was the uploading of the my dayfile.txt to my webserver. I had successfully created a "curl" command to upload the file and had added it as a daily file process and additionally had changed my FTP password and changed that through the MX console, saved it off and then rebooted my Pi to make sure everything was clean.
At this point, it all seemed to stop working. The console would no longer connect and my website is no longer updating.
I manually added the logging option into my Cumulus.ini to see what is going on, but as you can see from the attached MXDiag file, it is apparantly hanging after processing the "Logging Interval" line. I have rebooted numerous times, but, nothing! it always gets to the same point in the MXDiag file.

I do wonder if something has become corrupt, but where do I start?
Hope someone has a bright idea?

here's the file:

Are you running from an SD card? If so, perhaps it is corrupt, that's quite common. If you remove any passwords from your Cumulus.ini and attach it here, I'll take a look.

Thanks Steve. Attached is my Cumulus.ini
There does seem to be some sort of networking issue as far a the webserver element of Cumulus is concerned.
I can connect via Putty and also use WinSCP to connect to the Pi, so I know there is a working network connection, however, connecting to the ip address using a browser says:

"This web page is not available

ERR_CONNECTION_REFUSED"

which suggests that webserver isn't running on the pi maybe?

bigmac wrote:which suggests that webserver isn't running on the pi maybe?

Yes, it hasn't got as far as starting it. It hasn't got very far at all, but there are no error messages. I'll have a look at your ini file.

Are you not getting an error message on the command line?

Your MySQL port has somehow got the value -1 rather than the default of 3306. Cumulus initialises the details even if you're not using MySQL, and -1 is not a valid port number.

Aha, found out why!
It was the port setting for the MySQL server. I had been playing around with this earlier and had then deleted all the MySQL information. When I saved it off after deleting it, I did get an error message (can't remember what now though), but didn't really think much about it as everything carried on working.

Looking at the port number in the Cumulus.ini it is "-1". Changed it to 3600 and everything started working.

posting at the same time Steve!

Hopefully my explanation above gives you more info?