allsky: Image upload error + no keogram / timelapse / star trails produced today only
I’ve tried to keep up with the many new releases / files and this could be a case of delete it all and start again!
To avoid confusion, I have 2 x RPI4bs and 2 x ASi178MCs (outdoors is standard, indoors test one is the cooled version).
Outside known as Allsky PI, inside test one Allsky PI 2.
My log file on the inside test Allsky PI 2 says it’s v0.8.1 and for the past couple of days, the image upload (i.e. ‘live-view’ image) to my NAS fails.
Here’s the log from the latest attempt (personal details obscured with ******):
Oct 5 20:54:56 allsky allsky.sh[3453]: STARTING EXPOSURE at: 2021-10-05 20:54:56 Oct 5 20:54:56 allsky allsky.sh[3453]: > Extra Text File Age Disabled So Displaying Anyway Oct 5 20:54:56 allsky allsky.sh[3453]: > Saving image ‘image.jpg’ that started at 2021-10-05 20:54:56 (0 us) Oct 5 20:54:56 allsky allsky.sh[3453]: > Sleeping: 29988 ms Oct 5 20:54:58 allsky allsky.sh[3453]: *** upload.sh: ERROR: Oct 5 20:54:58 allsky allsky.sh[3453]: FILE_TO_UPLOAD=‘image.jpg’ Oct 5 20:54:58 allsky allsky.sh[3453]: REMOTE_DIR=‘/Allsky/Allsky PI 2/images’ Oct 5 20:54:58 allsky allsky.sh[3453]: TEMP_NAME=‘SI-26766’ Oct 5 20:54:58 allsky allsky.sh[3453]: DESTINATION_FILE=‘image.jpg’ Oct 5 20:54:58 allsky allsky.sh[3453]: put: image.jpg: Access failed: 550 SI-26766: Forbidden filename Oct 5 20:54:58 allsky allsky.sh[3453]: mv: Access failed: 550 SI-26766: No such file or directory Oct 5 20:54:58 allsky allsky.sh[3453]: Commands used (run via: lftp -f /home/pi/allsky/tmp/lftp_cmds.txt): Oct 5 20:54:58 allsky allsky.sh[3453]: open --user “" --password "” ftp://*********** Oct 5 20:54:58 allsky allsky.sh[3453]: set net:max-retries 2 Oct 5 20:54:58 allsky allsky.sh[3453]: set net:timeout 20 Oct 5 20:54:58 allsky allsky.sh[3453]: rm -f SI-26766 Oct 5 20:54:58 allsky allsky.sh[3453]: put “image.jpg” -o SI-26766 Oct 5 20:54:58 allsky allsky.sh[3453]: rm -f “image.jpg” Oct 5 20:54:58 allsky allsky.sh[3453]: mv SI-26766 “/Allsky/Allsky PI 2/images/image.jpg” Oct 5 20:54:58 allsky allsky.sh[3453]: bye
This is on my test PI indoors. There doesn’t appear to be any ‘saveImageNight.sh’ entries. The FTP settings are correct and match the PI outdoors which is also running v0.8.1 (from the log), albeit a different folder (Allsky, not Allsky 2).
The PI outdoors seems to be working fine, and I’ve had no issue with timelapse, startrails and keogram generation on the PI outdoors, albeit cloudy and wet ones!
Oct 5 21:02:53 allsky allsky.sh[828]: STARTING EXPOSURE at: 2021-10-05 21:02:53 Oct 5 21:02:54 allsky allsky.sh[828]: saveImageNight.sh: Uploading ‘image.jpg’ with timestamp: 21:02:53 Oct 5 21:03:23 allsky allsky.sh[828]: > Saving image ‘image.jpg’ that started at 2021-10-05 21:02:53 (0 us) Oct 5 21:03:23 allsky allsky.sh[828]: > Sleeping from auto exposure: 0 ms (0 sec) Oct 5 21:03:23 allsky allsky.sh[828]: STARTING EXPOSURE at: 2021-10-05 21:03:23 Oct 5 21:03:24 allsky allsky.sh[828]: saveImageNight.sh: Uploading ‘image.jpg’ with timestamp: 21:03:24 Oct 5 21:03:54 allsky allsky.sh[828]: > Saving image ‘image.jpg’ that started at 2021-10-05 21:03:23 (0 us) Oct 5 21:03:54 allsky allsky.sh[828]: > Sleeping from auto exposure: 0 ms (0 sec) Oct 5 21:03:54 allsky allsky.sh[828]: STARTING EXPOSURE at: 2021-10-05 21:03:54 Oct 5 21:03:55 allsky allsky.sh[828]: saveImageNight.sh: Uploading ‘image.jpg’ with timestamp: 21:03:54 Oct 5 21:04:24 allsky allsky.sh[828]: > Saving image ‘image.jpg’ that started at 2021-10-05 21:03:54 (0 us) Oct 5 21:04:24 allsky allsky.sh[828]: > Sleeping from auto exposure: 0 ms (0 sec) Oct 5 21:04:24 allsky allsky.sh[828]: STARTING EXPOSURE at: 2021-10-05 21:04:24 Oct 5 21:04:25 allsky allsky.sh[828]: saveImageNight.sh: Uploading ‘image.jpg’ with timestamp: 21:04:24
All of the files are saving fin on the PI in home/pi//allsky/inages, and thre are keograms etc since the last update (3rd of October) but this morning’s (5th of October) failed with the following in the log:
Keogram
Oct 5 07:15:37 allsky allsky.sh[3564]: endOfNight.sh: ===== Generating Keogram Oct 5 07:15:42 allsky allsky.sh[3564]: > Extra Text File Age Disabled So Displaying Anyway Oct 5 07:15:42 allsky allsky.sh[3564]: > Saving image ‘image.jpg’ that started at 2021-10-05 07:15:36 (0 us) Oct 5 07:15:42 allsky allsky.sh[3564]: > Sleeping from histogram exposure: 30000 ms Oct 5 07:15:43 allsky allsky.sh[3564]: *** upload.sh: ERROR: Oct 5 07:15:43 allsky allsky.sh[3564]: FILE_TO_UPLOAD=‘image.jpg’ Oct 5 07:15:43 allsky allsky.sh[3564]: REMOTE_DIR=‘/Allsky/Allsky PI 2/images’ Oct 5 07:15:43 allsky allsky.sh[3564]: TEMP_NAME=‘SI-16085’ Oct 5 07:15:43 allsky allsky.sh[3564]: DESTINATION_FILE=‘image.jpg’ Oct 5 07:15:43 allsky allsky.sh[3564]: put: image.jpg: Access failed: 550 SI-16085: Forbidden filename Oct 5 07:15:43 allsky allsky.sh[3564]: mv: Access failed: 550 SI-16085: No such file or directory Oct 5 07:15:43 allsky allsky.sh[3564]: Commands used (run via: lftp -f /home/pi/allsky/tmp/lftp_cmds.txt): Oct 5 07:15:43 allsky allsky.sh[3564]: open --user “" --password "” ftp://****** Oct 5 07:15:43 allsky allsky.sh[3564]: set net:max-retries 2 Oct 5 07:15:43 allsky allsky.sh[3564]: set net:timeout 20 Oct 5 07:15:43 allsky allsky.sh[3564]: rm -f SI-16085 Oct 5 07:15:43 allsky allsky.sh[3564]: put “image.jpg” -o SI-16085 Oct 5 07:15:43 allsky allsky.sh[3564]: rm -f “image.jpg” Oct 5 07:15:43 allsky allsky.sh[3564]: mv SI-16085 “/Allsky/Allsky PI 2/images/image.jpg” Oct 5 07:15:43 allsky allsky.sh[3564]: bye Oct 5 07:16:04 allsky allsky.sh[3564]: terminate called after throwing an instance of ‘std::out_of_range’ Oct 5 07:16:04 allsky allsky.sh[3564]: what(): basic_string::substr: __pos (which is 140) > this->size() (which is 0) Oct 5 07:16:04 allsky allsky.sh[3564]: scripts/endOfNight.sh: line 72: 9272 Aborted “${ALLSKY_HOME}/keogram” -d “${DATE_DIR}/” -e ${EXTENSION} -o “${UPLOAD_FILE}” ${KEOGRAM_PARAMETERS}`
Startrails
Oct 5 07:16:04 allsky allsky.sh[3564]: endOfNight.sh: ===== Generating Startrails Oct 5 07:16:05 allsky allsky.sh[3564]: Usage: startrails [-v] -d <dir> -e <ext> [-b <brightness> -o <output> | -s] Oct 5 07:16:05 allsky allsky.sh[3564]: #033[31mSource directory and file extension are always required. Oct 5 07:16:05 allsky allsky.sh[3564]: brightness threshold and output file are required to render startrails#033[0m Oct 5 07:16:05 allsky allsky.sh[3564]: Arguments: Oct 5 07:16:05 allsky allsky.sh[3564]: -h : display this help, then exit Oct 5 07:16:05 allsky allsky.sh[3564]: -v : increase log verbosity Oct 5 07:16:05 allsky allsky.sh[3564]: -s : print image directory statistics without producing image. Oct 5 07:16:05 allsky allsky.sh[3564]: -d <str> : directory from which to read images Oct 5 07:16:05 allsky allsky.sh[3564]: -e <str> : filter images to just this extension Oct 5 07:16:05 allsky allsky.sh[3564]: -o <str> : output image filename Oct 5 07:16:05 allsky allsky.sh[3564]: -S <int>x<int> : restrict processed images to this size Oct 5 07:16:05 allsky allsky.sh[3564]: -b <float> : ranges from 0 (black) to 1 (white). Default 0.35 Oct 5 07:16:05 allsky allsky.sh[3564]: #011A moonless sky may be as low as 0.05 while full moon can be as high as 0.4 Oct 5 07:16:05 allsky allsky.sh[3564]: ex: startrails -b 0.07 -d …/images/20180208/ -e jpg -o startrails.jpg
Timelapse
- Oct 5 07:16:05 allsky allsky.sh[3564]: endOfNight.sh: ===== Generating Timelapse
- Oct 5 07:16:10 allsky allsky.sh[3564]: timelapse.sh: Processing 1387 images…
- Oct 5 07:16:11 allsky allsky.sh[3564]: [swscaler @ 0x791c50] deprecated pixel format used, make sure you did set range correctly
- |
- |
- |
- Oct 5 07:30:13 allsky allsky.sh[3564]: timelapse.sh: Timelapse was created
- Oct 5 07:30:14 allsky allsky.sh[3564]: *** upload.sh: ERROR:
- Oct 5 07:30:14 allsky allsky.sh[3564]: FILE_TO_UPLOAD=‘/home/pi/allsky/images/20211004/allsky-20211004.mp4’
- Oct 5 07:30:14 allsky allsky.sh[3564]: REMOTE_DIR=‘’
- Oct 5 07:30:14 allsky allsky.sh[3564]: TEMP_NAME=‘TL-26567’
- Oct 5 07:30:14 allsky allsky.sh[3564]: DESTINATION_FILE=‘allsky-20211004.mp4’
- Oct 5 07:30:14 allsky allsky.sh[3564]: put: /home/pi/allsky/images/20211004/allsky-20211004.mp4: Access failed: 550 TL-26567: Forbidden filename
- Oct 5 07:30:14 allsky allsky.sh[3564]: mv: Access failed: 550 TL-26567: No such file or directory
- Oct 5 07:30:14 allsky allsky.sh[3564]: Commands used (run via: lftp -f /home/pi/allsky/tmp/lftp_cmds.txt):
- Oct 5 07:30:14 allsky allsky.sh[3564]: open --user “" --password "” ftp://******
- Oct 5 07:30:14 allsky allsky.sh[3564]: set net:max-retries 2
- Oct 5 07:30:14 allsky allsky.sh[3564]: set net:timeout 20
- Oct 5 07:30:14 allsky allsky.sh[3564]: rm -f TL-26567
- Oct 5 07:30:14 allsky allsky.sh[3564]: put “/home/pi/allsky/images/20211004/allsky-20211004.mp4” -o TL-26567
- Oct 5 07:30:14 allsky allsky.sh[3564]: rm -f “allsky-20211004.mp4”
- Oct 5 07:30:14 allsky allsky.sh[3564]: mv TL-26567 “allsky-20211004.mp4”
- Oct 5 07:30:14 allsky allsky.sh[3564]: bye
With my limited understanding of this, the common denominator appears to be the NAS. I don’t think it’s a NAS access issue, but I suppose I should check that too. Nothing else has an issue accessing the location. It’d the ‘Access failed: 550 TL-26567: Forbidden filename’ that says it’s not an access issue, but then also says ‘mv: Access failed: 550 TL-26567: No such file or directory’ which would suggest it can’t see the location or has been refused.
If this is totally weird and I need to delete allsky and start again with a fresh clone, that’s fine, but it might be more sinister. As I said, it could be a case of a botched installation i.e. mix / match of versions, but as both versions are shown as 0.8.1 in the logs, I have to assume they’re the same and I haven’t done something silly.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 68
@maphilli14 sorry, it’s called
generateForDay.sh
. Eric