Working camera but occasional errors

[greenman45]

Hello, I'm getting what seems like random errors. Thing is, startrails, keograms and timelapses are working as they should. All the time, every day, which is new for me, and great!

2025-06-05T05:32:26.259843-04:00 ASC allsky[213181]: *** generateForDay.sh ERROR: '--upload' specified but nowhere to upload!

Followed by this after several attempts but only sometimes.
2025-06-06T04:51:40.487395-04:00 ASC allsky[2278]: ERROR: Device timeout detected, attempting a restart!!!
allsky.log
allsky.log

And unrelated, I have installed modules several times to play around with, but so far have never been able to make any of them work over multiple versions.

[EricClaeys]

@greenman45,

Thanks for the logs. I see several things in your logs I don't understand and would like to get more information.
Please run checkAllsky.sh and post the results.
Also, please attach ~/allsky/tmp/metadata.txt, then follow the instructions on the WebUI's "Getting Support" page and post the support log it creates.

The "but nowhere to upload" message means your Keogram, Startrails, and/or Timelapse (I believe all 3 in your case) have their Upload setting enabled but you haven't specified anyplace to upload them to, i.e., your local and remote Websites are not defined.
Uncheck those three settings and those messages will go away.
You only see those messages every morning because that's when keograms, startrails, and timelapse are created.

For the "timeout" errors, your RPi camera is timing out, which most likely means it hung and Allsky killed it.

Would you please do the following:

sudo systemctl stop allsky
> /var/log/allsky.log
## Change the Debug Level in the WebUI to 4 and save changes

Sometime during the day, upload /var/log/allsky.log.

Thanks - Eric

[greenman45]

checkAllsky.sh
---------- Warning (items that may keep parts of Allsky running) ----------

'Remove Bad Images Threshold Low' is 0 (disabled).
FIX: Set to a value greater than 0 unless you are debugging issues.
    Try 0.1 and adjust if needed.
-----
'Remove Bad Images Threshold High' is 0 (disabled).
FIX: Set to a value greater than 0 unless you are debugging issues.
    Try 0.9 and adjust if needed.

---------- Summary ----------
Warnings: 2

I made these changes, thanks!

[EricClaeys]

@greenman45,
You have Daytime Auto-Exposure enabled but a Daytime Mean Target of 0. Are you sure you want that? That combination causes Allsky to use the camera's auto-exposure algorithm instead of Allsky's auto-exposure algorithm. We suggest leaving Auto-Exposure on and setting a Mean Target to something other than 0. The default Daytime value is 0.5.

[greenman45]

Thanks, I set it to 0.5.

[greenman45]

I changed the Debug Level in the WebUI to 4 and saved changes
restarted the software and will post the allsky.log tomorrow. Thanks again!

[greenman45]

Wanted to share this screenshot of the errors i'm seeing in the WebUI every day, and i'm including the allsky.txt log in the next message.

[EricClaeys]

@greenman45,
I just updated Allsky to not display the blue lines - they weren't errors, and to print a warning instead of the red line.
The RPi camera is hanging while taking a picture, and Allsky detects this and kill the command that hung, then continues with the next image. If it only happens occassionally you can ignore it, but if you get a lot of the "timeout" messages, let me know.
Other users have seen this and the Raspberry Pi team that support the camera hasn't found the cause yet, which is why the latest Allsky release detects the hang and recovers (prior Allsky releases would also hang).

Would you please update to the latest v2024.12.06_04 release?
If you have an existing allsky-OLD directory, either remove it or rename it to allsky-OLDEST.
Then stop allsky and cd; mv allsky allsky-OLD, then run the same git clone --branch .... command you recently ran.

[greenman45]

I didn't change all the toggles for uploading keograms, time lapses and star trails until today. I didn't realize there is a section for each one, so that is done today. There was a smart plug that restarted the raspberry pi every morning because I it had been locking up so much (last version) and I have disabled that now that everything is working much better and I understand the errors I was having. Here is the log you wanted. Thanks
I have to say that this version is working much better for me now. : )
allsky.log

[EricClaeys]

I have to say that this version is working much better for me now

Great! Thanks for the feedback. That's always our goal, and I agree the last few releases have overall been much better and the "Getting Support" page is working really well now.