• terrypacker

    In your first post you provided the output from the command line. It looks like you got a 2112 Bus error when it was executing ma-start.sh at line 142. That leads me to believe there is a hardware problem. I thought perhaps the files in the ext-enabled folder were corrupt or on a bad sector of the HD but that is just a guess.

    posted in User help read more
  • terrypacker

    I took a look at the source for ma-start.sh and it looks like it is trying to execute one of your extension from MA_HOME/bin/ext-enabled

    Perhaps that folder is missing, or has a corrupt file in it?

    posted in User help read more
  • terrypacker

    Look at the name of the mango-[version].jar file in MA_HOME/lib. All recent versions of Mango include the version in that filename.

    posted in User help read more
  • terrypacker

    What version of Mango are you trying to start. That error looks like a hardware/os problem but knowing the version will help us find the right version of the startup script and from that the command on line 142.

    posted in User help read more
  • terrypacker

    It looks to me like you are adding a permission to a point that already has a long list of permissions. The maximum size of the permissions columns for data points is 255 characters.

    You say:

    I am trying to add "polycorp" to the read permissions column of this data set "user312,Quser,superadmin".

    But the stacktrace shows this:

    Value too long for column "READPERMISSION VARCHAR_IGNORECASE(255) SELECTIVITY 2": "CAST('MU2user207,MU2user208,MU2user209,MU2user203,MU2user302,MU2user204,MU2user303,MU2user205,MU2user206,polycorp,superadmin,MU2... (266)"; 
    

    Does that point actually have that many permissions on it already?

    posted in User help read more
  • terrypacker

    MattFox is this because there is no chart to download the values from?

    posted in Wishlist read more
  • terrypacker

    Brian,

    That is not currently an option. The existing restrictions are that non-admin users can only edit/view themselves.

    There is an existing permission which should cover this the User's View permission but it does not hide the profile section of the menu.

    I've opened an issue for us to add this for the next release of Mango here

    Thanks.

    posted in How-To read more
  • terrypacker

    Yes, the latest release 3.5.1 of the BacNet module will likely fix this issue if any of your data sources shared a local device and you were using COV subscriptions.

    https://store.infiniteautomation.com/module/BACnet/3.5.1

    posted in User help read more
  • terrypacker

    Brian,

    I replicated the closing of a websocket due to the ping/pong timeout and found that my system handles it gracefully without throwing that java.lang.IllegalStateException. The page stops updating but no errors are produced and I get the same log message about "Didn't receive Pong from Endpoint within..." I replicated this by making the Mango server delay to read the pong message.

    I'm wondering if your browser isn't sending the pong message... (This should happen automatically by most every browser and isn't something you need to code into your page)

    For yet more information on the connection failure you can add this to your log4j2.xml file

    <AsyncLogger includeLocation="true" name="org.eclipse.jetty.websocket.common.io" level="debug"/>
    

    Ah Ok I just got you latest post while drafting this. I'm posting it anyway since I put a little time into it and it could be helpful to someone else in the future.

    posted in Dashboard Designer & Custom AngularJS Pages read more
  • terrypacker

    Thanks Brian,

    It looks like the ping/pong failure is the problem. The other messages are expected during normal operation.

    FYI on the status code meanings:

    Status Code 1001 (Going Away) - This is normal behavior when a page is navigated away from
    Status Code 1006 (No Close Frame) - Connection was terminated in an unclean way, it appears the socket was broken.

    I find it odd that 10s is not long enough to send/receive the messages so I'm thinking you have a network with packet loss. If you can I would suggest pinging the Mango server to see if that is correct. If not then perhaps increasing the env.properties value of

    web.websocket.pingTimeoutMs
    

    will help.

    posted in Dashboard Designer & Custom AngularJS Pages read more