Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Error status LED on startup and resulting software crash
-
aussiewmr
- Posts: 104
- Joined: Wed 23 Sep 2009 8:27 am
- Weather Station: Davis VP2+
- Operating System: Windows 10 Pro 1903
- Location: Brisbane Australia
- Contact:
Error status LED on startup and resulting software crash
Hi All,
I have latest build (1025) Cumulus running on a Fine Offset with UV station and when I start Cumulus I see the Red Error Status LED Flashing. Clicking on it brings up a log with the following:
26/12/2011 8:16:12 PM : Error plotting charts at line 1 of dayfile.txt: List index out of bounds (0)
26/12/2011 8:16:12 PM : Please correct the error by editing dayfile.txt
I cannot find a "dayfile.txt" file anywhere and when I use Cumulus to try to edit it (Edit | dayfile.txt) Cumulus crashes. The crash log seems to point to the dayfile.txt being missing.
I am not too sure how to get around this issue. I have tried the following:
1. Left Cumulus shutdown for 1/2 hr (WS 3081 is set to log every 5 mins) and then started up, let cumulus download all the data logs
2. Manually created the file in question with "123" as content in Cumulus base directory.
Both to no effect.
Crash log is attached, any help appreciated.
Cheers
Phil
I have latest build (1025) Cumulus running on a Fine Offset with UV station and when I start Cumulus I see the Red Error Status LED Flashing. Clicking on it brings up a log with the following:
26/12/2011 8:16:12 PM : Error plotting charts at line 1 of dayfile.txt: List index out of bounds (0)
26/12/2011 8:16:12 PM : Please correct the error by editing dayfile.txt
I cannot find a "dayfile.txt" file anywhere and when I use Cumulus to try to edit it (Edit | dayfile.txt) Cumulus crashes. The crash log seems to point to the dayfile.txt being missing.
I am not too sure how to get around this issue. I have tried the following:
1. Left Cumulus shutdown for 1/2 hr (WS 3081 is set to log every 5 mins) and then started up, let cumulus download all the data logs
2. Manually created the file in question with "123" as content in Cumulus base directory.
Both to no effect.
Crash log is attached, any help appreciated.
Cheers
Phil
You do not have the required permissions to view the files attached to this post.
http://www.ourbackyard.net/weather - using a VP2+
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Error status LED on startup and resulting software crash
It looks like the dayfile.txt file exists, but is empty; this doesn't happen under the normal course of events - I assume this is a new installation? Someone else had a similar issue recently, and I tried to reproduce the case of an empty file being created, but couldn't. I also added code which I thought would prevent the crash if this situation did somehow occur; perhaps your situation is slightly different.
If you zip up the diags folder and attach it, I'll see if I can offer any help.
If you zip up the diags folder and attach it, I'll see if I can offer any help.
Steve
-
aussiewmr
- Posts: 104
- Joined: Wed 23 Sep 2009 8:27 am
- Weather Station: Davis VP2+
- Operating System: Windows 10 Pro 1903
- Location: Brisbane Australia
- Contact:
Re: Error status LED on startup and resulting software crash
Hi Steve,
Man that was a quick reply.
Diags attached.
BTW - this happened in the previous version as well (1022 i think). I had a version I downloaded a week or so ago then say the update from yesterday but it made no difference.
Phil
Man that was a quick reply.
Diags attached.
BTW - this happened in the previous version as well (1022 i think). I had a version I downloaded a week or so ago then say the update from yesterday but it made no difference.
Phil
You do not have the required permissions to view the files attached to this post.
http://www.ourbackyard.net/weather - using a VP2+
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Error status LED on startup and resulting software crash
The diags logs don't go back far enough to show any problems relating to dayfile.txt. If you've been running Cumulus for more than one day, you should have one, and it shouldn't have been empty. This suggests that there is some problem with the midnight rollover. The date in yesterday.ini also suggests this:
26/12/2011 18:55:35.554 : Read yesterday file: Date = 00/00/00 Date now = 26/12/2011
If you still have a dayfile.txt with just your test string in it, I suggest you delete that file and then wait until tomorrow to see what happens. If you still have a problem then, attach the diags folder again.
Edit: I just noticed that you said "2. Manually created the file in question with "123" as content in Cumulus base directory." The dayfile.txt file goes in the data folder. So your file will be having no effect. What files do you actually have in the data folder? Perhaps if you zip up the data folder and attach it I might be able to see something.
26/12/2011 18:55:35.554 : Read yesterday file: Date = 00/00/00 Date now = 26/12/2011
If you still have a dayfile.txt with just your test string in it, I suggest you delete that file and then wait until tomorrow to see what happens. If you still have a problem then, attach the diags folder again.
Edit: I just noticed that you said "2. Manually created the file in question with "123" as content in Cumulus base directory." The dayfile.txt file goes in the data folder. So your file will be having no effect. What files do you actually have in the data folder? Perhaps if you zip up the data folder and attach it I might be able to see something.
Steve
-
aussiewmr
- Posts: 104
- Joined: Wed 23 Sep 2009 8:27 am
- Weather Station: Davis VP2+
- Operating System: Windows 10 Pro 1903
- Location: Brisbane Australia
- Contact:
Re: Error status LED on startup and resulting software crash
That's it Steve,
When I put arbiturary stuff in the file in the Data folder all is good.
I omitted to tell you that today is the first time Cumulus has run on the weather station. So thats how to replicate the issue - brand new install, or even delete the data folder contents would do it I guess.
Do you expect this behavior for the first day or is that what the crash prevention code you referred to is supposed to handle?
I will wait till tomorrow and see how it all goes.
Thanks for your time Steve.
When I put arbiturary stuff in the file in the Data folder all is good.
I omitted to tell you that today is the first time Cumulus has run on the weather station. So thats how to replicate the issue - brand new install, or even delete the data folder contents would do it I guess.
Do you expect this behavior for the first day or is that what the crash prevention code you referred to is supposed to handle?
I will wait till tomorrow and see how it all goes.
Thanks for your time Steve.
http://www.ourbackyard.net/weather - using a VP2+
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Error status LED on startup and resulting software crash
Ah - quite important information, as I point out in the 'please click here before posting' message.aussiewmr wrote:I omitted to tell you that today is the first time Cumulus has run on the weather station.
A new install doesn't create an empty dayfile.txt, and the code which tries to use the file at startup checks for the existence of the file and doesn't flash the error light (it may log messages to the diags file). I tried a new install and this is how it behaves. There was a problem where if you tried to use the dayfile editor on the first day, when no dayfile.txt file exists, and you click 'OK', then that would create an empty dayfile.txt file, so then there was the possibility of an empty dayfile.txt file. I believe I have fixed this problem a few builds ago.So thats how to replicate the issue - brand new install, or even delete the data folder contents would do it I guess.
Do you expect this behavior for the first day or is that what the crash prevention code you referred to is supposed to handle?
I've just renamed my dayfile.txt file and started Cumulus and got no flashing error light. I used the dayfile editor and clicked 'OK' and got no empty dayfile.txt created. You say you have no dayfile.txt in your data folder, but you are getting the error message that you get if the file exists but is empty. So I'm afraid I have run out of ideas, sorry. I would repeat my advise to delete the empty dayfile.txt file, and then presumably after your first rollover the file would get created as usual and all would then be well, but you have no file to delete, so for some reason the code which checks whether the file exists isn't working properly on your system.
Steve
-
aussiewmr
- Posts: 104
- Joined: Wed 23 Sep 2009 8:27 am
- Weather Station: Davis VP2+
- Operating System: Windows 10 Pro 1903
- Location: Brisbane Australia
- Contact:
Re: Error status LED on startup and resulting software crash
HI Steve,
I do have the file.
I thought I didn't because I was looking in the base directory, but when you pointed out it was in the Data directory I looked there and bingo it was there but empty.
After finally finding the file I put rubbish like "123" in it (like I did for the early attempt in the base dir) and now I don't get the error on start-up and I can use the editor.
So as per your advice I will delete the empty dayfile and wait till tomorrow and all should be great.
I guess what I was trying to let you know was in may case, a new install, on day one with an empty dayfile.txt when I use the dayfile editor Cumulus crashes.
Thanks
Phil
EDIT:
PS I read the FAQ but yes I did not do the "Click Here" bit - sorry. I am a bit colour challenged and the links don't stand out real clear - the longer ones stand out better than the one worder ones
I do have the file.
I thought I didn't because I was looking in the base directory, but when you pointed out it was in the Data directory I looked there and bingo it was there but empty.
After finally finding the file I put rubbish like "123" in it (like I did for the early attempt in the base dir) and now I don't get the error on start-up and I can use the editor.
So as per your advice I will delete the empty dayfile and wait till tomorrow and all should be great.
I guess what I was trying to let you know was in may case, a new install, on day one with an empty dayfile.txt when I use the dayfile editor Cumulus crashes.
Thanks
Phil
EDIT:
PS I read the FAQ but yes I did not do the "Click Here" bit - sorry. I am a bit colour challenged and the links don't stand out real clear - the longer ones stand out better than the one worder ones
http://www.ourbackyard.net/weather - using a VP2+
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Error status LED on startup and resulting software crash
Yes; the problem is that you don't normally get an empty dayfile.txt; it doesn't get created until there's something to put in it. There must be some other way for it to happen (since I think I have stopped the dayfile editor being able to create one), but I have no idea what that is.aussiewmr wrote:I guess what I was trying to let you know was in may case, a new install, on day one with an empty dayfile.txt when I use the dayfile editor Cumulus crashes.
Anyway, I'll stop the dayfile editor crashing if the file is empty, and it's probably best if you delete your empty file.
Steve
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Error status LED on startup and resulting software crash
That's OK, it's clear that very few people read it anyway. I did have the 'here' bit in large flashing capitals at one point, but I thought that was a bit silly. Didn't seem to help anywayaussiewmr wrote:PS I read the FAQ but yes I did not do the "Click Here" bit - sorry. I am a bit colour challenged and the links don't stand out real clear - the longer ones stand out better than the one worder ones
Steve
-
aussiewmr
- Posts: 104
- Joined: Wed 23 Sep 2009 8:27 am
- Weather Station: Davis VP2+
- Operating System: Windows 10 Pro 1903
- Location: Brisbane Australia
- Contact:
Re: Error status LED on startup and resulting software crash
Hi Steve 90% of people who "play" with weather stations would have to be male
(we should run a poll). That means RTFM as a last resort - a big flashing HERE would be in the manual category.
Anyway all is good - I have a dayfile, no crashing etc.
As soon as I make room on my PayPal acct from Christmas activities I will send a donation your way.
Phil
Anyway all is good - I have a dayfile, no crashing etc.
As soon as I make room on my PayPal acct from Christmas activities I will send a donation your way.
Phil
http://www.ourbackyard.net/weather - using a VP2+