• Categories
    • Recent
    • Tags
    • Popular
    • Register
    • Login

    Final 1.0.0 errors and crash report....

    Scheduled Pinned Locked Moved Troubleshooting
    mysgw
    40 Posts 4 Posters 7.7k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • skywatchS Offline
      skywatch
      last edited by jkandasa

      Here's todays problems with MYC on a pi2......

      2017-10-01 14:44:30,684 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/bin/tmp]
2017-10-01 14:44:30,700 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts]
2017-10-01 14:44:30,701 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/conditions]
2017-10-01 14:44:30,703 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/operations]
2017-10-01 14:44:30,707 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/www/_configurations]
2017-10-01 14:44:30,708 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/persistent_stores]
2017-10-01 14:44:30,818 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2017-10-01 14:44:34,229 INFO [main] [org.mycontroller.standalone.db.migration.V1_01__Initial_Configuration:398] Migration completed successfully.
2017-10-01 14:44:34,486 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_01__SNAPSHOT:63] Migration completed successfully.
2017-10-01 14:44:34,621 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_02__SNAPSHOT:127] Migration completed successfully.
2017-10-01 14:44:34,733 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_03__SNAPSHOT:48] Migration completed successfully.
2017-10-01 14:44:34,834 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_04__SNAPSHOT:107] Migration completed successfully.
2017-10-01 14:44:34,934 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_05__0_0_3_alpha1:49] Migration completed successfully.
2017-10-01 14:44:35,193 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_04__2016_Apr_25:58] Migration completed successfully.
2017-10-01 14:44:35,206 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_01__2016_Mar_24:340] Migration completed successfully.
2017-10-01 14:44:35,366 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_02__2016_Apr_11:66] Migration completed successfully.
2017-10-01 14:44:39,448 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_03__2016_Apr_14:85] Migration completed successfully.
2017-10-01 14:44:39,617 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_04__2016_Apr_25:58] Migration completed successfully.
2017-10-01 14:44:39,672 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_05__2016_Apr_27:68] Migration completed successfully.
2017-10-01 14:44:39,723 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_06__2016_May_10:49] Migration completed successfully.
2017-10-01 14:44:39,769 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_07__2016_May_19:57] Migration completed successfully.
2017-10-01 14:44:39,834 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_08__2016_Jul_01:108] Migration completed successfully.
2017-10-01 14:44:39,879 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_09__2016_Jul_16:93] Migration completed successfully.
2017-10-01 14:44:39,926 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_10__2016_Jul_29:53] Migration completed successfully.
2017-10-01 14:44:39,977 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_01__2016_Aug_03:66] Migration completed successfully.
2017-10-01 14:44:40,028 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_02__2016_Aug_06:63] Migration completed successfully.
2017-10-01 14:44:40,070 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_03__2016_Sep_20:95] Migration completed successfully.
2017-10-01 14:44:40,109 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_04__2016_Oct_19:61] Migration completed successfully.
2017-10-01 14:44:40,151 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_05__2016_Nov_18:77] Migration completed successfully.
2017-10-01 14:44:40,278 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_06__2017_Mar_03:66] Migration completed successfully.
2017-10-01 14:44:40,715 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:161] Number of migrations done:22
2017-10-01 14:44:40,718 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.0.0.Final, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.03.06 - 2017 Mar 03), Built on:2017-09-25T11:00:11+0530, Git commit:07c3a228b9c861280fe2f560ed4d1097349d08bb:master]
2017-10-01 14:44:41,017 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/persistent_stores/mc]
2017-10-01 14:44:41,676 INFO [Thread-8] [org.mycontroller.standalone.message.RawMessageQueue:54] Cleared offline messages[0] from the queue.
2017-10-01 14:44:42,666 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:52] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, bindAddress=0.0.0.0, httpPort=1883, websocketPort=7080, allowAnonymous=false)
2017-10-01 14:44:45,177 INFO [main] [org.mycontroller.standalone.StartApp:214] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2017-10-01 14:44:45,178 INFO [main] [org.mycontroller.standalone.StartApp:112] MyController.org server started in [14529] ms
[Sun Oct 01 14:44:45 BST 2017] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
2017-10-01 14:46:44,600 INFO [Acme.Utils.ThreadPool(4)-PooledThread: Acme.Serve.Serve$ServeConnection@39240b] [org.mycontroller.standalone.api.BackupApi:219] Restore triggered.
2017-10-01 14:46:47,602 INFO [Thread-16] [org.mycontroller.standalone.backup.Restore:69] About to restore a backup, BackupFile(name=on-demand_mc_backup_h2db_embedded-2017_10_01-14_14_53.zip, canonicalPath=/home/myvbackup/on-demand_mc_backup_h2db_embedded-2017_10_01-14_14_53.zip, timestamp=1506863694000, size=316013)
[Sun Oct 01 14:46:47 BST 2017] Accept: java.net.SocketException: Socket closed
2017-10-01 14:46:47,794 INFO [Thread-16] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:70] MQTT Broker has been stopped successfully
2017-10-01 14:46:52,994 INFO [Thread-16] [org.mycontroller.standalone.db.DataBaseUtils:288] Database restore completed. Database url:jdbc:h2:file:../conf/mycontroller;MVCC=TRUE, Restored file name:/home/mycontroller/bin/tmp/on-demand_mc_backup_h2db_embedded-2017_10_01-14_14_53/database_backup.zip
2017-10-01 14:46:53,010 INFO [Thread-16] [org.mycontroller.standalone.backup.Restore:153] Restore completed successfully. Start 'MyController.org' server manually
2017-10-01 14:46:53,015 WARN [MyController.org Shutdown-Hook] [org.knowm.sundial.SundialJobScheduler:140] Scheduler has not yet been created!!! Call "createScheduler" first.
2017-10-01 14:46:53,016 INFO [MyController.org Shutdown-Hook] [org.mycontroller.standalone.AppShutdownHook:36] Bye, Have a nice day! See you soon
2017-10-01 14:48:57,300 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts]
2017-10-01 14:48:57,334 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/conditions]
2017-10-01 14:48:57,336 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/operations]
2017-10-01 14:48:57,883 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2017-10-01 14:49:02,677 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.0.0.Final, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.03.06 - 2017 Mar 03), Built on:2017-09-25T11:00:11+0530, Git commit:07c3a228b9c861280fe2f560ed4d1097349d08bb:master]
2017-10-01 14:49:04,067 INFO [Thread-6] [org.mycontroller.standalone.message.RawMessageQueue:54] Cleared offline messages[0] from the queue.
2017-10-01 14:49:04,993 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:52] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, bindAddress=0.0.0.0, httpPort=1883, websocketPort=7080, allowAnonymous=true)
2017-10-01 14:49:05,754 INFO [main] [org.mycontroller.standalone.gateway.mqtt.MqttGatewayImpl:67] MQTT Gateway[name:Raspberry PI, URI:tcp://localhost:1883, NetworkType:MyController] connected successfully..
2017-10-01 14:49:09,893 INFO [main] [org.mycontroller.standalone.StartApp:214] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2017-10-01 14:49:09,894 INFO [main] [org.mycontroller.standalone.StartApp:112] MyController.org server started in [12683] ms
[Sun Oct 01 14:51:31 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Mon Oct 02 07:53:03 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Tue Oct 03 07:18:29 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 09:20:10 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 14:50:38 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 21:17:40 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
2017-10-04 21:22:37,318 ERROR [Thread-8] [org.mycontroller.standalone.gateway.serialport.SerialDataListenerjSerialComm:94] Exception, 
java.lang.NegativeArraySizeException: null
	at org.mycontroller.standalone.gateway.serialport.SerialDataListenerjSerialComm.serialEvent(SerialDataListenerjSerialComm.java:59)
	at com.fazecast.jSerialComm.SerialPort$SerialPortEventListener.waitForSerialEvent(SerialPort.java:937)
	at com.fazecast.jSerialComm.SerialPort$SerialPortEventListener$1.run(SerialPort.java:885)
	at java.lang.Thread.run(Thread.java:745)
2017-10-04 21:23:11,304 INFO [Thread-9] [org.mycontroller.standalone.gateway.serialport.SerialPortMonitoringThread:112] Serial GatewayTable[GatewaySerial(super=Gateway(id=2, enabled=true, name=MYSGW, type=SERIAL, networkType=MY_SENSORS, timestamp=1505319425589, state=DOWN, statusMessage=ERROR: null, statusSince=1507148557303, txDelay=0), driver=AUTO, portName=/dev/ttyMySensorsGateway, baudRate=115200, retryFrequency=60, runningDriver=JSERIALCOMM)] not connected, Reconnect initiated...
2017-10-04 21:23:11,832 ERROR [Thread-9] [org.mycontroller.standalone.gateway.serialport.SerialPortjSerialCommImpl:74] Unable to open serial port:[/dev/ttyMySensorsGateway]
2017-10-04 21:23:11,842 INFO [Thread-9] [org.mycontroller.standalone.gateway.serialport.SerialPortMonitoringThread:93] Serial GatewayTable[GatewaySerial(super=Gateway(id=2, enabled=true, name=MYSGW, type=SERIAL, networkType=MY_SENSORS, timestamp=1505319425589, state=DOWN, statusMessage=ERROR: Unable to open!, statusSince=1507148557303, txDelay=0), driver=AUTO, portName=/dev/ttyMySensorsGateway, baudRate=115200, retryFrequency=60, runningDriver=JSERIALCOMM)], Unable to reconnected! Will do next try after 60 second(s)
[Wed Oct 04 21:24:08 BST 2017] Accept: java.net.SocketException: Socket closed
2017-10-04 21:24:09,469 INFO [MyController.org Shutdown-Hook] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:70] MQTT Broker has been stopped successfully
2017-10-04 21:24:09,486 INFO [MyController.org Shutdown-Hook] [org.mycontroller.standalone.AppShutdownHook:36] Bye, Have a nice day! See you soon
2017-10-04 21:24:29,288 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2017-10-04 21:24:34,266 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.0.0.Final, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.03.06 - 2017 Mar 03), Built on:2017-09-25T11:00:11+0530, Git commit:07c3a228b9c861280fe2f560ed4d1097349d08bb:master]
2017-10-04 21:24:35,659 INFO [Thread-6] [org.mycontroller.standalone.message.RawMessageQueue:54] Cleared offline messages[0] from the queue.
2017-10-04 21:24:36,731 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:52] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, bindAddress=0.0.0.0, httpPort=1883, websocketPort=7080, allowAnonymous=true)
2017-10-04 21:24:37,491 INFO [main] [org.mycontroller.standalone.gateway.mqtt.MqttGatewayImpl:67] MQTT Gateway[name:Raspberry PI, URI:tcp://localhost:1883, NetworkType:MyController] connected successfully..
2017-10-04 21:24:42,259 INFO [main] [org.mycontroller.standalone.StartApp:214] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2017-10-04 21:24:42,260 INFO [main] [org.mycontroller.standalone.StartApp:112] MyController.org server started in [13531] ms
[Wed Oct 04 21:24:48 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(SynchronousDispatcher.java:167)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
	at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
	at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
	... 12 more
Caused by: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1906)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1870)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1815)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:128)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.write(Serve.java:4854)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.write(HttpServletResponseWrapper.java:46)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.write(CommitHeaderOutputStream.java:71)
	at org.jboss.resteasy.util.DelegatingOutputStream.write(DelegatingOutputStream.java:48)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2003)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.flush(UTF8JsonGenerator.java:1019)
	at com.fasterxml.jackson.databind.ObjectWriter.writeValue(ObjectWriter.java:891)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:207)
	... 20 more
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
	at sun.security.ssl.OutputRecord.writeBuffer(OutputRecord.java:431)
	at sun.security.ssl.OutputRecord.write(OutputRecord.java:417)
	at sun.security.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:876)
	at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:847)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123)
	... 29 more

