W8ADA
Ever since I received my openSPOT2 it has been exhibiting some odd behavior. If I leave the unit run for 6 or 7 hours, the web interface resets (it does this in all browsers) and makes the OS2 control page no longer loadable - I just get a blank page trying to load. The only fix I have found for this is unplugging the openSPOT2 and plugging it back in to reboot.
I can check in my router and see it is still connected and has an IP assigned to it, yet entering the address no longer works after the OS2 crashes. Most times this happens it is on a TG and still sends out data to the radio, but sometimes it totally crashes the OS2 where it neither sends nor receives anything after the crash. If I recall correctly, when this happens the LED changes from alternating green and red to some other pattern. Not sure on this as it has only totally crashed a handful of times, the rest of the times it just crashes the web interface.
HA2NON
Can you ping the IP address when this happens?
Does this also happens if the web interface is not opened?
Which modem mode and connector do you use? Does it happen with other connectors?
What is the LED pattern you see?
G4TKO
I have exactly the same problem since the V51 update
This happens maybe 1 or twice per day
John
W8ADA
It just happened again in only several hours of uptime. This time I can confirm the red light is glowing on and off and no radio is being passed by the OS2. I read elsewhere I believe this means it's lost its WiFI connection; not sure, will wait for an expert. I can confirm from the router that the unit no longer has an IP on the WiFi network as it should. All I know to do for now is pull the plug on the OS2 and have it reboot.
After the reboot (by pulling the plug) I had to wait a long time, but finally it announced via the modem and started passing audio on the last TG again. Also the web interface is reachable again after this long reboot. And obviously it is showing up in the router with its proper IP.
W8ADA
Can you ping the IP address when this happens?
When it does not fully crash, just the web interface, the OS2 still has an address and IP on my network that could be pinged, but in the above crash, the OS2 disappears from the network entirely.
Does this also happens if the web interface is not opened?
Yes when the OS2 fully crashes and disappears from the LAN.
Which modem mode and connector do you use? Does it happen with other connectors?
I am using the Homebrew/MMDVM BrandMeeister DMR radio interface. An Anytone AT-D878UV is the radio I am using, but it happens on the other TYT radio as well...
What is the LED pattern you see?
When it crashes like it just did (fully) the light was pulsating red bright and dim.
W8ADA
OK, so I just watched the log as it crashed at 3 hours uptime. It says it has lost its connection and tries to ping gstatic to see if it is reachable, which it was not and timed out after 3 tries. I can still ping the unit, but it no longer is assigned an IP by my router (router says unknown for the device ID and IP address) and only shows its MAC address. It is still keying my radio on the last active TG but is totally erratic.
Rebooting my router doesn't set the OS2 with a new IP, but I can reach the interface after rebooting the router which caused the OS2 to connect and disconnect from the WiFi. It will still only have an active IP once I pull the plug on the OS2 and let it reboot.
After pulling the plug on the OS2 waiting 30 seconds and plugging it back in, it reacquires its IP address and performance
for now
is restored.
W8ADA
When the unit totally crashes I receive the red on and off as in "Hardware error."
http://manuals.sharkrf.com/openspot2/en/gif/hwerror.gif
Last night I let it run and all that happened was the web interface reset, but surprisingly refreshing the browser brought the control panel back up and uptime was at 14 hours. This is not typical.
So I have seen two behaviors, both which crash the web control, but one that crashes the OS2 entirely also and the LED indicates "Hardware error" - although today all that crashed was the web interface.
I spoke too soon. While writing this the OS2 reset and reacquired its IP. Of course the web interface broke while the unit was cycling and getting its IP back. The unit completely cycled as the uptime is back to 0:00. As far as LED's, while it was rebooting I saw almost all of the different LED states save maybe blue???
HA2NON
Please connect the OS2 to a computer and enter the "log" command (without the double quotation marks) into the USB serial console to turn logging on, and send us any relevant log section to
info@sharkrf.com
W8ADA
Please connect the OS2 to a computer and enter the "log" command (without the double quotation marks) into the USB serial console to turn logging on, and send us any relevant log section to
info@sharkrf.com
I am not quite sure I know how to do this; I'll check the manual, but a brief explanation would be helpful. For instance do I set a static IP in the OS2 so I can send it the log command? I have never had it plugged into a PC.
W8ADA
OK, so I logged in with PuTTy and am seeing the realtime log. What do you suggest I do to get relevant log data to you when this malfunction happens at random intervals?
HA2NON
You can set PuTTY to save the output to a file.
KD6QFO
Can the log show timestamps? If not, this would be a very helpful feature. Not all of us have tome to sit and watch a Realtime log.
HA2NON
The log does not timestamp, because the terminal emulator can append timestamp to the logs. PuTTY can do it if you enable it.
W8ADA
I will send my log to the specified address. This log just shows, "httpsrv[0]: websocket closed" "httpcln: connect error" and some failed net checks then it tries to create a new token and log in that then fails. During this log (at the end when I walked back into the shack) I did get the web control page to come back up after a handful of refreshes. Status of OS2, still running on the talkgroup that was in use, but the web interface no longer shows it connected to a TG.
There is some issue with the webserver setup you are using or this unit has a unique hardware issue; although this seems doubtful. It was still running and did not exhibit the hardware error red flashing LED this time either.
With exception to this one time, the only fix for this is to power cycle the OS2. Does no one else ever leave their OS2 on for 6 or more hours? If you do, does the web interface crash? BTW, all browsers react the same.
**UPDATE** The web interface went back down and will not come back up; I will have to power cycle the OS2.
W8ADA
So the web interface only crashes if you have it in a browser window open and monitoring it. Last night I started the OS2 up WITHOUT opening the web interface; it ran for over 16 hours and I was still able to log on to the web control panel for the time being this morning. I will update this when it fails again.
LA9ULA
I am not sure if this is related, but I have noticed, both with version 51 and the previous one, that the web browser (firefox) sometimes (quite often) looses connection and will not load the OS2-page again. I think this happens when the PC is idle and goes to sleep. In addition to unplugging and plugging the OS2 again, which has already been mentioned, I have found that changing the profile from the radio using DTMF commands will make web browser load the web page again.
(I am using a Yaesu/Fusion radio). Hope this might be of some help?
Best regards
Bjørnung
W8ADA
Yes I tried loading the profile by calling (in my case) 9001 yet the web interface still stays down. Also my computer does not sleep; not even the screen. I am trying to capture what happens now with PuTTY and OBS recording the web interface with the log file.
HA2NON
Thank you for providing more information. Changing profiles reboot the device. This is also noted in the user manual.
k7cet
I am having the same problem or very similar . My OS2 unit does not crash but after leaving status page loaded on Firefox for several hours, Firefox always goes to a blank loading page . From then, I cannot load the web interface from OS2 . Using Firefox or Chrome no load until I unplug OS2 and make it reboot . I have the latest beta firmware . The OS2 unit continues to operate, I just can't get the web browser to connect until I unplug and power up the OS2 again .
Ping to OS2 is good .
It happened just now in less than two hours after rebooting OS2 .
I guess I need to learn how to connect using PuTTY and get a logging stream ?