Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Connect » Cannot start XMPP server on Kerio Connect 8.1 (Cannot start XMPP server on Kerio Connect 8.1)
  •  
fornax

Messages: 2
Karma: 0
Send a private message to this user
Hi,

I've just upgraded my Kerio Connect from 8.0.2 to 8.1, and am encountering issues starting the Instant Messenger XMPP server. I've checked the logs and this is what I saw:

error.log
[13/May/2013 08:33:13] HealthMonitor.cpp: Problem has occured in the 'Instant Messaging' component. 5 failures has been found. Component is paused for another 10 minutes. Enable 'Instant Messaging' debug logging and inspect the log for more details.
[13/May/2013 08:33:15] HealthMonitor.cpp: Problem has occured in the 'Instant Messaging' component. 5 failures has been found. Component is paused for another 10 minutes. Enable 'Instant Messaging' debug logging and inspect the log for more details.


debug.log
[13/May/2013 08:32:23][1460] {im} Federation test message has been arranged (id: a37b6212-4f62-45d3-a8df-2566ad4b76af).
[13/May/2013 08:32:23][1460] {im} There has been generated 'a37b6212-4f62-45d3-a8df-2566ad4b76af' token for wait for response message. External process is expected to respond with this token. Go to sleep.
[13/May/2013 08:32:23][1881] {im} Failed to send message with id 'a37b6212-4f62-45d3-a8df-2566ad4b76af' through socket. (32) Unknown error 32
[13/May/2013 08:32:23][1881] {im} Problem has occured.
[13/May/2013 08:32:25][1881] {im} Failed to send message with id 'a37b6212-4f62-45d3-a8df-2566ad4b76af' through socket. (110) Unknown error 110
[13/May/2013 08:32:25][1881] {im} Problem has occured.


