what does these ejabberd info log messages mean? - xmpp

can anyone tell me what does these log messages mean? is any session been terminated ,why?
2016-01-20 15:48:24.651 [info] <0.477.0>#ejabberd_listener:accept:333 (#Port<0.16235>) Accepted connection 192.16.35.6:1432 -> 28.4.5.2
2016-01-20 15:48:27.497 [info] <0.1411.0>#ejabberd_c2s:wait_for_feature_request:740 ({socket_state,p1_tls,{tlssock,#Port<0.16235>,#Port<0.16236>},<0.1410.0>}) Accepted authentication for 14512843168518 by ejabberd_auth_odbc from 103.233.119.62
2016-01-20 15:48:27.903 [info] <0.1411.0>#ejabberd_c2s:wait_for_session:1106 ({socket_state,p1_tls,{tlssock,#Port<0.16235>,#Port<0.16236>},<0.1410.0>}) Opened session for 14512843168518#cndivneofveofv/androidjc1PGFLG
2016-01-20 15:48:27.906 [info] <0.1355.0>#ejabberd_c2s:terminate:1768 ({socket_state,p1_tls,{tlssock,#Port<0.16227>,#Port<0.16228>},<0.1354.0>}) Replaced session for 14512843168518#cedefjwojffj/androidjc1PGFLG

Yes, the user 14512843168518#devchat.drooly.co had an open session with resource androidjc1PGFLG, and this session was terminated and replaced by a new session with the same resource.
This is a feature of XMPP: if a user's client has lost its connection to the XMPP server, but the server hasn't detected it yet, the client can force the server to terminate the previous connection by connecting again and specifying the same resource.

Related

Fusion Freeswitch Maximum Calls In Progress

I use Fusion core Freeswitch to build my PBX Server.
My version:
FreeSWITCH version: 1.10.2-release-14-f7bdd3845a~64bit (-release-14-f7bdd3845a 64bit)
it working find till last month BUT when user registrations reach to 1000
i have check Freeswitch log ( debug level) freeswitch still working
I have check postgreSql log still working
But client disconnected ( webrct from Web using SipJS and Zoiper use TCP protocol) and can not connect to Freeswitch for Registrations , so it can make any call at this time.
At this time when i see log it show "Maximum Calls In Progress"
I have try increase session reach to 5000 and session per second to 1000 and flush cached/ restart freeswitch but still not woking.
Here my switch.conf.xml
Here my postgresql.conf
Here my log when server down: fs_log
You can see i restart freeswitch at this log:
2020-07-29 14:39:08.291394 [INFO] switch_core.c:2879 Shutting down ca289c03-0617-46bf-a7af-eda4a4fe2fbb 2020-07-29 14:39:08.291394 [NOTICE] switch_core_session.c:407 Hangup sofia/internal/1100365#125.212.xxx.xxx [CS_NEW] [SYSTEM_SHUTDOWN]
Please take a look at help me solve this.

SQL Server 2012 service not starting automatically

I have multiple SQL Server instance and I want to start service automatically for each when system starts. So I choose services state to automatically but it does not start automatically.
Here is the error log of one of the SQL Server instances
2018-07-12 17:55:30.96 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-07-12 17:55:30.96 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-07-12 17:55:30.97 Server Detected 16155 MB of RAM. This is an informational message; no user action is required.
2018-07-12 17:55:30.97 Server Using conventional memory in the memory manager.
2018-07-12 17:55:47.27 Server This instance of SQL Server last reported using a process ID of 4400 at 12/07/2018 5:26:22 PM (local) 12/07/2018 9:26:22 AM (UTC). This is an informational message only; no user action is required.
2018-07-12 17:55:47.54 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-07-12 17:55:47.56 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2018-07-12 17:55:47.59 Server Software Usage Metrics is disabled.
2018-07-12 17:55:48.57 spid1s Starting up database 'master'.
2018-07-12 17:55:49.53 Server CLR version v4.0.30319 loaded.
2018-07-12 17:55:53.62 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2018-07-12 17:56:09.76 spid1s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-07-12 17:56:09.81 spid1s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-07-12 17:56:13.96 spid1s SQL Trace ID 1 was started by login "sa".
2018-07-12 17:56:14.92 spid1s Server name is 'NB-1608-001\SQLEXPRESS1'. This is an informational message only. No user action is required.
2018-07-12 17:56:16.22 spid12s A self-generated certificate was successfully loaded for encryption.
2018-07-12 17:56:16.28 spid12s Server is listening on [ 'any' <ipv6> 51270].
2018-07-12 17:56:16.28 spid12s Server is listening on [ 'any' <ipv4> 51270].
2018-07-12 17:56:16.33 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS1 ].
2018-07-12 17:56:16.33 spid12s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS1\sql\query ].
2018-07-12 17:56:16.33 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2018-07-12 17:56:16.36 spid12s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2018-07-12 17:56:16.36 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2018-07-12 17:56:16.36 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/NB-1608-001:SQLEXPRESS1 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2018-07-12 17:56:16.36 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/NB-1608-001:51270 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2018-07-12 17:56:18.34 Logon Error: 18456, Severity: 14, State: 38.
2018-07-12 17:56:18.34 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ReportServer$SQLEXPRESS1'. [CLIENT: 192.168.0.100]
2018-07-12 17:56:25.44 Logon Error: 18456, Severity: 14, State: 38.
2018-07-12 17:56:25.44 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ReportServer$SQLEXPRESS1'. [CLIENT: 192.168.0.100]
2018-07-12 17:56:31.17 spid13s Error: 9954, Severity: 16, State: 1.
2018-07-12 17:56:31.17 spid13s SQL Server failed to communicate with filter daemon launch service (Windows error: Windows Error: hr = 0x8007006d(failed to retrieve text for this error)). Full-Text filter daemon process failed to start. Full-text search functionality will not be available.
2018-07-12 17:56:31.57 spid1s Starting up database 'msdb'.
First I changed to Service state to Start Delay but it does not work.
Second I changed to Log on properties and set to computer logon user's account but it does not work.
I am not sure why this error occurs and I cant find any useful resource.

