• T
    Turbo

    Okay: (2) things here:

    Item 1) I Just updated to Mango 3.6.0, and the Modbus tools (Modbus Slave Scan, Modbus Read Data, Write Data, and Point Locator Test) no longer seem to work. You click "read data" and it just sits there on the legacy page, with no error showing up. I did replace the libjssc-java as I discussed in another thread, as otherwise on ARM the property pages won't load at all.

    On the snazzy new page, you click "read data" and you get the following error:

    "Error reading registers - Validation failed, property "configuration.commPortId" -- Required Value"

    This is on a running data source (ie, the system is polling, and data seems to be coming in over the configured data source (in my case, /dev/ttyUSB0)

    Screen shot below.

    Item #2) It appears as if the "flashing save" icon on the legacy Modbus configuration page page never stops flashing after being clicked. I've been playing with this, and set it flashing after changing comm ports, and now it's still flashing, minutes later. Am I missing something with this? I just tried this on the New Point Data Source Configuration Page, and it appears to save properly. Is saving with the Legacy Data Source editor now non-functional for Modbus serial points?

    0_1561443461377_Comm_PortID-RequiredValue.PNG

    posted in User help read more
  • T
    Turbo

    Re: RequestError: Unable to load /data_source_properties.shtm?typeId=MODBUS_IP status: 500

    This was an issue on earlier Mangos, but the new 3.6 upgrade overwrites the jssc-2.8.0.jar with the version that doesn't work on ARM. I'm using ARM for my data aquisition devices, and if you do the 3.6 upgrade it will re-install the nonworking jssc-2.8.0.jar file. So, you'll need to do what was suggested in Topic 4106 again:

    To whit:

    apt-get install libjssc-java

    then

    cp /usr/share/java/jssc-2.8.0.jar /opt/mango/lib

    Otherwise, you get error 500's when trying to edit a data source, and your serial comms won't work on the ARM platform.

    posted in User help read more
  • T
    Turbo

    Ok.

    I've figured this bit out-- Apparently, if you try and import a configuration with the persistent publisher enabled, that seems to cause the errors I was seeing. So, if you get a problem with this, try importing your configs but without the persistent publisher.

    posted in Mango Automation Installation read more
  • T
    Turbo

    Ok.

    Just did this again. I imported a config that I have running on another machine, and.. Crash, with the same error code.

    I'm going to go ahead and try importing one device at a time.

    All the data points added fine, with no error: This install does have the persistent publisher mapped, but not licensed (although it shoudl be-- I've emailed to get my license fxied abotu that).

    The last error message visible is "Initializing H2 connection manager".

    Just before it crashed this time, I was getting error 500's on opening point details when I tried to check the import.

    posted in Mango Automation Installation read more
  • T
    Turbo

    @turbo Just re-installed Mango again, and am going through uploading my config.. So far, no errors, and we seem to be OK.

    This one just came out of the blue, though, so I dunno. I'll let the thread know what I figure out about this.

    posted in Mango Automation Installation read more
  • T
    Turbo

    So. Here's a new one.

    I was working on a Mango machine I installed a week ago, and on a reboot Mango started to give me this "springframework.beans.factory.BeanCreationException: Error creating bean with name 'tokenAuthenticationService'" error.

    Originally, I thought maybe my Java was scrambled, so I re installed Java, and I'm running:
    java version "1.8.0_211"
    Java(TM) SE Runtime Environment (build 1.8.0_211-b12)
    Java HotSpot(TM) Client VM (build 25.211-b12, mixed mode)

    Mango fully started fine, but then started tossing this error on it's own, apparently. I installed, it started, I removed some modules, registered GUID, and then reboot the machine. Now it's giving me this every time it starts up.

    I don't want to dump my entire MA.log file, but, well, here's the end of it:

    ERROR 2019-04-19T19:27:23,352 (com.serotonin.m2m2.Main.main:142) - Error during
    initialization
    org.springframework.beans.factory.BeanCreationException: Error creating bean wit
    h name 'tokenAuthenticationService' defined in URL [jar:file:/opt/mango/lib/mang
    o-3.5.6.jar!/com/infiniteautomation/mango/spring/components/TokenAuthenticationS
    ervice.class]: Bean instantiation via constructor failed; nested exception is or
    g.springframework.beans.BeanInstantiationException: Failed to instantiate [com.i
    nfiniteautomation.mango.spring.components.TokenAuthenticationService]: Construct
    or threw exception; nested exception is com.serotonin.ShouldNeverHappenException
    : java.security.spec.InvalidKeySpecException: encoded key spec not recognized: f
    ailed to construct sequence from byte[]: Extra data detected in stream
    at org.springframework.beans.factory.support.ConstructorResolver.autowir
    eConstructor(ConstructorResolver.java:283) ~[spring-beans-5.0.10.RELEASE.jar:5.0
    .10.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1266) ~[spri
    ng-beans-5.0.10.RELEASE.jar:5.0.10.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1123) ~[sprin
    g-beans-5.0.10.RELEASE.jar:5.0.10.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:535) ~[spring-beans
    -5.0.10.RELEASE.jar:5.0.10.RELEASE]
    at org.springframework.beans.factory.support.AbstractAutowireCapableBean
    Factory.createBean(AbstractAutowireCapableBeanFactory.java:495) ~[spring-beans-5
    .0.10.RELEASE.jar:5.0.10.RELEASE]
    at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$
    doGetBean$0(AbstractBeanFactory.java:317) ~[spring-beans-5.0.10.RELEASE.jar:5.0.
    10.RELEASE]
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
    y.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.0.10.RELE
    ASE.jar:5.0.10.RELEASE]
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
    an(AbstractBeanFactory.java:315) ~[spring-beans-5.0.10.RELEASE.jar:5.0.10.RELEAS
    E]
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
    (AbstractBeanFactory.java:199) ~[spring-beans-5.0.10.RELEASE.jar:5.0.10.RELEASE]
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.
    preInstantiateSingletons(DefaultListableBeanFactory.java:759) ~[spring-beans-5.0
    .10.RELEASE.jar:5.0.10.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.finish
    BeanFactoryInitialization(AbstractApplicationContext.java:867) ~[spring-context-
    5.0.10.RELEASE.jar:5.0.10.RELEASE]
    at org.springframework.context.support.AbstractApplicationContext.refres
    h(AbstractApplicationContext.java:548) ~[spring-context-5.0.10.RELEASE.jar:5.0.1
    0.RELEASE]
    at com.serotonin.m2m2.Lifecycle.springRuntimeContextInitialize(Lifecycle
    .java:407) ~[ma-priv-3.5.6.jar:?]
    at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:311) ~[ma-priv
    -3.5.6.jar:?]
    at com.serotonin.m2m2.Main.main(Main.java:138) ~[ma-priv-3.5.6.jar:?]
    Caused by: org.springframework.beans.BeanInstantiationException: Failed to insta
    ntiate [com.infiniteautomation.mango.spring.components.TokenAuthenticationServic
    e]: Constructor threw exception; nested exception is com.serotonin.ShouldNeverHa
    ppenException: java.security.spec.InvalidKeySpecException: encoded key spec not
    recognized: failed to construct sequence from byte[]: Extra data detected in str
    eam
    at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:1

    1. ~[spring-beans-5.0.10.RELEASE.jar:5.0.10.RELEASE]
      at org.springframework.beans.factory.support.SimpleInstantiationStrategy
      .instantiate(SimpleInstantiationStrategy.java:117) ~[spring-beans-5.0.10.RELEASE
      .jar:5.0.10.RELEASE]
      at org.springframework.beans.factory.support.ConstructorResolver.autowir
      eConstructor(ConstructorResolver.java:276) ~[spring-beans-5.0.10.RELEASE.jar:5.0
      .10.RELEASE]
      ... 14 more
      Caused by: com.serotonin.ShouldNeverHappenException: java.security.spec.InvalidK
      eySpecException: encoded key spec not recognized: failed to construct sequence f
      rom byte[]: Extra data detected in stream
      at com.infiniteautomation.mango.jwt.JwtSignerVerifier.keysToKeyPair(JwtS
      ignerVerifier.java:160) ~[mango-3.5.6.jar:?]
      at com.infiniteautomation.mango.spring.components.TokenAuthenticationSer
      vice.loadKeyPair(TokenAuthenticationService.java:64) ~[mango-3.5.6.jar:?]
      at com.infiniteautomation.mango.jwt.JwtSignerVerifier.<init>(JwtSignerVe
      rifier.java:55) ~[mango-3.5.6.jar:?]
      at com.infiniteautomation.mango.spring.components.TokenAuthenticationSer
      vice.<init>(TokenAuthenticationService.java:42) ~[mango-3.5.6.jar:?]
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      ~[?:1.8.0_211]
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
      orAccessorImpl.java:62) ~[?:1.8.0_211]
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
      onstructorAccessorImpl.java:45) ~[?:1.8.0_211]
      at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1
      .8.0_211]
      at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:1
    2. ~[spring-beans-5.0.10.RELEASE.jar:5.0.10.RELEASE]
      at org.springframework.beans.factory.support.SimpleInstantiationStrategy
      .instantiate(SimpleInstantiationStrategy.java:117) ~[spring-beans-5.0.10.RELEASE
      .jar:5.0.10.RELEASE]
      at org.springframework.beans.factory.support.ConstructorResolver.autowir
      eConstructor(ConstructorResolver.java:276) ~[spring-beans-5.0.10.RELEASE.jar:5.0
      .10.RELEASE]
      ... 14 more
      Caused by: java.security.spec.InvalidKeySpecException: encoded key spec not reco
      gnized: failed to construct sequence from byte[]: Extra data detected in stream
      at org.bouncycastle.jcajce.provider.asymmetric.util.BaseKeyFactorySpi.en
      gineGeneratePrivate(Unknown Source) ~[bcprov-jdk15on-1.60.jar:1.60.0]
      at org.bouncycastle.jcajce.provider.asymmetric.ec.KeyFactorySpi.engineGe
      neratePrivate(Unknown Source) ~[bcprov-jdk15on-1.60.jar:1.60.0]
      at java.security.KeyFactory.generatePrivate(KeyFactory.java:366) ~[?:1.8
      .0_211]
      at com.infiniteautomation.mango.jwt.JwtSignerVerifier.keysToKeyPair(JwtS
      ignerVerifier.java:157) ~[mango-3.5.6.jar:?]
      at com.infiniteautomation.mango.spring.components.TokenAuthenticationSer
      vice.loadKeyPair(TokenAuthenticationService.java:64) ~[mango-3.5.6.jar:?]
      at com.infiniteautomation.mango.jwt.JwtSignerVerifier.<init>(JwtSignerVe
      rifier.java:55) ~[mango-3.5.6.jar:?]
      at com.infiniteautomation.mango.spring.components.TokenAuthenticationSer
      vice.<init>(TokenAuthenticationService.java:42) ~[mango-3.5.6.jar:?]
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      ~[?:1.8.0_211]
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
      orAccessorImpl.java:62) ~[?:1.8.0_211]
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
      onstructorAccessorImpl.java:45) ~[?:1.8.0_211]
      at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1
      .8.0_211]
      at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:1
    3. ~[spring-beans-5.0.10.RELEASE.jar:5.0.10.RELEASE]
      at org.springframework.beans.factory.support.SimpleInstantiationStrategy
      .instantiate(SimpleInstantiationStrategy.java:117) ~[spring-beans-5.0.10.RELEASE
      .jar:5.0.10.RELEASE]
      at org.springframework.beans.factory.support.ConstructorResolver.autowir
      eConstructor(ConstructorResolver.java:276) ~[spring-beans-5.0.10.RELEASE.jar:5.0
      .10.RELEASE]
      ... 14 more
      INFO 2019-04-19T19:27:23,352 (com.serotonin.m2m2.Lifecycle.terminate:422) - Man
      go Lifecycle terminating...
      INFO 2019-04-19T19:27:23,816 (com.serotonin.m2m2.Lifecycle.terminate:571) - Man
      go Lifecycle terminated.

    posted in Mango Automation Installation read more
  • T
    Turbo

    Oh yeah:

    If I use miniterm or something, I can get data out of the /dev/ttymxc devices just fine. And they can listen for incoming things, once again via your local term software, so the ports appear to be showing up.. Just not quite right to Mango.

    posted in User help read more
  • T
    Turbo

    So:

    I'm working with a new IoT device based on ARM. It has several hardware serial ports, mapped to /dev/ttymxc0 through /dev/ttymxc6.

    I was testing this out here, and the hardware serial ports don't seem to work: It looks like Mango is sending the proper string, and the slave device is responding with the proper data (at least according to my scope grab of the bus). But Mango never gets the response.

    I tried every possible setting of flow control and echo, and got the same results. Same setup on the /dev/USBx device (a standard FT232RL cheapo converter) workes just fine.

    Any ideas on troubleshooting this one?

    There's no fire here; It just means I have multiple USB dongles hanging out of the thing, and I'd rather not have that...

    Cheers,
    -Greg

    posted in User help read more
  • T
    Turbo

    Okay. I figured this out:

    (1) This is a small sort of Debian install, supported by Compulab, that is missing some Important Things.
    (2) Part of this is an old (or incomplete) java that doesn't have all the bits to make Mango happy.

    I fixed this by:
    (1) apt-get update--
    Which failed, because the people at Compulab didn't register their certs right, so I had to put the cert data in manually.
    (2) apt-get update worked.
    (3) apt-get install java then did the business.

    We can now configure our data sources without the 500 error.

    However, that opened up the next thing, which seems to be something odd in the serial ports for this device. Was hoping I'd have more time to figure this out, but I'll post this as another thread.

    Cheers,
    -Greg Linder

    posted in How-To read more
  • T
    Turbo

    I've deployed some pretty monster OpenVPN systems going back several years.. It's worked very well, and I'm using it again on our new monitoring product here. It's free, integrated with lots of things, and is generally very useful. Note that we're doing this all on the backend- Our end users have no idea that we're doing this, but that's the way it should be..

    posted in User help read more