ha7ilm
commented
8 years ago Hi Daniel,
Thanks for reporting that. This kind of bug is hard to find without direct access to the system, and I am planning to set up public receiver(s) myself as well to be able to debug things like that.
However, the first question is to see if it is OpenWebRX that hangs, or it is the receiver (via the rtl_sdr tool). The RTL-SDR can randomly fail for various reasons (but typically because of insufficient power supply or getting overheated).
Could you add csdr through | csdr fifo in the input chain at the config?
This is the original line:
start_rtl_command="rtl_sdr -s {samp_rate} -f {center_freq} -p {ppm} -g {rf_gain} -".format(rf_gain=rf_gain, center_freq=center_freq, samp_rate=samp_rate, ppm=ppm)This is the modified line:
start_rtl_command="rtl_sdr -s {samp_rate} -f {center_freq} -p {ppm} -g {rf_gain} - | csdr through | csdr fifo".format(rf_gain=rf_gain, center_freq=center_freq, samp_rate=samp_rate, ppm=ppm)- With
csdr through, you will be able to monitor the speed of the I/Q sample stream. csdr fifowill always take all the possible input, even if the other end (in the OpenWebRX script) failed. If it happens, it will emit a lot of:circular buffer full, so don't pipe stderr into a log file.
It would help to see what you get at the console with these new settings while the system hangs.
VY 73!
Andras, HA7ILM
daniel5457h
JonathanThorpe
tejeez
Hi,
I'm trying to set up a public SDR for listening CB comms near Barcelona, Spain and help the local CB enthusiasts listening each other when the QRM is high (URL http://z-ha-dum.dyndns.org:8080). However, it hangs once or twice every day, no errors are given on the log. I tried on a Rasbberry Pi 3 running Raspbian and in a NUC 6I3 running Ubuntu 16.04. Same thing.
When this happens, new clients reach this in the OpenWebRX log: "WebSocket opened to ws://z-ha-dum.dyndns.org:8080/ws/", but they never see the "Web Audio API succesfully initialized, sample rate: 44100 sps" that appears when it's running ok. No audio and no waterfall.
So, any hints? Or maybe, is there any way I can increase the debug information / logging so we can properly locate the issue here?
By the way, our of despair, I'll just settle happily with a patch for a forced exit of OpenWebRX everytime this happens, I can have systemd restarting it as may times as it has to.
Best regards, Daniel, EA3HRU.