• R
    raylatbasix

    Thanks for the excellent support today Phil!!

    posted in MangoES Hardware read more
  • R
    raylatbasix

    I was in the parent directory for the java-8-oracle. Tried it both ways, still no luck.

     Note <filename> must be a regular (non-symlink) file.
    > cd /usr/lib/jvm/
    > sudo setcap 'cap_net_bind_sevice=+ep' java-8-oracle/bin/java
    fatal error: Invalid argument
    usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]
    
     Note <filename> must be a regular (non-symlink) file.
    > sudo setcap 'cap_net_bind_sevice=+ep' /usr/lib/jvm/java-8-oracle/bin/java
    fatal error: Invalid argument
    usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]
    
     Note <filename> must be a regular (non-symlink) file.
    

    posted in MangoES Hardware read more
  • R
    raylatbasix

    @phildunlap said in Java update to 1.8 162 has caused Mango ES 3.2.2 to become unreachable.:

    sudo setcap 'cap_net_bind_sevice=+ep' java-8-oracle/bin/java

    Just upgraded to 1.8 162. Having an issue with the:

    sudo setcap 'cap_net_bind_sevice=+ep' java-8-oracle/bin/java
    

    Throws an invalid argument error for setcap:

    > sudo setcap 'cap_net_bind_sevice=+ep' java-8-oracle/bin/java
    fatal error: Invalid argument
    usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]
    
     Note <filename> must be a regular (non-symlink) file.
    

    Any ideas?

    posted in MangoES Hardware read more
  • R
    raylatbasix

    Thanks Phil,

    So I should be safe to attempt a java update back to 1.8 162, and perform you additional steps??

    Also, it seems all of my licensing on the modules page shows as "Unlicensed" or free mode now. Any Idea how to fix that? I'm guessing in this mode, I'm limited on my point count to 300, and I am well over that.

    Thanks.

    posted in MangoES Hardware read more
  • R
    raylatbasix

    ma.log file error:

    ERROR 2018-02-13T10:48:32,418 (com.serotonin.m2m2.Main.main:129) - Error during initialization 
    java.lang.RuntimeException: java.net.SocketException: Permission denied
    	at com.serotonin.m2m2.Lifecycle.webServerInitialize(Lifecycle.java:922) ~[ma-priv-3.2.2.jar:?]
    	at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:199) ~[ma-priv-3.2.2.jar:?]
    	at com.serotonin.m2m2.Main.main(Main.java:125) [ma-priv-3.2.2.jar:?]
    Caused by: java.net.SocketException: Permission denied
    	at sun.nio.ch.Net.bind0(Native Method) ~[?:1.8.0_131]
    	at sun.nio.ch.Net.bind(Net.java:433) ~[?:1.8.0_131]
    	at sun.nio.ch.Net.bind(Net.java:425) ~[?:1.8.0_131]
    	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[?:1.8.0_131]
    	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[?:1.8.0_131]
    	at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:317) ~[jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721]
    	at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) ~[jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721]
    	at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235) ~[jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721]
    	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721]
    	at org.eclipse.jetty.server.Server.doStart(Server.java:390) ~[jetty-server-9.3.11.v20160721.jar:9.3.11.v20160721]
    	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[jetty-util-9.3.11.v20160721.jar:9.3.11.v20160721]
    	at com.serotonin.m2m2.Lifecycle.webServerInitialize(Lifecycle.java:919) ~[ma-priv-3.2.2.jar:?]
    	... 2 more
    INFO  2018-02-13T10:48:32,431 (com.serotonin.m2m2.Lifecycle.terminate:361) - Mango Lifecycle terminating... 
    ERROR 2018-02-13T10:48:32,447 (com.serotonin.m2m2.Lifecycle.terminate:436) - com.serotonin.provider.InputStreamEPollProvider 
    ERROR 2018-02-13T10:48:32,449 (com.serotonin.m2m2.Lifecycle.terminate:444) - com.serotonin.provider.ProcessEPollProvider 
    FATAL 2018-02-13T10:48:32,459 (com.infiniteautomation.zwave.rt.ZwaveControlCenter.<init>:62) - Z-Wave Device configuration directory at:  does not exist! 
    FATAL 2018-02-13T10:48:32,459 (com.infiniteautomation.zwave.rt.ZwaveControlCenter.<init>:68) - Z-Wave user data directory at:  does not exist, Mango will shutodwn.! 
    INFO  2018-02-13T10:48:32,466 (com.serotonin.m2m2.Lifecycle.terminate:480) - Mango Lifecycle terminated. 
    
    

    So it was some sort of permission issue. How do you recommend updating java ??

    posted in MangoES Hardware read more
  • R
    raylatbasix

    Hi Phil,

    > java -version
    java version "1.8.0_131"
    Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
    Java HotSpot(TM) Client VM (build 25.131-b11, mixed mode)
    

    I put it back to 1.8 131 thinking there was an issue.

    cd /opt/mango/bin; ./ma.sh start
    

    Appears to start the service ok, I am now able to access the Mango UI.

    Is this because I tried to restart via Webmin using the mango user account?

    I am trying to solve a Java memory leak issue by updating java from 1.8 131 to something newer. What did I miss on performing the java update?

    posted in MangoES Hardware read more
  • R
    raylatbasix

    Just tried performing a Java update after uploading the 32-bit ARM version of the java update using the following recommended commands:

    tar -xvzf jdk-*.tar.gz
    cp -rf jdk1.8.0_162/* java-8-oracle/
    rm -r jdk1.8.0_162
    rm jdk-*.tar.gz
    

    All seemed to go ok, I rebooted system from Webmin, and not I cannot access the Mango UI. Webmin is still accessible though. Thinking there was an issue with this version of Java, I used the same above procedure to put it back to Java 1.8 131 as it was before, rebooted via webmin, and I am still not able to access the Mango UI. Any assistance would be appreciated.

    posted in MangoES Hardware read more
  • R
    raylatbasix

    Thanks Phil. I should be all set.

    posted in User help read more
  • R
    raylatbasix

    Thanks Phil. I'm not all that familiar using python scripts in Mango. In playing around a little, I've noticed that I can export these points to a CSV file. It seems to arrange the point data quite nicely. From there, it looks like I can easily update the Device Names a lot faster using excel. After making my Device name changes in the CSV, can I import this like I would a JSON file, and have it update the existing data point device names automatically? Or, do i need to stick to trying to modify this import using JSON.

    Thanks again for the help!

    posted in User help read more
  • R
    raylatbasix

    I have over 400 points from about 45 different bacnet controllers that were discovered under one local bacnet ip device called "bacnet_network" using Mango 3.3.0. The issue is that I now have all of these points referring to their device name as "bacnet_network" instead of their actual bacnet device name (ie. VAV1). So when look at a list of points, the only thing that i can see is a column called "Device" that refers to the correct numerical bacnet device id for the particular device for a given set of bacnet points. I need to display the "friendly name" of the bacnet device, and not the device id.
    Example: I now have 45 points listed as "bacnet_network - zonetemp", where as I need them to display "VAV1 - zonetemp, VAV2 - zonetemp, etc.).

    It appears that I could open up each point individually, and change the device name to something other than the local bacnet device name of "bacnet_network", but that could be rather tedious, and prone to error. Any help on this would be appreciated. The funny thing is, when these points were initially discovered, Mango correctly indicated the correct "friendly" name of each parent bacnet device before I added their points to the system.

    posted in User help read more