warning.log
[13/May/2013 08:25:14] Instant Messaging [external]: Initializing external component failed (StartServer$LazyExtServiceLoader.event): com.kerio.im.xmpp.api.XmppException: Updating certificate failed at com.kerio.im.tigase.DomainServiceImpl.update(DomainServiceIm pl.java:111) at com.kerio.im.core.cert.Certificates.<init>(Certificates.java:29) at com.kerio.im.core.CoreRuntime.setExtService(CoreRuntime.java :74) at com.kerio.im.service.task.StartServer$LazyExtServiceLoader.e vent(StartServer.java:85) at com.kerio.im.service.task.StartServer$LazyExtServiceLoader.e vent(StartServer.java:68) at com.kerio.im.core.Bus.publish(Bus.java:34) at com.kerio.im.core.remote.RemoteControl.messageReceived(Remot eControl.java:51) at com.kerio.im.tigase.ConnectComponent.processPacket(ConnectCo mponent.java:129) at tigase.server.AbstractMessageReceiver$QueueListener.run(Abst ractMessageReceiver.java:1341) Caused by: java.security.cert.CertificateParsingException: Problem adding a new certificate. at tigase.io.SSLContextContainer.addCertificates(SSLContextCon
[13/May/2013 08:25:14] Instant Messaging [external]: Performing IM service shutdown (Shutdown$ShutdownTask.run)



Any idea why is the IM service not starting?

Thanks.
  •  
Pavel Dobry (Kerio)

Messages: 5245
Karma: 251
Send a private message to this user
Your server SSL certificate seems to have incompatible file format. Please contact our technical support and provide *.crt file from the sslcrt directory.
  •  
nhoague

Messages: 853
Karma: 18
Send a private message to this user
I have a similar problem that I can't start XMPPS, however my certs are valid, and I can start the service on other servers using the same CA.

Here is a cut from the error log:


02/Jun/2013 07:52:31] StdErrChannel.cpp: Instant Messaging [external]: Starting Tigase server failed (IMService.main): com.kerio.im.common.error.ServiceException: Starting Tigase server failed at com.kerio.im.tigase.TigaseServerImpl.tigaseMain(TigaseServer Impl.java:91) at com.kerio.im.tigase.TigaseServerImpl.start(TigaseServerImpl. java:59) at com.kerio.im.tigase.TigaseServerFactory.get(TigaseServerFact ory.java:28) at com.kerio.im.service.task.StartServer.run(StartServer.java:5 1) at com.kerio.im.service.task.StartServer.run(StartServer.java:3 2) at com.kerio.im.service.IMService.run(IMService.java:82) at com.kerio.im.service.IMService.start(IMService.java:78) at com.kerio.im.service.IMService.main(IMService.java:32) Caused by: com.kerio.im.xmpp.api.XmppException: Tigase initialization failed at com.kerio.im.tigase.configuration.ConnectConfigurator.init(C onnectConfigurator.java:103) at com.kerio.im.tigase.TigaseServerImpl.tigaseMain(TigaseServer Impl.java:73) ... 7 more Caused by: com.kerio.im.xmpp.api.XmppExce
[02/Jun/2013 07:53:40] StdErrChannel.cpp: Instant Messaging [external]: Starting Tigase server failed (IMService.main): com.kerio.im.common.error.ServiceException: Starting Tigase server failed at com.kerio.im.tigase.TigaseServerImpl.tigaseMain(TigaseServer Impl.java:91) at com.kerio.im.tigase.TigaseServerImpl.start(TigaseServerImpl. java:59) at com.kerio.im.tigase.TigaseServerFactory.get(TigaseServerFact ory.java:28) at com.kerio.im.service.task.StartServer.run(StartServer.java:5 1) at com.kerio.im.service.task.StartServer.run(StartServer.java:3 2) at com.kerio.im.service.IMService.run(IMService.java:82) at com.kerio.im.service.IMService.start(IMService.java:78) at com.kerio.im.service.IMService.main(IMService.java:32) Caused by: com.kerio.im.xmpp.api.XmppException: Tigase initialization failed at com.kerio.im.tigase.configuration.ConnectConfigurator.init(C onnectConfigurator.java:103) at com.kerio.im.tigase.TigaseServerImpl.tigaseMain(TigaseServer Impl.java:73) ... 7 more Caused by: com.kerio.im.xmpp.api.XmppExce
[02/Jun/2013 07:54:53] StdErrChannel.cpp: Instant Messaging [external]: Starting Tigase server failed (IMService.main): com.kerio.im.common.error.ServiceException: Starting Tigase server failed at com.kerio.im.tigase.TigaseServerImpl.tigaseMain(TigaseServer Impl.java:91) at com.kerio.im.tigase.TigaseServerImpl.start(TigaseServerImpl. java:59) at com.kerio.im.tigase.TigaseServerFactory.get(TigaseServerFact ory.java:28) at com.kerio.im.service.task.StartServer.run(StartServer.java:5 1) at com.kerio.im.service.task.StartServer.run(StartServer.java:3 2) at com.kerio.im.service.IMService.run(IMService.java:82) at com.kerio.im.service.IMService.start(IMService.java:78) at com.kerio.im.service.IMService.main(IMService.java:32) Caused by: com.kerio.im.xmpp.api.XmppException: Tigase initialization failed at com.kerio.im.tigase.configuration.ConnectConfigurator.init(C onnectConfigurator.java:103) at com.kerio.im.tigase.TigaseServerImpl.tigaseMain(TigaseServer Impl.java:73) ... 7 more Caused by: com.kerio.im.xmpp.api.XmppExce
[02/Jun/2013 07:55:52] HealthMonitor.cpp: Problem has occured in the 'Instant Messaging' component. 5 failures has been found. Component is paused for another 10 minutes. Enable 'Instant Messaging' debug logging and inspect the log for more details.


Ideas? Thanks!
  •  
Tomas Skoda (Kerio)

Messages: 107
Karma: 20
Send a private message to this user
Nhoague,

I'm unable to say what prevents IM to start unless you send us debug.log, error.log, warning.log and also files from store/xmpp/logs.

Cheers,
Tomas Skoda
  •  
nhoague

Messages: 853
Karma: 18
Send a private message to this user
Hello,

So there is not much data in the debug or error log except for what I already sent. However, there is LOTS of data in this store/xmpp/logs file. It is attached.

Thanks!

  • Attachment: logs.zip
    (Size: 4.23KB, Downloaded 232 times)
  •  
Tomas Skoda (Kerio)

Messages: 107
Karma: 20
Send a private message to this user
There is a problem with accessing IM default database located on "store/xmpp/database/kerio-connect.private" path.

If this folder does exist and have proper rights - backup whole parent 'database' folder (don't just copy it if server is running), stop Kerio Connect server, delete the 'kerio-connect.private' folder and start Kerio Connect server again. The folder should be recreated on IM service start.

Could you send me the 'kerio-connect.private' through PM for further investigation?

Thanks,
Tomas Skoda
  •  
nhoague

Messages: 853
Karma: 18
Send a private message to this user
That worked! Thanks! PM will include the database attachment.
  •  
tomendfellner

Messages: 1
Karma: 0
Send a private message to this user
Hi Tomas,

I seem to have the very same problem. Warning log fills with error messages like these:

[28/Nov/2013 07:55:16] Instant Messaging [external]: Failed to process domain csundm.com (DomainFullSync$ExtDomainsHandler.handle): com.kerio.im.xmpp.api.XmppException: Failed to check database /opt/kerio/mailserver/store/xmpp/database/csundm.com at com.kerio.im.tigase.derby.DerbyChecker.check(DerbyChecker.ja va:74) at com.kerio.im.tigase.DomainServiceImpl.activate(DomainService Impl.java:150) at com.kerio.im.core.domain.DomainControl.add(DomainControl.jav a:69) at com.kerio.im.core.domain.DomainFullSync$ExtDomainsHandler.ha ndle(DomainFullSync.java:87) at com.kerio.im.connect.AdminApi.getAllDomains(AdminApi.java:13 0) at com.kerio.im.connect.ExtServiceImpl.getAllDomains(ExtService Impl.java:99) at com.kerio.im.core.domain.DomainFullSync.sync(DomainFullSync. java:44) at com.kerio.im.core.domain.DomainFullSync.run(DomainFullSync.j ava:35) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknow n Source) at java.util.concurrent.FutureTask.ru

