capture_RPiHQ RECODE=137

[jimjackii]

Hi,

what is the meaning of this RETCODE=137?

Sometimes the capture breaks off. Current with version V0.8.3 (new).
RasPi 2B V1.1 and HQ camera.

[EricClaeys]

@jimjackii @AndreasLMeg Every command has a return code which I called "Retcode" for short. 0 is success and non-zero is an error of some type. 137 often means the program crashed, compared to failing to read a file and printing an error message and gracefully exiting with non-zero.
Setting Debug Level to 4 and then attaching the log file with a 137 will help us narrow down where it is crashing.
Someone posted a log file with 137 but Debug Level of 0 which doesn't really help since level 0 produces very little output.

[jimjackii]

@EricClaeys @AndreasLMeg
I will continue to watch.

[jimjackii]

Hi,

Now, I have another error 137.

http://jimjackii.de/files/allsky/20220113/allsky.log

This happened when a manual timelapse video was being created in the background.

[EricClaeys]

@jimjackii Debug Level 4 didn't help. It's unclear if its the Allsky program crashing or the "raspistill" program it calls that actually takes the picture that is crashing. It's possible the "Killed" message is similar to the "killed" message people get when creating a timelapse when their swap space is too small. Try increasing your swap sapce.

How much memory and swap do you currently have?

[jimjackii]

@EricClaeys
I also suspect a memory error or insufficient memory.
The error always occurred when the timelapse was calculated. Either manually or at the end of the night in automatic mode(see my error message #916).

I then set the swap space to 1GB as recommended in the wiki.
In use I have a Rasp Pi 2B with 1GB RAM, whereby I used 50MB for the tempfs.
Since increasing the swap space, the problem has not recurred.

I think the thread can be closed with that.

[EricClaeys]

@jimjackii That's good to hear that increasing the swap space solved the issue.

[jimjackii]

@EricClaeys
Please, you can close this thread.

I can't close the thread yet - there is no close button.

[EricClaeys]

@jimjackii I can't either - apparently Discussions can't be closed but they can be deleted or locked. I'll lock this.