Big Crash....... ???

  • Last night at 22.30 I checked MYC to see if all was well. It wasn't. The first graph I looked at had stopped getting data at about 20.35. The next sensors also stopped at that time.

    Looking in more detail, there were HUGE spikes in temperature. The loft which was a cool 24C suddenly registered over 850C and the hot water in the kitchen went to over 9000C !!!!!

    Then I looked into resources->nodes and was shocked to see 6(!) Mys gateways with random id's and all my nodes were totally screwed up. Nodes that never had batteries were reporting battery levels, Nodes suddenly became repeater nodes and sensor values were all muddled (pressure sensor reporint humidity and so on).....

    Sensor widgets lost their data as did many graphs.

    I don't know what caused this. No electrical storms and no power cuts. May be it was a power surge of some type, but nothing else was affected.

    The log for this incident contains a long break in information, but included here for completeness.

    2017-08-14 16:25:14,008 WARN [Quartz_Scheduler_Worker-3] [org.mycontroller.standalone.rule.McRuleEngine:120] Scheduled Rule execution skipped. Engine not available for more than 4000 ms
    [Mon Aug 14 18:27:15 BST 2017] IO error: Received fatal alert: unknown_ca in processing a request from / /
    [Mon Aug 14 18:27:16 BST 2017] IO error: Received fatal alert: unknown_ca in processing a request from / /
    [Mon Aug 14 22:07:37 BST 2017] IO error: Connection has been shutdown: Received fatal alert: unknown_ca in processing a request from / /
    2017-08-14 22:11:47,161 ERROR [Thread-7] [org.mycontroller.standalone.gateway.serialport.SerialDataListenerjSerialComm:94] Exception, 
    java.lang.NegativeArraySizeException: null
    	at org.mycontroller.standalone.gateway.serialport.SerialDataListenerjSerialComm.serialEvent(
    	at com.fazecast.jSerialComm.SerialPort$SerialPortEventListener.waitForSerialEvent(
    	at com.fazecast.jSerialComm.SerialPort$SerialPortEventListener$
    [Mon Aug 14 22:11:49 BST 2017] Accept: Socket closed
    [Mon Aug 14 22:11:49 BST 2017] Unexpected problem running servlet
    org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeException(
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(
    	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(
    	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(
    	at javax.servlet.http.HttpServlet.service(
    	at Acme.Serve.Serve$ServeConnection.runServlet(
    	at Acme.Serve.Serve$ServeConnection.parseRequest(
    	at Acme.Serve.Serve$
    	at Acme.Utils$ThreadPool$
    Caused by: Socket is closed
    	at Acme.Serve.Serve$ServeOutputStream.flush(
    	at Acme.Serve.Serve$ServeOutputStream.close(
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(
    	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(
    	at org.jboss.resteasy.util.DelegatingOutputStream.close(
    	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(
    	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(
    	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(
    	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(
    	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(
    	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(
    	... 12 more

    So, any ideas what happened? This has dented my confidence a little. Maybe I can put a better oiwer supply with UPS on this pi, I have all the things I need to build one (except time OFC)...

    I'm stumped! ???

  • @skywatch Till now I could not guess what causes this issue. But I remember @naguraob reported similar kind of issue. I hope he has some clue on this. mean time could you please send mycontroller.log to my email address? jkandasa at gmail dot com

  • Log sent.

    #is there a way to back up and restore when this happens#?

  • @skywatch Thank you for the email.

    #is there a way to back up and restore when this happens#?

    Yes, you can schedule backup for every hour once. If something goes unrecoverable. do restore from the last backup.

Log in to reply

Suggested Topics