There are three domains on this server:

• csundm.de
• csundm.com
• radioradsport.de

The corresponting xmpp directories (/opt/kerio/mailserver/store/xmpp/database/...) for the first and last domain are filled with the usual information:

-rw-------. 1 root root 88K 28. Nov 01:00 BACKUP.HISTORY
-rw-------. 1 root root 4 26. Nov 20:55 dbex.lck
-rw-------. 1 root root 38 26. Nov 20:55 db.lck
drwx------. 2 root root 4,0K 24. Okt 20:19 log/
drwx------. 2 root root 4,0K 27. Jun 19:37 seg0/
-rw-------. 1 root root 931 27. Jun 19:37 service.properties
drwx------. 2 root root 4,0K 26. Nov 20:55 tmp/

However, the .../database/csundm.com directory continues to stay empty except for a 2.9K BACKUP.HISTORY file.

I'll attach a zip file containing the im.log.0.txt, support_info.txt, and debug.log.txt files hoping you can find the cause of the issue.

BTW, raising the maximum open files limit in the init.d script (ulimit -n to 8192) didn't make any difference.

Thanks for any help or ideas
Thomas

  • Attachment: logs.zip
    (Size: 142.71KB, Downloaded 172 times)
  •  
Tomas Skoda (Kerio)

Messages: 107
Karma: 20
Send a private message to this user
Hi Thomas,

delete the /opt/kerio/mailserver/store/xmpp/database/csundm.com folder ... it should be created within 10 minutes again and IM for that domain should start working.

Cheers,
Tomas
  •  
hofmank

Messages: 2
Karma: 0
Send a private message to this user
Hello,

we have troubles with warnings in log, it started 27.5.2014 and still going on.
Error log
[27/May/2014 15:04:24] socklib.cpp: Bind to port 389 failed: (10048) Normálně je povoleno pouze jedno použití každé adresy (protokolu, síťové adresy, portu) soketu.
[27/May/2014 15:04:24] ProtocolServiceDerives.cpp: Cannot start service LDAP on port 389, unable to bind service to all IP addresses
[27/May/2014 15:04:24] ProtocolService.cpp: Service LDAP failed to start
[27/May/2014 15:04:24] socklib.cpp: Bind to port 636 failed: (10048) Normálně je povoleno pouze jedno použití každé adresy (protokolu, síťové adresy, portu) soketu.
[27/May/2014 15:04:24] ProtocolServiceDerives.cpp: Cannot start service LDAPS on port 636, unable to bind service to all IP addresses
[27/May/2014 15:04:24] ProtocolService.cpp: Service LDAPS failed to start
[27/May/2014 15:07:37] HealthMonitor.cpp: Problem has occured in the 'Instant Messaging' component. 5 failures has been found. Component is paused for another 10 minutes. Enable 'Instant Messaging' debug logging and inspect the log for more details.
[27/May/2014 15:09:54] HealthMonitor.cpp: Problem has occured in the 'Instant Messaging' component. 5 failures has been found. Component is paused for another 10 minutes. Enable 'Instant Messaging' debug logging and inspect the log for more details.

