-
Notifications
You must be signed in to change notification settings - Fork 181
Replies: 5 comments · 13 replies
-
@Alex-developer, can you comment on the
The directory |
Beta Was this translation helpful? Give feedback.
All reactions
-
I have pressed the button. I've also restarted allsky and rebooted the pi and went so far as to delete whole aborts folder, but the message persists. |
Beta Was this translation helpful? Give feedback.
All reactions
-
please do the following:
Then press the "Clear messages" button in the WebUI and run the two commands again.
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Hmmm... Now the message is finally gone, even without "clear messages".
I'd say that maybe it was a browser cache problem, but the images were updating. Still no overlays, but that's one problem "solved". If it happens again, I'll look to see if that file gets cleared with the button. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@craigim, thanks for running the command. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I am experiencing the exact same issue here. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Kim I assume yours is a pi5 as well? Alex |
Beta Was this translation helpful? Give feedback.
All reactions
-
Correct, Pi 5 and I did update / upgrade the Pi manually, so not after an outage. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@craigim So it was all running fine until you lost power? After loosing power did you update anything on the pi? Thanks Alex |
Beta Was this translation helpful? Give feedback.
All reactions
-
I think my uptime was closing in on 2 months continuous operation before I tripped the circuit. I did not run any updates after turning the breaker back on. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I have reinstalled the master branch, I presume you are both using v2023.05.01_04 ? The install works fine for me so whilst I am investigating you could try commenting out line 21 of ~/allsky/scripts/modules/allsky_shared.py - Just add a # at the start of the line. This will prevent you using any modules that require GPIO but the overlay will work. I am away with work tomorrow (Wed) so if I dont find the problem tonight will look at it again on Thursday Thanks Alex |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 2
-
I'm at work now but will test when I get home. I am using the release branch. I vaguely remember something like this happening before and tracking it down to a rogue lock file or something, but I did not take any notes and I don't remember how I figured that out (and of course this could be false memory). |
Beta Was this translation helpful? Give feedback.
All reactions
-
I commented out the import board on line 21 and after a restart of Allsky the overlays are back. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Same. Error is gone, overlays are back. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Could you please do the following source ~/allsky/venv/bin/activate Then paste the output in here Also please do source ~/allsky/venv/bin/activate And paste that output Thanks |
Beta Was this translation helpful? Give feedback.
All reactions
-
PIP3 list: Package Version Adafruit-Blinka 8.37.0 |
Beta Was this translation helpful? Give feedback.
All reactions
-
PIP3 Outdated: Package Version Latest Type Adafruit-Blinka 8.37.0 8.47.0 wheel |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Beta Was this translation helpful? Give feedback.
-
I tripped the power in my garage where my allsky camera lives. When it came back on, there has been a persistent error in the logs (debug level 4 shown below for a single frame). The images are being captured and saved, but the overlay isn't being written to the image. When I go to the webpage, I also get the "10 uploads have been aborted waiting for others to finish." message, but I've cleared the tmp/aborts file. My tmp directory looks like this:
I'm using the overlay module with these fields: DATE, sEXPOSURE, GAIN, MEAN, DAY_OR_NIGHT, CAMERA_TYPE, and CAMERA_MODEL.
I'm running the following modules: Overlay data on the image, Light Graph, AllSKY Export (day and night) and AllSKY GPS (periodic).
The error seems to be having problems with a GPIO pin, but the only thing I have connected to that is the GPS. Is the module trying to read the GPS directly? I currently have the GPS running using gpsd which is feeding ntpd and both are running find. The PPS is showing a 316ns error and when I run xgps it shows that I'm connected to 11 satellites.
My questions:
I'm running on a Raspberry Pi 5 with the HQ camera. The OS is the latest version of raspberry pi OS.
Beta Was this translation helpful? Give feedback.
All reactions