I have two Wansview W3 WiFi/Ethernet cameras connected via WiFi to my Zoneminder 1.29 VM by RTSP and have been having an issue with them daily. Namely, the feeds "stop" and I'm not able to view them. The root /zm/ page has the feeds red. Clicking on them, verifying settings, and re-saving the options makes them work A-OK... until it happens again. Digging some into it via
, there are two connections to each camera stuck in a "CLOSE_WAIT" status. My understanding is the cameras send a TCP packet with the "FIN" flag set, but never send anything else to actually close the port, resulting in this port to just hang out indefinitely, waiting to finish closing out the TCP session by the camera. My latest attempt at fixing was writing a script do a
, grepping out for the IP and "CLOSE_WAIT," then killing the process id associated with it (obtained via
. It still never comes back up though, unless I go into the web UI and re-save the settings, which isn't an option when I want to execute it as a cron-job every minute. Executing
to reload the settings for that monitor isn't sufficient either. Latest firmware available from the company applied (whose response was essentially "our app works fine!" I'm sure it does indeed work fine - for about a day then I'll have the same issue...). Changing the feeds to use a captured JPG image works indefinitely, but runs at 1-2 FPS, rather than the camera-limited 15 FPS over RTSP/h264.
Any thoughts/scripting suggestions to execute an equivalent "re-save?"
A few more details:
OS: Debian Stretch VM
ZM: 1.29 via stretch-backports
WiFi AP: Ubiquiti AC-AP-Pro
Gigabit switch in-between AP and Host PC