Need further Troubleshooting - sometimes allsky crashes pi in the morning starting timelapse generating

[starhopper-de]

Hello,
I need help troubleshooting. Our allsky cam operates for more than a year without any problems. From December sometimes no timelapse are created. Checking logs may suggest, that allsky starts new.
Documentation (/documentation/troubleshooting/timelapse.html) does not help, because a timelapseTMP.txt files is not created in my case.

What can I do next?

allsky.log
journal.txt

[starhopper-de]

[EricClaeys]

@starhopper-de, Thomas,
Allsky is restarting because your Pi is rebooting. In the attached log file it rebooted while the startrails is being created.
How often has this happened?
Please attach all the files called /var/log/allsky.log*. There should be at least allsky.log and allsky.log-1.
Please also create 2 windows to the Pi. One where you run generateForDay.sh 20241221 and the other on the WebUI's System page where you constantly refresh it, checking the Throttle bar and the CPU Temperature. It's possible the Pi is overheating and rebooting.

After the next reboot run journalctl to see if there are any messages regarding why it rebooted.

[starhopper-de]

Hallo Eric,
thanks for your reply and your help. I ran generateForDay.sh and observed load, temperature and throttle status. There was no throttle during keo, startrail and timelapse. The temperatur has extended 60°C during startrails and timelapse two times. This is my temperature threshold and therefore the fan switches on and the pi temperatur goes back to the green zone.

allsky.log.1.zip
allsky.log
generateForDay.log

[EricClaeys]

Thanks for the logs. I don't think this is a software problem. The Pi crashes sometimes but not other times, and when it crashes it's usually when startrails are being created but once was when a timelapse started.

How many images do you take a day? It looks like once a minute. Run cd ~/allsky/images; ls 20241223 | wc -l.
Some things to try:

1. Upgrade to v2024.12.06. It probably won't fix the problem but will make troubleshooting easier.
2. Increase your delay, especially during the day, so fewer pictures are taken.
3. Temporarily turn off startrails creation. See if crashes now happen during timelapse creation.
4. Try shrinking the size of the images via "resize", if you aren't already.
5. Temporarily put a delay in between keogram and startrails generation, and between startrails and timelapse. To do so, edit ~/allsky/scripts/endOfNight.sh and add sleep 120 before the line that says "Keogram complete" and another before the "Startrails complete" line. If the Pi is overheating, this will give it a couple minutes to cool down.

When it crashes the Pi's time goes back 10 or so minutes. Something you may want to check on.

[Tys1980]

How are you powering the allsky? I had a similar issue with POE not supplying enough amps.

…

On Tue, 24 Dec 2024, 04:30 Eric Claeys, ***@***.***> wrote: Thanks for the logs. I don't think this is a software problem. The Pi crashes sometimes but not other times, and when it crashes it's *usually* when startrails are being created but once was when a timelapse started. How many images do you take a day? It looks like once a minute. Run cd ~/allsky/images; ls 20241223 | wc -l. Some things to try: 1. Upgrade to v2024.12.06. It probably won't fix the problem but will make troubleshooting easier. 2. Increase your delay, especially during the day, so fewer pictures are taken. 3. Temporarily turn off startrails creation. See if crashes now happen during timelapse creation. 4. Try shrinking the size of the images via "resize", if you aren't already. 5. Temporarily put a delay in between keogram and startrails generation, and between startrails and timelapse. To do so, edit ~/allsky/scripts/endOfNight.sh and add sleep 120 before the line that says "Keogram complete" and another before the "Startrails complete" line. If the Pi is overheating, this will give it a couple minutes to cool down. When it crashes the Pi's time goes back 10 or so minutes. Something you may want to check on. — Reply to this email directly, view it on GitHub <#4101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5CULAAEJZKSYYU53NEG4LT2HDPN5AVCNFSM6AAAAABUBRP6T6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRVGUZTSMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[starhopper-de]

Power is provided by a 12.5V DC line with 0.75 mm2 and is reduced to usb-c 5V within the allsky case. Dome Heating is taken from 12V not from th 5V. But I cannot guarantee for the dc-dc converter.

[starhopper-de]

Thanks for your extensive answer. I will check all the things after x-mas. The time is provided by a ntp server. Timedatectl status shows that it is syncronized well.
Best wishes Thomas