Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
MangoES becomes unreachable
-
Hi !
My MangoES shut down Ethernet communication after a day or two.
Both LED on the Ethernet port is off, but activity on the device (on yellow, and green LED)
The only way to recover is a cold boot, it seems to go back to normal then.
What is this ? -
Hi Stensma,
Can you check out the internal metrics page after your system has been running for a while (and report back a screenshot of that page)? Are you able to SSH to the device? Does your Mango have data sources that use the ethernet? Is there anything in your Mango log, Mango/logs/ma.log?
-
Hi!
Yes I do have Ethernet based sources, and when I think about it this started when I had big problem with 1-wire sources over virtual com ports (USB).
Then I installed Mangon freeware on a raspberryPi and that act as a Modbus IP source towards my MangoES, to access my 1-wire ( witch raspberry Pi has no problem with !!)It answers on ping.
SSH no success yet it refuses connection (tried port 22 and 2222)
Internal metrics page not available yet still booting up right now.
I will update this later, i will browse the log later. -
Interesting. Yeah, there is an issue with the OneWire data source, since it relies on RXTX (which is where the issue is, I believe), where it can initiate a poll and never finish it. It's on our list to move it over to JSSC, as the other serial data sources have been. Still, that shouldn't solely be responsible for what you are describing, but it would be interesting to see the logs.
-
Hi!
First, the 1-wire works fine in RaspberryPi (v3) hardware but not in my MangoES so it is probably more to the hardware side of the USB, in combination with some of the USB/i-wire devices i use.
I could give you more info later, but some of the lost connections an DB hanging is gone using my raspberryPi.But now since I wrote my topic, I restarted my MangoES, it does not behave correct it is not reachable. On the outside it looks like it boots up and run, but it does not appear in web browser nor in SSH.
It does respond to ping.
but when I try to connect with SSH the connection is refused.
I have tried to do a cold boot but it seem not to help.I tried to connect directly the other day with HDMI and USB keyboard but I do not seem to have correct credentials to get logged in. what are they?
Without this access I cannot give you info about the log or system status./S
-
Access solved !
Disk full (or rather my external disk not properly connected where I store some of the log files) so the system did not boot up fully.
So the System status now:
-
Latest Mango log file
-
Some of my findings:
The MangoES has become unreachable due to internal disk is full. (system & kernel log file in GB size) after erasing those it starts up again.
Unreachable when external disk not mounted, where i store all backups and some system log files.
But there must be other reasons as well,
Some errors seems to be caused the USB numbering when I configured the ports in the past I used the port numbers given from the system on boot, so I do see a conflict when I use ttyUSB0 for M-bus in one session and after reboot the port is re-mapped as the internal RS485.
This should be able to configure in the Data source GUI. -
For a V3 MangoES, the RS485 and ttymUSB ports are symlinks based on the device port, so you can rely on that name being given to the device in a particular port. A full disk can definitely prevent many things from functioning... it doesn't even have enough memory for the TAB button to function on the command line!
