After reboot client can not connect to server (core-8.7.84.60)

mclu

Hi
I recently updated my Ubuntu 16.04 with the newest available community edition
(core-8.7.84.60.8b9c444-Ubuntu_16.04-amd64.tar.gz)

Everything worked fine until my virtual server was rebooted.
After the reboot the kopano server.log looks fine but spooler, webapp and all the other tools can not connect!

Spooler log:

HrLogon server "default:" user "SYSTEM": network error
2019-10-24T10:25:09.549517: [  248] [error  ] Unable to open admin session: network error (80040115)
2019-10-24T10:25:12.550263: [  248] [error  ] gsoap connect: ()

Serverlog:

2019-10-24T10:24:39.815568: [warning] Shutting down
2019-10-24T10:24:39.823350: [info   ] Shutdown all current sessions
2019-10-24T10:24:39.823677: [info   ] Shutdown notification manager
2019-10-24T10:24:40.831794: [notice ] Waiting for mysql_server_end
2019-10-24T10:24:40.831847: [notice ] Waiting for mysql_library_end
2019-10-24T10:24:40.831855: [=======] Server shutdown complete.
2019-10-24T10:25:05.853822: [info   ] Audit logging not enabled.
2019-10-24T10:25:05.853897: [=======] Starting kopano-server version 8.7.84 (pid 514 uid 0)
2019-10-24T10:25:05.853938: [info   ] Using epoll events
2019-10-24T10:25:05.854275: [info   ] Listening on 0.0.0.0:236 (fd 6)
2019-10-24T10:25:05.854357: [info   ] Listening on [::]:236 (fd 7)
2019-10-24T10:25:05.856280: [info   ] Listening on unix:/var/run/kopano/prio.sock (fd 8)
2019-10-24T10:25:05.856443: [info   ] Listening on unix:/var/run/kopano/server.sock (fd 9)
2019-10-24T10:25:06.880258: [info   ] Audit logging not enabled.
2019-10-24T10:25:06.880341: [=======] Starting kopano-server version 8.7.84 (pid 514 uid 999)
2019-10-24T10:25:06.880381: [info   ] Using epoll events
2019-10-24T10:25:06.880589: [info   ] Re-using fd 6 for 0.0.0.0:236
2019-10-24T10:25:06.880612: [info   ] Re-using fd 7 for [::]:236
2019-10-24T10:25:06.882378: [info   ] Re-using fd 8 for unix:/var/run/kopano/prio.sock
2019-10-24T10:25:06.882464: [info   ] Re-using fd 9 for unix:/var/run/kopano/server.sock
2019-10-24T10:25:06.889369: [notice ] Connection to database 'kopano' succeeded
2019-10-24T10:25:06.909816: [info   ] Using the "files" attachment storage backend
2019-10-24T10:25:06.914900: [info   ] Setting object cache size: 16777216
2019-10-24T10:25:06.914922: [info   ] Setting indexedobject cache size: 33554432
2019-10-24T10:25:06.914929: [info   ] Setting quota cache size: 1048576
2019-10-24T10:25:06.914935: [info   ] Setting userdetails cache size: 26214400
2019-10-24T10:25:06.923339: [notice ] Querying database for searchfolders. This may take a while.
2019-10-24T10:25:07.064156: [notice ] Loading search folders.
2019-10-24T10:25:07.115434: [notice ] Done loading search folders.
2019-10-24T10:25:07.115637: [notice ] Startup succeeded on pid 514

If I manually restart the kopano server process everything reconnects and everything works again.
Where should I look? Maybe delay the kopano server startup?

Thx for your suggestions
Markus Lutum

fbartels

Hi @mclu,

this is currently a known issue. You can follow progress at https://jira.kopano.io/browse/KC-1616.

mclu

I can not add a Jira comment so I want to comment on
https://jira.kopano.io/browse/KC-1616?focusedCommentId=35398&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-35398

@jengelhardt : Im not using docker so its not only a docker cornercase. I run it on a VServer instance from Strato (Provider).

Greet Markus

jengelh

Yes, I figured that it is because /run/kopano can be, and in fact is, empty after a reboot (or equivalent). Other cases would include PrivateTmp=yes. Appropriate pull requests are already afloat.