• dan

    I can run up a fresh instance with no data points etc and it seems to run, I'll check what version JVM is on there.
    Cheers

    posted in Mango Automation read more
  • dan

    ok, so I went back to the original upgrade process, this time extracting the zip which contains the modules also.

    now the mango process seems to be starting then restarting, looping..
    one of the errors I see is:

    ERROR 2018-09-07 11:39:27,544 (com.serotonin.m2m2.Lifecycle.fullyInitializeWebContext:971) -
    java.lang.NullPointerException
            at com.serotonin.m2m2.Lifecycle.fullyInitializeWebContext(Lifecycle.java:967)
            at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:324)
            at com.serotonin.m2m2.Main.main(Main.java:115)
    ERROR 2018-09-07 11:39:27,555 (com.serotonin.m2m2.Main.main:119) - Error during initialization
    java.lang.NullPointerException
            at com.serotonin.m2m2.Lifecycle.configureStartupDwr(Lifecycle.java:1023)
            at com.serotonin.m2m2.Lifecycle.fullyInitializeWebContext(Lifecycle.java:974)
            at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:324)
            at com.serotonin.m2m2.Main.main(Main.java:115)
    
    

    posted in Mango Automation read more
  • dan

    Thanks for that, I'll try that one.

    Cheers

    posted in Mango Automation read more
  • dan

    Hey Phil, I can't seem to find a bundle pack with all the modules..

    0_1536187014714_47eecce0-06f3-412c-9179-3a0852d67aa8-image.png

    Am I looking in the right place?

    posted in Mango Automation read more
  • dan

    Ah I see, that makes sense ;)
    I'll try that and come back to you.

    Cheers

    posted in Mango Automation read more
  • dan

    this was the result of the overrides folder...

    root@water:/opt/mango# find /opt/mango/overrides/
    /opt/mango/overrides/
    /opt/mango/overrides/properties
    /opt/mango/overrides/properties/env.properties
    /opt/mango/overrides/lib
    /opt/mango/overrides/lib/libjdns_sd.so
    
    

    posted in Mango Automation read more
  • dan

    OK. Now it's looking better, but it's not starting the modules for some reason. Should it be removing the old modules in favour of new ones?
    https://pastebin.com/nFwmvse0

    posted in Mango Automation read more
  • dan

    Ah looks like it hadn't finished deleting the lib folder.
    File operations on these ES boxes seem a little sluggish at times.

    I'll try again now.

    Cheers

    posted in Mango Automation read more
  • dan

    hmm, looks like there's something on the wing...

    It's cycling the startup script now, re-spawning over and over. There are a couple of issues I see in the ma.log

    ERROR 2018-09-05 08:26:33,604 (org.springframework.web.context.ContextLoader.initWebApplicationContext:220) - Context initialization failed
    org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Method 'delegatingApplicationListener' must not be private, final or static; change the method's modifiers to continue
    Offending resource: class path resource [org/springframework/security/config/annotation/web/configuration/WebSecurityConfiguration.class]
    
    ERROR 2018-09-05 08:26:26,624 (org.springframework.web.context.ContextLoader.initWebApplicationContext:220) - Context initialization failed
    org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Method 'delegatingApplicationListener' must not be private, final or static; change the method's modifiers to continue
    Offending resource: class path resource [org/springframework/security/config/annotation/web/configuration/WebSecurityConfiguration.class]
            at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
            at org.springframework.context.annotation.ConfigurationClassMethod.validate(ConfigurationClassMethod.java:61)
            at org.springframework.context.annotation.ConfigurationClass.validate(ConfigurationClass.java:139)
            at org.springframework.context.annotation.ConfigurationClassParser.validate(ConfigurationClassParser.java:167)
            at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:198)
            at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:142)
            at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:599)
            at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:407)
            at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
            at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
            at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
            at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:640)
            at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:229)
            at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1208)
            at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:586)
            at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:449)
            at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
            at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:89)
            at org.eclipse.jetty.server.Server.doStart(Server.java:258)
            at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:58)
            at com.serotonin.m2m2.Lifecycle.webServerInitialize(Lifecycle.java:735)
            at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:177)
            at com.serotonin.m2m2.Main.main(Main.java:106)
    ERROR 2018-09-05 08:26:26,794 (com.serotonin.m2m2.Lifecycle.terminate:360) - com.serotonin.provider.InputStreamEPollProvider
    ERROR 2018-09-05 08:26:26,796 (com.serotonin.m2m2.Lifecycle.terminate:368) - com.serotonin.provider.ProcessEPollProvider
    ERROR 2018-09-05 08:26:26,818 (com.serotonin.m2m2.Main.main:111) - Error during initialization
    java.lang.NullPointerException
            at com.serotonin.m2m2.Lifecycle.configureStartupDwr(Lifecycle.java:792)
            at com.serotonin.m2m2.Lifecycle.webServerInitialize(Lifecycle.java:741)
            at com.serotonin.m2m2.Lifecycle.initialize(Lifecycle.java:177)
            at com.serotonin.m2m2.Main.main(Main.java:106)
    
    

    Then in the dmesg output it looks like it's cycling the process. I might try a reboot, I'll also double check permissions haven't changed after the extraction of the new version?

    [318213.951971] init: mango main process ended, respawning
    [318220.950731] init: mango main process ended, respawning
    [318227.939019] init: mango main process ended, respawning
    [318235.510695] init: mango main process ended, respawning
    [318242.501926] init: mango main process ended, respawning
    
    

    posted in Mango Automation read more
  • dan

    Thanks for that I'll see how the upgrade goes..

    Cheers
    Dan

    posted in Mango Automation read more
  • dan

    Hey Phil, thanks for the info. I'll try the upgrade to 2.8.8.
    I'm not quite sure how to tell which database it's using, I do see info about Mango NoSQL in the System Settings page. It doesn't seem very large, although I did purge a heap of historic data when I first noticed it going slow in the GUI.

    0_1536095846731_8d0a68e5-346e-4298-bc06-b8386c595e82-image.png

    Or is it the top part... H2? That's SQL I think?

    0_1536095930518_edd784bc-3427-400c-bab6-dbc168218301-image.png

    I'll give it a go, I've copied the whole folder sideways, I see the reports folder is massive, it doesn't seem to purge reports after it's sent them via email.

    Cheers
    Dan

    posted in Mango Automation read more
  • dan

    This unit is an older MangoES hardware unit, it's running 2.4.2 still. I wonder if I should upgrade to the latest version. I guess the enterprise licence it came with won't upgrade?

    posted in Mango Automation read more
  • dan

    Re: [Mango consuming 100% CPU](web interface not responding)

    Hey Guys, I reference whileoneloop's similar issues, although I'm having the same issues on a number of mango installations I have around the traps recently. They are all responding very slowly and timing out on the web interface and the CPU on the box running them is using over 100%.

    
      PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
     2678 root      20   0  711504 365344  13468 S 110.6 17.6  73:34.81 java
    
    

    I'm not quite sure where to go from here.
    I can't find where whileoneloop was talking about putting the JAVAOPTS into the startup file, would this be ma-start.sh?

    Regards
    Dan

    posted in Mango Automation read more
  • dan

    Hey Phillip, thanks for that. For the gensets, we're running Moxa MB3180 RS485 - Ethernet MODBUS gateways, they have worked until we put a new instance of Mango in. They also work fine on all of our other sites.
    I will see if I can get some more debugging out of the gateways.

    Cheers
    Dan

    posted in User help read more
  • dan

    Hey Guys, having a really strange problem with our MODBUS TCP data source.
    We have a bunch of solar regulators and a bunch of genset controllers (via Moxa MB3180 converters). Both talk MODBUS / TCP and have all been working up until recently where all the genset controllers (4 in this network) stopped responding.
    The solar regulators are however still working fine.
    All data points in the genset controllers are coming up as unreliable, and are not reporting at all.
    Here is the error I get when trying to interrogate a data point directly...
    0_1525145247750_e4797b2d-2fc2-4e9a-b610-8f66953973aa-image.png
    I've never seen that error before, I tried a quick google and it's pointing towards misconfiguration or overloading of a datapoint, this doesn't seem right as nothing's changed apart from a new instance of Mango on that site.
    The solar regulators using the same type of MODBUS TCP client are still working, just the gensets aren't responding.

    I turned on specific data logging on that data source and got the following, I see I'm getting some kind of response judging by the I and O?

    2018/05/01-13:26:20,240 O 001c00000006010475320019
    2018/05/01-13:26:20,261 I 001c0000000301840a
    2018/05/01-13:27:20,241 O 001d00000006010475320019
    2018/05/01-13:27:20,261 I 001d0000000301840a
    2018/05/01-13:28:20,241 O 001e00000006010475320019
    2018/05/01-13:28:20,261 I 001e0000000301840a
    2018/05/01-13:29:20,241 O 001f00000006010475320019
    2018/05/01-13:29:20,261 I 001f0000000301840a
    
    

    Any ideas would be much appreciated.

    Cheers
    Dan

    posted in User help read more
  • dan

    You might have to bridge the ethernet adapter on the mangoES with the usb WiFi adapter into br0 then give br0 the ip address of the mango instance.
    Then you should be able to see the machine from either interface.

    The default ethernet ip on mine is set in /etc/network/interfaces.d/eth0

    You would have to create a bridge interface, add the eth0 and wlan0 or whichever interface it comes up as to the bridge, then give the bridge the IP Address.

    Cheers
    Dan

    posted in Mango Automation general Discussion read more
  • dan

    I've used Mango as a MODBUS over IP master for years, it works fantastically.

    Regards
    Dan

    posted in Mango Automation general Discussion read more
  • dan

    OK, I think I've resolved it, managed to remove all the settings, add them all in again using port 587, TLS with mailjet and it's working.

    Thanks for your assistance :)

    Cheers
    Dan

    posted in User help read more
  • dan

    I've even tried using localhost as the mail server and tailed the log...

    Apr 11 09:36:04 water postfix/smtpd[9329]: connect from localhost[127.0.0.1]
    Apr 11 09:36:11 water postfix/smtpd[9329]: lost connection after HELO from localhost[127.0.0.1]
    Apr 11 09:36:11 water postfix/smtpd[9329]: disconnect from localhost[127.0.0.1]
    

    It appears that the HELO part is failing. This seems to be related to the hostname, I haven't changed this that I'm aware of however :-/

    WARN  2018-04-11 09:36:04,555 (com.serotonin.m2m2.rt.maint.work.EmailWorkItem.execute:86) - Error sending email
    org.springframework.mail.MailSendException: Mail server connection failed; nested exception is javax.mail.MessagingException: 501 Syntax: HELO hostname
    . Failed messages: javax.mail.MessagingException: 501 Syntax: HELO hostname
    ; message exception details (1) are:
    Failed message 1:
    javax.mail.MessagingException: 501 Syntax: HELO hostname
    
    

    posted in User help read more
  • dan

    This is running on one of those MangoES solid state bad boys. It's been super reliable.

    root@water:~# java -version
    java version "1.8.0-ea"
    Java(TM) SE Runtime Environment (build 1.8.0-ea-b111)
    Java HotSpot(TM) Client VM (build 25.0-b53, mixed mode)
    
    

    posted in User help read more