Project

General

Profile

Tigase filling up my log files with strange output

Ganesh Krishnan
Added about 4 years ago

It's a clustered server with only one instance in the cluster. (servername: intouchy)

The server accepts connections and works normally but there are abnormal spikes in cpu (goes from 0 - 20% usage randomly). Should I be worried about these logs?

2015-03-03 03:15:16.248 [pool-11-thread-5]  StreamManagementIOProcessor.serviceStopped()  FINEST: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58630, type: accept, Socket: TLS: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58630 Socket[unconnected], jid: null, service stopped - StreamManagement disabled
2015-03-03 03:15:16.248 [pool-11-thread-5]  ConnectionManager.serviceStopped()  FINER:  [[c2s]] Connection stopped: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58630, type: accept, Socket: TLS: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58630 Socket[unconnected], jid: null
2015-03-03 03:15:16.249 [pool-11-thread-5]  ClientConnectionManager.xmppStreamClosed()  FINER: Stream closed: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58630
2015-03-03 03:15:16.249 [ConnectionOpenThread]  ConnectionManager$ConnectionListenerImpl.accept()  FINEST: Accept called for service: null@null, port_props: {type=accept, socket=ssl, ifc=[Ljava.lang.String;@4f5b08d, remote-host=localhost, required=false, port-no=5223}
2015-03-03 03:15:16.250 [ConnectionOpenThread]  ConnectionManager.serviceStarted()  FINER: [[c2s]] Connection started: null, type: accept, Socket: TLS: nullSocket[addr=/168.63.129.16,port=58691,localport=5223], jid: null
2015-03-03 03:15:29.014 [pool-11-thread-6]  StreamManagementIOProcessor.serviceStopped()  FINEST: c2s@intouchy/10.0.0.4_5222_168.63.129.16_58680, type: accept, Socket: c2s@intouchy/10.0.0.4_5222_168.63.129.16_58680 Socket[unconnected], jid: null, service stopped - StreamManagement disabled
2015-03-03 03:15:29.014 [pool-11-thread-6]  ConnectionManager.serviceStopped()  FINER:  [[c2s]] Connection stopped: c2s@intouchy/10.0.0.4_5222_168.63.129.16_58680, type: accept, Socket: c2s@intouchy/10.0.0.4_5222_168.63.129.16_58680 Socket[unconnected], jid: null
2015-03-03 03:15:29.014 [ConnectionOpenThread]  ConnectionManager$ConnectionListenerImpl.accept()  FINEST: Accept called for service: null@null, port_props: {type=accept, socket=plain, ifc=[Ljava.lang.String;@4f5b08d, remote-host=localhost, required=false, port-no=5222}
2015-03-03 03:15:29.015 [ConnectionOpenThread]  ConnectionManager.serviceStarted()  FINER: [[c2s]] Connection started: null, type: accept, Socket: nullSocket[addr=/168.63.129.16,port=58712,localport=5222], jid: null
2015-03-03 03:15:29.017 [pool-11-thread-6]  ClientConnectionManager.xmppStreamClosed()  FINER: Stream closed: c2s@intouchy/10.0.0.4_5222_168.63.129.16_58680
2015-03-03 03:15:31.248 [pool-11-thread-7]  StreamManagementIOProcessor.serviceStopped()  FINEST: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58691, type: accept, Socket: TLS: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58691 Socket[unconnected], jid: null, service stopped - StreamManagement disabled
2015-03-03 03:15:31.248 [ConnectionOpenThread]  ConnectionManager$ConnectionListenerImpl.accept()  FINEST: Accept called for service: null@null, port_props: {type=accept, socket=ssl, ifc=[Ljava.lang.String;@4f5b08d, remote-host=localhost, required=false, port-no=5223}
2015-03-03 03:15:31.248 [pool-11-thread-7]  ConnectionManager.serviceStopped()  FINER:  [[c2s]] Connection stopped: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58691, type: accept, Socket: TLS: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58691 Socket[unconnected], jid: null
2015-03-03 03:15:31.249 [pool-11-thread-7]  ClientConnectionManager.xmppStreamClosed()  FINER: Stream closed: c2s@intouchy/10.0.0.4_5223_168.63.129.16_58691
2015-03-03 03:15:31.251 [ConnectionOpenThread]  ConnectionManager.serviceStarted()  FINER: [[c2s]] Connection started: null, type: accept, Socket: TLS: nullSocket[addr=/168.63.129.16,port=58725,localport=5223], jid: null

Replies (4)

Added by Wojciech Kapcia TigaseTeam about 4 years ago

It looks like that for some reason some client connects/disconnects constantly. It's hard to tell as "why" it's happening from such short log output.

Added by Ganesh Krishnan about 4 years ago

There are no clients connected; it's a brand new server.

I changed the hostname to FQDN and I got similar errors. Could this be certificate issue? The only difference between my other good server and this one is the certificate

2015-03-03 11:19:46.813 [pool-11-thread-6]  StreamManagementIOProcessor.serviceStopped()  FINEST: c2s@im.getintouch.co/10.0.0.4_5223_168.63.129.16_65527, type: accept, Socket: TLS: c2s@im.getintouch.co/10.0.0.4_5223_168.63.129.16_65527 Socket[unconnected], jid: null, service stopped - StreamManagement disabled
2015-03-03 11:19:46.814 [pool-11-thread-6]  ConnectionManager.serviceStopped()  FINER:  [[c2s]] Connection stopped: c2s@im.getintouch.co/10.0.0.4_5223_168.63.129.16_65527, type: accept, Socket: TLS: c2s@im.getintouch.co/10.0.0.4_5223_168.63.129.16_65527 Socket[unconnected], jid: null
2015-03-03 11:19:46.814 [pool-11-thread-6]  ClientConnectionManager.xmppStreamClosed()  FINER: Stream closed: c2s@im.getintouch.co/10.0.0.4_5223_168.63.129.16_65527
2015-03-03 11:19:46.814 [ConnectionOpenThread]  ConnectionManager$ConnectionListenerImpl.accept()  FINEST: Accept called for service: null@null, port_props: {type=accept, socket=ssl, ifc=[Ljava.lang.String;@4375b013, remote-host=localhost, required=false, port-no=5223}
2015-03-03 11:19:46.814 [ConnectionOpenThread]  ConnectionManager.serviceStarted()  FINER: [[c2s]] Connection started: null, type: accept, Socket: TLS: nullSocket[addr=/168.63.129.16,port=49181,localport=5223], jid: null

Added by Wojciech Kapcia TigaseTeam about 4 years ago

Ganesh Krishnan wrote:

There are no clients connected; it's a brand new server.

Well, from the logs it looks like something is definitely trying to connect. If it helps, connection is being opened from 168.63.129.16.

I changed the hostname to FQDN and I got similar errors. Could this be certificate issue? The only difference between my other good server and this one is the certificate

This is rather not cause by certificate.

Added by Ganesh Krishnan about 4 years ago

The IP address helped me nail it. It's the Microsoft Azure Load balancer which pings to check if the service is alive.

Thank you so much. You guys are awesome!

    (1-4/4)