[Wed Oct 04 21:24:48 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(SynchronousDispatcher.java:167)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
	at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
	at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
	... 12 more
Caused by: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1906)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1870)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1815)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:128)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.write(Serve.java:4854)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.write(HttpServletResponseWrapper.java:46)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.write(CommitHeaderOutputStream.java:71)
	at org.jboss.resteasy.util.DelegatingOutputStream.write(DelegatingOutputStream.java:48)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2003)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.flush(UTF8JsonGenerator.java:1019)
	at com.fasterxml.jackson.databind.ObjectWriter.writeValue(ObjectWriter.java:891)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:207)
	... 20 more
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
	at sun.security.ssl.OutputRecord.writeBuffer(OutputRecord.java:431)
	at sun.security.ssl.OutputRecord.write(OutputRecord.java:417)
	at sun.security.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:876)
	at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:847)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123)
	... 29 more

[Wed Oct 04 21:24:48 BST 2017] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
[Wed Oct 04 21:24:48 BST 2017] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
[Wed Oct 04 21:24:48 BST 2017] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 21:24:48 BST 2017] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl

      Hope this helps to improve stability..... 😉

      jkandasaJ 1 Reply Last reply Reply Quote 1
      • jkandasaJ Offline
        jkandasa @skywatch
        last edited by

        @skywatch Your gateway works after this issue? Are you receiving data from sensors?

        1 Reply Last reply Reply Quote 0
        • skywatchS Offline
          skywatch
          last edited by

          After this error all data from nodes stops being displayed on the graphs etc, so guess it affects the GW somehow. I believe that all data from mcagent was still working.

          A reboot didn't cure it for more than a few minutes (all nodes seem to work but then after 1 or 2 data packets stop functioning again). - I will try a reinstall from scratch again tonight or tomorrow.

          Thanks.

          jkandasaJ 1 Reply Last reply Reply Quote 0
          • jkandasaJ Offline
            jkandasa @skywatch
            last edited by

            @skywatch I guess you are using NRF24L01 directly with PI?

            @Tag Are you using NRF24L01 directly with PI? Do you see any issue?

            T 1 Reply Last reply Reply Quote 0
            • skywatchS Offline
              skywatch
              last edited by

              I ran tail -f /var/log/syslog and no data is getting through the gateway, hope this helps.

              Yes NRF attached directly to the pi as shown in the mysensors build page.

              1 Reply Last reply Reply Quote 0
              • skywatchS Offline
                skywatch
                last edited by

                What really puzzles me is how it worked for over a week without issue and then suddenly this.

                Any idea what triggers this to happen?

                1 Reply Last reply Reply Quote 0
                • C Offline
                  cimba007
                  last edited by

                  I use mycontroller with HTTP and not HTTP and with esp8266 mqtt-gateway .. no problem so far with Final 1.0.0

                  1 Reply Last reply Reply Quote 0
                  • T Offline
                    Tag MOD @jkandasa
                    last edited by Tag

                    @jkandasa

                    Using the OrangePI Zero, nrf24l01 is directly attached to GPIO for a couple of months now. I have not seen any of these issues.

                    @skywatch, are you using the latest version of mysgw?
                    if so, what is the output of

                    mysgw -d

                    if the above command does not provide any output that shows it connected the radio successfully, check the wiring, another thing i can imagine is that your radio is dead...

                    1 Reply Last reply Reply Quote 1
                    • T Offline
                      Tag MOD
                      last edited by

                      I realized that i was still using the previous release.... just upgraded to Final-1.0.0.. will keep you posted

                      1 Reply Last reply Reply Quote 0
                      • skywatchS Offline
                        skywatch
                        last edited by skywatch

                        @jkandasa

                        pi@HAMASS:~ $ mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
