HELP -- New Install

[BWentler]

The tail of cascading failures.

Cumulus MX was running fine on a ESXi VM running Windows 2012 (64 bit). The hosting ESXi server had a HD "failure" in the RAID 5 setup. I forced the drive back online but this corrupted the complete ESXi volume. I setup this VM and another server 2016 to use a NFS share off a FreeNAS box for MS Backup to backup to and this was working great. In my attempts resolve the faulure, I deleted all the VM's running off this corrupted ESXi volume and selected "Remove from Disk" thinking this would quickly place me at ground zero to delete the ESXi volume and start over. It was not until I went to rebuild the VM's that I discovered my hasty mistake/oversight. For in deleting the VM and the vdvm's on the local ESXi server, I told ESXI to delete the ones on the FreeNAS NFS share. All my backups for these two VM's are gone......

I have since started to rebuild what I had lost and now working on returning Cumulus MX to working state on the server 2012 VM. I have download the latest, un-zipped to Server 2012 and then Window 10 OS's but get the following error:

Windows 2012, 64bit (Admin command prompt & after running "netsh http add urlacl url=http://*:8998/ user=\users")
C:\CumulusMX>CumulusMX.exe
Current culture: English (United States)
Serial: BFDF97AE01C73D83A58EC41F78A4291F
Cumulus MX v.3.2.6 build 3062

Unhandled Exception: System.OverflowException: Value was either too large or too small for an Int32.

at System.Convert.ToInt32(Double value)
at CumulusMX.Cumulus.DoSunriseAndSunset()
at CumulusMX.Cumulus..ctor(Int32 HTTPport)
at CumulusMX.Program.Main(String[] args)

Windows 10, 64bit (Admin command prompt)
C:\CumulusMX>CumulusMX.exe
Current culture: English (United States)
Serial: 3B8FBE606B6D119DFE7042411FAC9DD2
Cumulus MX v.3.2.6 build 3062

Unhandled Exception: System.OverflowException: Value was either too large or too small for an Int32.
at System.Convert.ToInt32(Double value)
at CumulusMX.Cumulus.DoSunriseAndSunset()
at CumulusMX.Cumulus..ctor(Int32 HTTPport)
at CumulusMX.Program.Main(String[] args)1

I tried doing the same thing with with version 3043 and got somewhat the same error.

I noticed that new ZIP files are not containing a sample Cumulus.ini file.

Any suggestions?

[mcrossley]

I'm not sure why this happening, and I cannot reproduce the error.
Do you any sort of backup of your Cumulus.ini file somewhere?

[BWentler]

No....

I had several copies on the other VM but that was "deleted" with removing all the VM's on the ESXi.

The weak link/single point of failure was the VM config.

[mcrossley]

Could you try creating a new Cumulus.ini with just to following content...

Code: Select all

[Station]
Latitude=38
Longitude=-99

And see if MX will start then?

[BWentler]

Finally got back to this.

Thank you mcrossley for the start of the ini file. I used these lines (replaced with my info) and saved the INI file. I also noticed that Windows SmartScreen stops the startups when ever I started Cumulus. So I white listed cumulusmx.exe and all is well in the weather reporting.

These errors might have been Windows SmartScreen in the end but maybe it was both not having a Cumulus.ini file and SmartScreen.

Thank you for your help!