@marceloaqno :
At first, THANKS for your help. CPU usage does not rise anymore.
But unfortunately no more node READs after the same situation:
Mar 4 07:00:09 raspiez mysgw: TSF:MSG:READ,14-14-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
Mar 4 07:00:09 raspiez mysgw: TSF:MSG:READ,12-12-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
Mar 4 07:00:09 raspiez mysgw: GWT:RFC:C=1,MSG=14;255;3;0;6;M
Mar 4 07:00:09 raspiez mysgw: !TSF:MSG:SEND,0-0-14-14,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=NACK:M
Mar 4 07:00:09 raspiez mysgw: TSF:MSG:READ,11-11-0,s=255,c=0,t=18,pt=0,l=3,sg=0:1.5
Mar 4 07:00:09 raspiez mysgw: GWT:RFC:C=1,MSG=12;255;3;0;6;M
Mar 4 07:00:09 raspiez mysgw: TSF:MSG:SEND,0-0-12-12,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=OK:M
Mar 4 07:00:13 raspiez mysgw: TSM:READY:NWD REQ
Mar 4 07:00:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar 4 07:00:13 raspiez mysgw: TSF:SRT:OK
Mar 4 07:00:13 raspiez mysgw: TSF:SAN:OK
Mar 4 07:00:37 raspiez mysgw: Ethernet client disconnected.
Mar 4 07:00:37 raspiez mysgw: New connection from 192.168.1.11
Mar 4 07:00:37 raspiez mysgw: GWT:TSA:C=0,CONNECTED
Mar 4 07:00:37 raspiez mysgw: GWT:TSA:C=1,DISCONNECTED
After this point (again after a reconnect from the controller) no more messages from any node PLUS the cpu usage stayed normal (what makes it even worse at this moment, as I would have to create a script which monitors the logfile and restarts the mysgw service in this situation). As soon as the service is restarted, everything is working fine again.
What happens after this point in the log:
Mar 4 07:00:37 raspiez mysgw: GWT:RFC:C=0,MSG=0;0;3;0;2;
Mar 4 07:15:13 raspiez mysgw: TSF:SAN:OK
Mar 4 07:20:13 raspiez mysgw: TSM:READY:NWD REQ
Mar 4 07:20:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar 4 07:30:13 raspiez mysgw: TSF:SRT:OK
Mar 4 07:30:13 raspiez mysgw: TSF:SAN:OK
Mar 4 07:30:37 raspiez mysgw: GWT:TSA:C=0,DISCONNECTED
Mar 4 07:30:37 raspiez mysgw: Ethernet client disconnected.
Mar 4 07:30:37 raspiez mysgw: New connection from 192.168.1.11
Mar 4 07:30:37 raspiez mysgw: GWT:TSA:C=0,CONNECTED
Mar 4 07:30:37 raspiez mysgw: GWT:RFC:C=0,MSG=0;0;3;0;2;
Mar 4 07:40:13 raspiez mysgw: TSM:READY:NWD REQ
Mar 4 07:40:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar 4 07:45:13 raspiez mysgw: TSF:SAN:OK
Mar 4 08:00:13 raspiez mysgw: TSM:READY:NWD REQ
Mar 4 08:00:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar 4 08:00:13 raspiez mysgw: TSF:SRT:OK
Mar 4 08:00:13 raspiez mysgw: TSF:SAN:OK
Mar 4 08:00:37 raspiez mysgw: GWT:TSA:C=0,DISCONNECTED
Mar 4 08:00:37 raspiez mysgw: Ethernet client disconnected.
Mar 4 08:00:37 raspiez mysgw: New connection from 192.168.1.11
Mar 4 08:00:37 raspiez mysgw: GWT:TSA:C=0,CONNECTED
and so on....
It seems that the increasing cpu usage is only a symptom for the real problem.
As I am using this in production I will dis-apply the patch and use the daemon as before (beacuse using the python script for cpu-usage-monitoring makes the situation somehow controllable for me).
Maybe you could have an additional eye on this please? Could I help you with further information? Maybe I could add some additional logging somewhere in the code?
Thanks again and cheers,
Otto