mysgw: Couldn't create a symlink '/dev/ttyMySensorsGateway' to PTY! (17) File exists
mysgw: Failed to open serial port.

                        Yet it worked for more than a week until the crash....Replaced radio today, still the same....

                        T 1 Reply Last reply Reply Quote 0
                        • T Offline
                          Tag MOD @skywatch
                          last edited by Tag

                          @skywatch

                          Strange can you post the output of

                          ls -la /dev/ttyMySensorsGateway

                          It should show something like this:

                          
root@orangepizero:~# ls -la /dev/ttyMySensorsGateway
lrwxrwxrwx 1 root root 10 Oct  7 13:11 /dev/ttyMySensorsGateway -> /dev/pts/0

                          if not just stop mysgw, and delete the file. mysgw will create a new once mysgw starts.

                          1 Reply Last reply Reply Quote 0
                          • skywatchS Offline
                            skywatch
                            last edited by skywatch

                            @Tag

                            here it is....

                             ls -la /dev/ttyMySensorsGateway
lrwxrwxrwx 1 root root 10 Oct  9 21:19 /dev/ttyMySensorsGateway -> /dev/pts/1

                            I changed the radio module this evening and rebooted, no change at all.....Puzzled am I.....

                            jkandasaJ T 3 Replies Last reply Reply Quote 0
                            • jkandasaJ Offline
                              jkandasa @skywatch
                              last edited by

                              @skywatch I believe you might have done these steps already. If not, kindly check it.

                              Have you attached capacitor for your NRF24L01+ radio? It works on 3.3 Volts. Kindly check all the details once again from https://www.mysensors.org/build/raspberry Seems the original repo deprecated https://github.com/mysensors/Raspberry

                              1 Reply Last reply Reply Quote 0
                              • T Offline
                                Tag MOD @skywatch
                                last edited by

                                @skywatch

                                Weird, if you kill mysgw, is the device file removed?
                                (will dig into this a little later today)

                                1 Reply Last reply Reply Quote 0
                                • skywatchS Offline
                                  skywatch
                                  last edited by

                                  So yes capacitor on nrf and 3.28v seen across it, so no problem there. The radio has a single 2x4 connector so all leads stay in position (much quicker) 🙂

                                  Anyway, today brings a new mystery for me as I did the following.....

                                  sudo systemctl daemon-reload
                                  sudo systemctl restart mysgw.service
                                  sudo systemctl stop mysgw.service
                                  sudo systemctl start mysgw.service

                                  Then to see what was going on....
                                  tail -f /var/log/syslog

                                  This showed data, so I connected to the web server on the pi and graphs were showing of data received since last night.... It looks like it's all back to normal, except it isn't as I still get exactly the same error message from mysgw -d.

                                  Weirder still!

                                  T 1 Reply Last reply Reply Quote 0
                                  • T Offline
                                    Tag MOD @skywatch
                                    last edited by Tag

                                    @skywatch

                                    I have tried your commands:

                                    sudo systemctl restart mysgw.service