ejabberd: XML stanza not acknowledged

While resuming a stream managed session of ejabberd, I get the below logs:
2016-04-11 08:53:07.430 [info] <0.5432.11>#ejabberd_c2s:terminate:1752 Closing former stream of resumed session for 54ff31587261691606060000#108.59.83.204/sender
2016-04-11 08:53:07.430 [info] <0.7868.11>#ejabberd_c2s:handle_unacked_stanzas:2814 1 stanzas were not acknowledged by 54ff31587261691606060000#108.59.83.204/sender
2016-04-11 08:53:07.430 [info] <0.7868.11>#ejabberd_c2s:handle_resume:2731 Resumed session for 54ff31587261691606060000#108.59.83.204/sender
2016-04-11 08:53:08.602 [info] <0.8227.11>#ejabberd_c2s:handle_enable:2644 Stream management with resumption enabled for 5695b87d7261697179130000#108.59.83.204/sender
2016-04-11 08:53:09.516 [info] <0.8227.11>#ejabberd_c2s:terminate:1779 ({socket_state,gen_tcp,#Port<0.138899>,<0.8244.11>}) Close session for 5695b87d7261697179130000#108.59.83.204/sender
2016-04-11 08:53:09.517 [info] <0.8227.11>#ejabberd_c2s:handle_unacked_stanzas:2814 1 stanzas were not acknowledged by 5695b87d7261697179130000#108.59.83.204/sender
2016-04-11 08:53:09.987 [info] <0.458.0>#ejabberd_listener:accept:333 (#Port<0.138210>) Accepted connection 106.196.172.221:58035 -> 10.240.0.3:5222
2016-04-11 08:53:11.157 [info] <0.8254.11>#ejabberd_c2s:wait_for_sasl_response:919 ({socket_state,gen_tcp,#Port<0.138210>,<0.8185.11>}) Accepted authentication for 5695b87d7261697179130000 by undefined from 106.196.172.221
Here 1 stanza was not acknowledged, what does it mean and how to correct it.
Sometimes, few delivery acknowledgements are not received by the receiver client, is this the reason that those stanzas are getting lost?
UPDATE:
Stanzas not acknowledged during a session are exchanged again when the connection resumes. But there are cases when some stanzas are getting lost, as a result delivery acknowledgements are not reflected on the sender client side.
Parameters set for stream management:
Resume on timeout: 120 seconds
Resend on timeout: true
Is there any configuration that I may be missing due to which some stanzas are getting lost?
It means that you are using stream management and that your client did not confirm he received some stanzas. If this were messages they will be stored for offline delivery or resend on another connections, so you should not lose any message.

Connection failure has been detected: HQ119014: Did not receive data from invm:0

actually I have a TimerWS running correctly, but in a few hours I have this error
WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
WARN [org.hornetq.jms.server] (Thread-3 (HornetQ-client-global-threads-451033388)) Notified of connection failure in xa discovery, we will retry on the next recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119006: Channel disconnected]
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
Any idea?
Something is going wrong with a client's connection to the server.
These warnings are generated from the server which determines that a client is no longer responding.When that happens, the server cleans up the server-side resources related to the client's connections.
I have seen this many times by clients which are not properly coded to close their resources when they exit (finally block).
Have a look also for network problems which break the connection.

RHQ Agent does not install

I configured the rhq-agent.bat. When I try to run it. It has the followings errors:
2015-06-25 14:51:24,891 ERROR [RHQ Server Polling Thread] (enterprise.communications.command.client.JBossRemotingRemoteCommunicator)- {JBossRemotingRemoteCommunicator.init-callback-failed}The initialize callback has failed. It will be tried again. Cause: org.jboss.remoting.CannotConnectException:Can not connect http client invoker after 1 attempt(s) -> java.net.ConnectException:Connection timed out: connect. Cause: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s)
2015-06-25 14:51:42,987 ERROR [main] (org.rhq.enterprise.agent.AgentMain)- {AgentMain.plugin-update-failure}Failed to update the plugins.. Cause: java.lang.IllegalStateException: The sender object is currently not sending commands now. Command not sent: [Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[getLatestPlugins], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}]]
I could solve it myself the problem was the security token. I modified those fields in the registry vierwer (Windows). When I restarted the agent it worked.