Ok, now I have found and fixed the problem that caused the looping logs. I had a mechanism the sent warning-logs as events - but since this error triggered a warning as soon as an event was sent the system went into a infinite loop...
I have removed the events generated by Warning logs. Instead I have added two action attributes in the settings page. One action that will be performed when a warning is logged in the system and one action that is performed when a severe error is logged.
This will hopefully solve the looping logs that locks up the entire system. You will probably still have the original problem, which I still suspect is caused by the router dropping the TCP-connection... Anyway you can perhaps get better error logs of the actual cause of the problem when the logs are not flooded by the loop. The change is in the nightly build.
Problems running in a RPi
Re: Problems running in a RPi
Great news, thank you!
I agree that the connection breaks maybe to the router itself (or the WiFi network drops out since the RPi is connected using a wifi dongle). Anyway my implementation (plugin for EventGhost) is automatically reconnecting if this happens and so far, it is working ok, some reconnects but nothing critical.
Kind regards, Walter
Version: 2.1-SNAPSHOT-6b4ce
SentEventCount: 16586
EventsPerMinute: 4
UpTime: 2 days 8 hours 25 minutes
MaxDistributionTime: 355.45 ms
AverageDistributionTime: 0.77 ms
MaxItemTime: 354.89 ms
MaxItemName: TCP
AlarmCount: 6
TotalLogRows: 32
Time Source Message
16.01.03 13:05:35 TCPCommandPort Connection from 192.168.10.2
16.01.03 13:05:30 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.03 09:33:09 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.03 09:33:09 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:45:15 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:38:55 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:38:55 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 16:35:04 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:34:28 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:34:28 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 16:27:39 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:27:00 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:25:04 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:24:36 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:24:36 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 15:43:18 TCPCommandPort Connection from 192.168.10.2
16.01.02 15:34:16 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 15:34:16 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 15:31:39 TCPCommandPort Connection from 192.168.10.2
16.01.02 15:30:57 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 15:30:57 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 15:25:53 TCPCommandPort Connection from 192.168.10.2
16.01.02 14:09:00 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 09:16:23 TCPCommandPort Connection from 192.168.10.2
16.01.02 09:16:18 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 06:09:03 TCPCommandPort Connection from 192.168.10.2
16.01.02 06:08:54 HomeServer Activated 9 of 9 Items
16.01.02 06:08:46 AudioProtocolPort Sample Rate:44100.0
16.01.02 06:08:44 TrayBarIcon SystemTray is not supported on this system
16.01.02 06:08:39 HomeItemFileLoader Loading Items from /etc/opt/nethome/config.xml
16.01.02 06:08:38 HomeManagerStarter Logging to: /var/log/nethome/HomeManager%g.log
16.01.02 06:08:38 HomeManagerStarter **Starting HomeManager 2.1-SNAPSHOT-6b4ce**
I agree that the connection breaks maybe to the router itself (or the WiFi network drops out since the RPi is connected using a wifi dongle). Anyway my implementation (plugin for EventGhost) is automatically reconnecting if this happens and so far, it is working ok, some reconnects but nothing critical.
Kind regards, Walter
Version: 2.1-SNAPSHOT-6b4ce
SentEventCount: 16586
EventsPerMinute: 4
UpTime: 2 days 8 hours 25 minutes
MaxDistributionTime: 355.45 ms
AverageDistributionTime: 0.77 ms
MaxItemTime: 354.89 ms
MaxItemName: TCP
AlarmCount: 6
TotalLogRows: 32
Time Source Message
16.01.03 13:05:35 TCPCommandPort Connection from 192.168.10.2
16.01.03 13:05:30 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.03 09:33:09 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.03 09:33:09 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:45:15 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:38:55 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:38:55 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 16:35:04 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:34:28 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:34:28 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 16:27:39 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:27:00 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:25:04 TCPCommandPort Connection from 192.168.10.2
16.01.02 16:24:36 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 16:24:36 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 15:43:18 TCPCommandPort Connection from 192.168.10.2
16.01.02 15:34:16 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 15:34:16 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 15:31:39 TCPCommandPort Connection from 192.168.10.2
16.01.02 15:30:57 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 15:30:57 TCPCommandPort$Session Failed reading from socket in TCPCommandPort java.net.SocketException: Connection reset
16.01.02 15:25:53 TCPCommandPort Connection from 192.168.10.2
16.01.02 14:09:00 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 09:16:23 TCPCommandPort Connection from 192.168.10.2
16.01.02 09:16:18 TCPCommandPort$Session Disconnected from 192.168.10.2
16.01.02 06:09:03 TCPCommandPort Connection from 192.168.10.2
16.01.02 06:08:54 HomeServer Activated 9 of 9 Items
16.01.02 06:08:46 AudioProtocolPort Sample Rate:44100.0
16.01.02 06:08:44 TrayBarIcon SystemTray is not supported on this system
16.01.02 06:08:39 HomeItemFileLoader Loading Items from /etc/opt/nethome/config.xml
16.01.02 06:08:38 HomeManagerStarter Logging to: /var/log/nethome/HomeManager%g.log
16.01.02 06:08:38 HomeManagerStarter **Starting HomeManager 2.1-SNAPSHOT-6b4ce**
-
mariareese
- Posts: 1
- Joined: Tue Feb 09, 2016 9:55 am
Re: Problems running in a RPi
looking for the same thing, its was helpful but some points could not done from my end 
Re: Problems running in a RPi
Hello again im back 
I was some years ago debug this problem and if i remember right tcp take after connection next port , and when port reach 65xxx something nethome crash.
Not sure if never get idea which cause this i allways use udp connection so this not never happend.
t
I was some years ago debug this problem and if i remember right tcp take after connection next port , and when port reach 65xxx something nethome crash.
Not sure if never get idea which cause this i allways use udp connection so this not never happend.
t