sudo systemctl stop mysgw.service
sudo systemctl start mysgw.service

                                    This is my output:

                                    root@orangepizero:/var/log# tail -f syslog
Oct 10 22:25:09 localhost systemd[1]: Started MySensors Gateway daemon.
Oct 10 22:25:09 localhost mysgw: Starting gateway...
Oct 10 22:25:09 localhost mysgw: Protocol version - 2.2.0-beta
Oct 10 22:25:39 localhost systemd[1]: Stopping MySensors Gateway daemon...
Oct 10 22:25:39 localhost mysgw: Received SIGTERM
Oct 10 22:25:39 localhost systemd[1]: Stopped MySensors Gateway daemon.
Oct 10 22:25:56 localhost systemd[1]: Starting MySensors Gateway daemon...
Oct 10 22:25:56 localhost systemd[1]: Started MySensors Gateway daemon.
Oct 10 22:25:56 localhost mysgw: Starting gateway...
Oct 10 22:25:56 localhost mysgw: Protocol version - 2.2.0-beta

                                    Does this match your output?

                                    looking at the /dev/ device directory, the device file /dev/ttyMySensorsGateway is gone once stopped. and recreated when the mysgw daemon started again...

                                    (i also had to re-enable the GW in mycontroller...since it got disabled...)

                                    1 Reply Last reply Reply Quote 0
                                    • T Offline
                                      Tag MOD @skywatch
                                      last edited by

                                      @skywatch

                                      the link seems okay. now i am wondering what is behind the link...

                                      root@orangepizero:~/MySensors/bin# ls -l  /dev/ttyMySensorsGateway 