im.log
[05/06/2014 15:25:13] WARNING Performing IM service shutdown (com.kerio.im.core.Shutdown$ShutdownTask.run)
[05/06/2014 15:25:17] WARNING ShutdownThread started... (tigase.server.monitor.MonitorRuntime$MainShutdownThread.run )
[05/06/2014 15:25:33] WARNING No implementation found for plugin id: connect-conversation-listener (tigase.server.xmppsession.SessionManager.addPlugin)
[05/06/2014 15:25:45] WARNING Initializing external component failed (com.kerio.im.service.task.StartServer$LazyExtServiceLoader. event): com.kerio.im.common.error.ServiceException: Failed to load archive
at com.kerio.im.core.conversation.archive.Archive.open(Archive. java:90)
at com.kerio.im.core.CoreRuntime.setExtService(CoreRuntime.java :93)
at com.kerio.im.service.task.StartServer$LazyExtServiceLoader.e vent(StartServer.java:85)
at com.kerio.im.service.task.StartServer$LazyExtServiceLoader.e vent(StartServer.java:68)
at com.kerio.im.core.Bus.publish(Bus.java:34)
at com.kerio.im.core.remote.RemoteControl.messageReceived(Remot eControl.java:51)
at com.kerio.im.tigase.ConnectComponent.processPacket(ConnectCo mponent.java:129)
at tigase.server.AbstractMessageReceiver$QueueListener.run(Abst ractMessageReceiver.java:1350)
Caused by: java.io.IOException: Destination C:\Program Files\Kerio\MailServer\store\archive\xmpp is not a directory and cant be created
at com.kerio.im.core.conversation.archive.FileStoreManager.<init >(FileStoreManager.java:77)
at com.kerio.im.core.conversation.archive.FileStore.open(FileSt ore.java:22)
at com.kerio.im.core.conversation.archive.Archive.open(Archive. java:72)
... 7 more

Our store directory in Program files is empty as we have store on different drive but it didnt changed during last couple of months.
We are not using instant messaging.

How to fix this.

Thank you
Karel


  •  
hofmank

Messages: 2
Karma: 0
Send a private message to this user
Hello,

additional info, another repeating warnings. All this happend after upgrade to 8.3.0.

config.log
[06/Jun/2014 08:22:49] $instant_messaging - Get private key of certificate server
[06/Jun/2014 08:23:21] $instant_messaging - Get private key of certificate server
[06/Jun/2014 08:23:53] $instant_messaging - Get private key of certificate server
[06/Jun/2014 08:24:26] $instant_messaging - Get private key of certificate server
[06/Jun/2014 08:24:58] $instant_messaging - Get private key of certificate server
[06/Jun/2014 08:25:30] $instant_messaging - Get private key of certificate server
[06/Jun/2014 08:34:59] $instant_messaging - session expired for host 127.0.0.1 from Web Administration.
[06/Jun/2014 08:35:01] $instant_messaging - session expired for host 127.0.0.1 from Web Administration.
[06/Jun/2014 08:36:00] $instant_messaging - session expired for host 127.0.0.1 from Web Administration.
[06/Jun/2014 08:36:01] $instant_messaging - session expired for host 127.0.0.1 from Web Administration.
[06/Jun/2014 08:37:01] $instant_messaging - session expired for host 127.0.0.1 from Web Administration.

debug.log
[06/Jun/2014 09:14:25][9120] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:14:25][9120] {auth} SessionManager: successfully created WebMail session for $instant_messaging special account
[06/Jun/2014 09:14:25][9120] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:14:25][9120] {auth} SessionManager: successfully created WebAdmin session for $instant_messaging special account
[06/Jun/2014 09:15:03][9120] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:15:03][9120] {auth} SessionManager: successfully created WebMail session for $instant_messaging special account
[06/Jun/2014 09:15:03][8388] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:15:03][8388] {auth} SessionManager: successfully created WebAdmin session for $instant_messaging special account
[06/Jun/2014 09:15:46][8388] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:15:46][8388] {auth} SessionManager: successfully created WebMail session for $instant_messaging special account
[06/Jun/2014 09:15:46][9120] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:15:46][9120] {auth} SessionManager: successfully created WebAdmin session for $instant_messaging special account
[06/Jun/2014 09:16:21][9120] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:16:21][9120] {auth} SessionManager: successfully created WebMail session for $instant_messaging special account
[06/Jun/2014 09:16:21][8388] {auth} Special user .imadmin of type 2 successfully authenticated.
[06/Jun/2014 09:16:21][8388] {auth} SessionManager: successfully created WebAdmin session for $instant_messaging special account


Děkuji
Karel
  •  
Tomas Skoda (Kerio)

Messages: 107
Karma: 20
Send a private message to this user
Hi Karel,

This is known issue in Kerio Connect 8.3. 'Target archive folder' configured under 'Archiving and Backup' must exists even if both 'Email archiving' and 'Instant messaging archiving' are disabled. Create 'C:\Program Files\Kerio\MailServer\store\archive\' or point it to another existing destination.

Please try to re-use correct forum thread next time or create new one if you are not sure whether your issue belongs there. The correct thread is http://forums.kerio.com/t/27348// .

Cheers,
Tomas
Previous Topic: Mail rejected in local blacklist
Next Topic: Kerio woring with Active Directory
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Sat Oct 21 17:38:56 CEST 2017

Total time taken to generate the page: 0.00542 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.