Page 1 of 1

OTmonitor stops working randomly and Deamon not working

Posted: Mon Nov 02, 2015 9:09 pm
by Stingone
Hello Everyone,

For a couple of days now i hooked-up my OTGW to my raspberry PI. When i start the OTmonitor it works for couple of minutes till max 45 min. Then suddenly it stops working and i need to restart the otmonitor. When lucky it still reads the data but often i have to wait for couple of minutes after reboot. Has this maybe to do with the fact that it needs USB with external power?

The other issue is that i cant seem to startup the OTmonitor at start-up. Does anyone has a decent process to manage this?

When i run

Code: Select all

./otmonitor-ahf --daemon -f /opt/otmonitor/otmonitor.conf
sometimes it workes... sometimes not and then getting the output below

Code: Select all

no display name and no $DISPLAY environment variable
    while executing
"load /opt/otmonitor/otmonitor-ahf/lib/tk8.6/libtk8.6.so Tk"
    ("package ifneeded Tk 8.6.4" script)
    invoked from within
"package require Tk"
    (file "/opt/otmonitor/otmonitor-ahf/gui.tcl" line 2)
    invoked from within
"source /opt/otmonitor/otmonitor-ahf/gui.tcl"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list source [file join /opt/otmonitor/otmonitor-ahf $file]]"
    (procedure "include" line 2)
    invoked from within
"include gui.tcl"
    (file "/opt/otmonitor/otmonitor-ahf/otmonitor.tcl" line 1620)
    invoked from within
"source /opt/otmonitor/otmonitor-ahf/otmonitor.tcl"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list source [file join /opt/otmonitor/otmonitor-ahf $file]]"
    (procedure "include" line 2)
    invoked from within
"include otmonitor.tcl"
    (file "/opt/otmonitor/otmonitor-ahf/main.tcl" line 13)

Re: OTmonitor stops working randomly and Deamon not working

Posted: Thu Nov 05, 2015 2:38 pm
by hvxl
Computers are known for their consistency in doing the same thing when given the same inputs. It is therefor hard to believe that your Raspberry Pi is producing random results when started with the same command. Are you sure you always type the command correctly? I can see how you would get the reported error message if you forget the "-f" in your command.

I don't completely understand the rest of your story. You say you need to restart otmonitor but often have to wait a couple of minutes after reboot. How does a reboot come into play here?

Does otmonitor report anything when it terminates? Can you run the command "ulimit -c unlimited" before you start otmonitor and then check if there's a file called "core" after it terminates?

OTmonitor does not require USB.