Missing a reason for end of a session

[Sergio558]

I'm running the program in unattended mode, collecting data in CSV format to a file. Sometimes, I notice that the program finishes, but the CSV file contains no information for an exit's reason. It would be helpful if there were a way to retrieve it somehow.

[zuckschwerdt]

You can write a log file with system messages: rtl_433 -F csv:csv.log -F log:rtl433.log

[Sergio558]

I did start new session with the new parameter for create log file.

Just before it, got a stop of last run with a one message on console:

cb transfer status: 4, canceling...

[merbanan]

This comes from librtlsdr:

https://github.com/osmocom/rtl-sdr/blob/84195f169f5b4b7dc06a10efb1e210d02b49e51c/src/librtlsdr.c#L1735

Ie not part of rtl_433 and most likely some hardware issue. A restart usually fix things.

[Sergio558]

I'll watch the stoppage by checking log file periodically.

Perhaps "[R82XX] PLL not locked!" message related to the status "4" sometimes.

[zuckschwerdt]

You can ignore that line. The PLL does lock, but late. You might want to try -D restart or a supervisor like supervisord or systemd to automate restarts. Maybe just a shell script similar to

while sleep 10 ; do rtl_433 ALL YOU OPTIONS ; done

[Sergio558]

I'm running it on Windows 10.

Got new reason from log file:

Input: Async read stalled, exiting!

Update 4/27
Input: Async read stalled, exiting!

Again, same reason. :(