lrwxrwxrwx 1 root root 10 Oct 12 18:45 /dev/ttyMySensorsGateway -> /dev/pts/2
root@orangepizero:~/MySensors/bin# ll /dev/pts/2
crw--w---- 1 root tty 136, 2 Oct 12 18:46 /dev/pts/2

                                      if you do an

                                      ls -l /dev/pts/1

                                      what does that look like?

                                      did you use the correct flags to build mysgw? (as described here)

                                      1 Reply Last reply Reply Quote 0
                                      • skywatchS Offline
                                        skywatch
                                        last edited by

                                        @Tag
                                        thanks for the support but the mystery is solved (at least this bit) - I rebooted the pi before giving the mysgw -d and of course mysgw was already started at boot and so was trying to start a second session and that is why the strange messages happened.

                                        I have the system working again now and hope that it will stay that way for many weeks! ......

                                        T 1 Reply Last reply Reply Quote 1
                                        • T Offline
                                          Tag MOD @skywatch
                                          last edited by

                                          @skywatch said in Final 1.0.0 errors and crash report....:

                                          but the mystery is solved (at least this

                                          ah okay!! good!,
                                          It will stay running 😉

                                          good luck!

                                          1 Reply Last reply Reply Quote 0
                                          • skywatchS Offline
                                            skywatch
                                            last edited by

                                            It didn't stay running - It crashed again.

                                            Nothing in the myc log.
                                            The MYSGW log shows data still being received from the sensor nodes.

                                            Now I am stumped.....really stumped, as to how to get this sorted out......

                                            T 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            0

                                            Online

                                            586

                                            Users

                                            529

                                            Topics

                                            3.4k

                                            Posts
                                            Copyright © 2015-2025 MyController.org | Contributors | Localization