failed to write file - output probably corrupt

[EricClaeys]

As reported by @Lbergoug May 27:
Now it's always "starting"

---

EricClaeys, May 27: @Lbergoug, please follow the instructions on the WebUI's "Getting Support" page and attach the file it creates. Are you running v2024.12.06_03 ?

---

Lbergoug, May 27: This morning, i reboot the rpi4, it's running, i'll see next night if it's ok or not and if the problem already exist, i'll generate support file. Thank you. Yes i run the latest version. It was OK before i use it.

---

Lbergoug, May 28:
@EricClaeys The problem seems to occur when switching from day mode to night mode. Afterwards, even if you reboot, it doesn't work and ends up giving this error message :

Message on web UI :
Mode selection for 2028:1520:12:P
    SRGGB10_CSI2P,1332x990/0 - Score: 3456.22
    SRGGB12_CSI2P,2028x1080/0 - Score: 1083.84
    SRGGB12_CSI2P,2028x1520/0 - Score: 0
    SRGGB12_CSI2P,4056x3040/0 - Score: 887
Mode selection for 4056:3040:12:P
    SRGGB10_CSI2P,1332x990/0 - Score: 10552.2
    SRGGB12_CSI2P,2028x1080/0 - Score: 8179.84
    SRGGB12_CSI2P,2028x1520/0 - Score: 7096
    SRGGB12_CSI2P,4056x3040/0 - Score: 0
Still capture image received
ERROR: *** failed to write file - output probably corrupt ***   (4 occurrences, last on mai 27, 11:43:15 )	
********************   (8 occurrences, last on mai 27, 11:43:16 )	
*** capture_RPi: ERROR: maximum number of consecutive errors of 4 reached; capture program stopped. Total errors=4.   (mai 27, 11:43:16 )	
Make sure cable between camera and Pi is all the way in.   (mai 27, 11:43:16 )	
Look in /home/allsky/allsky/tmp/capture_RPi_debug.txt for details.   (mai 27, 11:43:16 )

when i generate with support.sh:

./support.sh: ligne 194: /usr/bin/mktemp: Liste d'arguments trop longue
./support.sh: ligne 193: /system.txt: Permission non
./support.sh: ligne 310: /usr/bin/cp: Liste d'arguments trop longue
./support.sh: ligne 319: /usr/bin/cp: Liste d'arguments trop longue
....

---

Lbergoug, May 29:
I solve support.sh trouble
support-none-20250528202918.zip

I don't know why, but this night it seems to be OK. see tomorow

This morning all seems to be OK. Timelapse and startrail are generated and uploaded on remote website https://tlb-astro.bergougnoux.eu/ even i don't know why its ok now.
the two modification I made is to resolve support.sh trouble

[EricClaeys]

@Lbergoug,
You've got a few things going on:

1. There were several of these messages: ERROR: *** failed to write file - output probably corrupt ***. I'm pretty sure the rpicam-still command is creating this message, but I have no idea why it happens, but it went away when you restarted Allsky on May 28 at 19:55:05. It's possible your ~/allsky/tmp was full.

   Please run df -h|grep -E "Filesystem|allsky" now and if you see that message again.

2. This error appears for almost every image: rm of image.jpg failed! Trying again.... Is there a file on your remote server whose name starts with image.jpg, for example, image.jpg-old?

3. The overlay system is giving this error: WARNING: Image not set so ignoring. I've asked @Alex-developer about this.

4. The first half of the log file had this message for every image: unable to open image /home/allsky/allsky/darks/0.jpg': Aucun fichier ou dossier de ce type. There may be a bug in the dark subtraction code, as I assume it wasn't 0 degrees C ?

   Please run ls -l ~/allsky/darks

[EricClaeys]

@Lbergoug,

UPDATE:

1. This message: ERROR: *** failed to write file - output probably corrupt *** IS because your ~/allsky/tmp ran out of space. Yours is 300 MB which should be a LOT more than is needed, so I suspect something is creating a huge number of files and not removing them.
   allsky/tmp is cleaned up after a reboot, so it's interesting that you still have the problem after a reboot.

Can you think of anything that may be creating files in allsky/tmp? A module perhaps?

Please still run:

df -h | grep -E "Filesystem|allsky"
ls -l ~/allsky/darks

Also run:

tree --du -h ~/allsky/tmp > /tmp/tree.txt

then upload the /tmp/tree.txt file.

[Alex-developer]

The image warning is due to there being an image on the overlay with no image set, if you look in the overlay manager there will be an image where the image is currently set to 'Select Image;. Either select an image or delete the field

{
  "image": "missing",
  "x": 2028,
  "y": 1013,
  "tlx": 1964,
  "tly": 949,
  "id": "oe-field-45"
},

[EricClaeys]

@Alex-developer,
Can the Overlay Editor highlight this and other fields that need attention?