Ich habe UCS 4.2-3 (Errata 323) in Verbindung mit Kopano. Jetzt kommt es vereinzelt vor, dass sich Kopano “aufhängt” - dann brauch ich einfach nur den Server neustarten und es geht dann wieder. Leider passierte es häufig in der Nacht. Und wenn dann Mails angekommen, werden diese nicht mehr zugestellt.
Wo kann ich einstellen, dass Postfix (?) die Mails mehrfach versucht zuzustellen und nicht schon nach dem 1. Versuch keinen weiteren unternimmmt?
Huhu,
was genau sagen denn die Logmeldungen aus /var/log/mail.log, wenn so ein Einlieferungsversuch fehlschlägt?
Gruß
mosu
Es geht hier um die Mail von “VeeamLinuxBackup@company.lan”, die nicht zugestellt wurde
Apr 23 04:07:29 ucsXXXXXX postfix/pickup[13947]: 808594B01FD5: uid=0 from=<VeeamLinuxBackup@company.lan>
Apr 23 04:07:29 ucsXXXXXX postfix/cleanup[7319]: 808594B01FD5: message-id=<5add3fe1.2TqVxMomtc4Bwy54%VeeamLinuxBackup@company.lan>
Apr 23 04:07:29 ucsXXXXXX postfix/qmgr[3506]: 808594B01FD5: from=<VeeamLinuxBackup@company.lan>, size=921, nrcpt=1 (queue active)
Apr 23 04:07:29 ucsXXXXXX postfix/pickup[13947]: B73644B013BA: uid=0 from=<root>
Apr 23 04:07:29 ucsXXXXXX postfix/cleanup[7319]: B73644B013BA: message-id=<20180423020729.B73644B013BA@ucsXXXXXX.company.lan>
Apr 23 04:07:29 ucsXXXXXX postfix/qmgr[3506]: B73644B013BA: from=<root@ucsXXXXXX.company.lan>, size=1027, nrcpt=1 (queue active)
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: connect from localhost[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: 8418F4B0201E: client=localhost[127.0.0.1], orig_client=unknown[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/cleanup[7319]: 8418F4B0201E: message-id=<5add3fe1.2TqVxMomtc4Bwy54%VeeamLinuxBackup@company.lan>
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: disconnect from localhost[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/qmgr[3506]: 8418F4B0201E: from=<VeeamLinuxBackup@company.lan>, size=1611, nrcpt=1 (queue active)
Apr 23 04:07:30 ucsXXXXXX amavis[8031]: (08031-06) Passed CLEAN {RelayedInbound}, [127.0.0.1] <VeeamLinuxBackup@company.lan> -> <michael.kolowicz@company.lan>, Message-ID: <5add3fe1.2TqVxMomtc4Bwy54%Ve$
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: connect from localhost[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: C43244B01F72: client=localhost[127.0.0.1], orig_client=unknown[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/cleanup[7319]: C43244B01F72: message-id=<20180423020729.B73644B013BA@ucsXXXXXX.company.lan>
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: disconnect from localhost[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/qmgr[3506]: C43244B01F72: from=<root@ucsXXXXXX.company.lan>, size=1536, nrcpt=1 (queue active)
Apr 23 04:07:30 ucsXXXXXX postfix/smtp[7321]: 808594B01FD5: to=<michael.kolowicz@company.lan>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.32/0.06/0.03/1.1, dsn=2.0.0, status=sent (250 2.0.0 fr$
Apr 23 04:07:30 ucsXXXXXX postfix/qmgr[3506]: 808594B01FD5: removed
Apr 23 04:07:30 ucsXXXXXX amavis[10268]: (10268-05) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <root@ucsXXXXXX.company.lan> -> <root@ucsXXXXXX.company.lan>, Message-ID: <20180423020729.B73644B013BA@u$
Apr 23 04:07:31 ucsXXXXXX postfix/lmtp[7327]: 8418F4B0201E: to=<michael.kolowicz@company.lan>, relay=127.0.0.1[127.0.0.1]:2003, delay=0.6, delays=0.28/0.01/0.03/0.28, dsn=5.1.1, status=bounced (host 127.$
Apr 23 04:07:31 ucsXXXXXX postfix/cleanup[7319]: 111AD4B0203A: message-id=<20180423020731.111AD4B0203A@ucsXXXXXX.company.lan>
Apr 23 04:07:31 ucsXXXXXX postfix/smtp[7322]: B73644B013BA: to=<root@ucsXXXXXX.company.lan>, orig_to=<root>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.7, delays=0.43/0.03/0.01/1.3, dsn=2.0.0, status=sent$
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: B73644B013BA: removed
Apr 23 04:07:31 ucsXXXXXX postfix/bounce[7330]: 8418F4B0201E: sender non-delivery notification: 111AD4B0203A
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 111AD4B0203A: from=<>, size=3698, nrcpt=1 (queue active)
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 8418F4B0201E: removed
Apr 23 04:07:31 ucsXXXXXX postfix/local[7331]: C43244B01F72: to=<systemmail@ucsXXXXXX.company.lan>, orig_to=<root@ucsXXXXXX.company.lan>, relay=local, delay=0.45, delays=0.15/0.04/0/0.26, dsn=5.2.2, st$
Apr 23 04:07:31 ucsXXXXXX postfix/cleanup[7319]: 3D0294B0201E: message-id=<20180423020731.3D0294B0201E@ucsXXXXXX.company.lan>
Apr 23 04:07:31 ucsXXXXXX postfix/lmtp[7327]: 111AD4B0203A: to=<VeeamLinuxBackup@company.lan>, relay=127.0.0.1[127.0.0.1]:2003, delay=0.25, delays=0.12/0/0.03/0.09, dsn=5.1.1, status=bounced (host 127.0.$
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 111AD4B0203A: removed
Apr 23 04:07:31 ucsXXXXXX postfix/bounce[7330]: C43244B01F72: sender non-delivery notification: 3D0294B0201E
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 3D0294B0201E: from=<>, size=3624, nrcpt=1 (queue active)
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: C43244B01F72: removed
Apr 23 04:07:31 ucsXXXXXX postfix/local[7331]: 3D0294B0201E: to=<systemmail@ucsXXXXXX.company.lan>, orig_to=<root@ucsXXXXXX.company.lan>, relay=local, delay=0.2, delays=0.09/0/0/0.11, dsn=5.2.2, status$
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 3D0294B0201E: removed
Huhu,
leider wurden beim Copy & Paste die interessanten Teile abgeschnitten:
…relay=127.0.0.1[127.0.0.1]:2003, delay=0.25, delays=0.12/0/0.03/0.09, dsn=5.1.1, status=bounced (host 127.0.$ ← da geht’s eigentlich noch weiter mit der Meldung.
Gruß
mosu
Sorry - hier nochmal das ganze 
Apr 23 04:07:30 ucsXXXXXX postfix/qmgr[3506]: 8418F4B0201E: from=<VeeamLinuxBackup@company.lan>, size=1611, nrcpt=1 (queue active)
Apr 23 04:07:30 ucsXXXXXX amavis[8031]: (08031-06) Passed CLEAN {RelayedInbound}, [127.0.0.1] <VeeamLinuxBackup@company.lan> -> <michael.kolowicz@company.lan>, Message-ID: <5add3fe1.2TqVxMomtc4Bwy54%VeeamLinuxBackup@company.lan>, mail_id: fxwZ9CczeV4B, Hits: -0.001, size: 921, queued_as: 8418F4B0201E, 925 ms
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: connect from localhost[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: C43244B01F72: client=localhost[127.0.0.1], orig_client=unknown[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/cleanup[7319]: C43244B01F72: message-id=<20180423020729.B73644B013BA@ucsXXXXXX.company.lan>
Apr 23 04:07:30 ucsXXXXXX postfix/smtpd[7326]: disconnect from localhost[127.0.0.1]
Apr 23 04:07:30 ucsXXXXXX postfix/qmgr[3506]: C43244B01F72: from=<root@ucsXXXXXX.company.lan>, size=1536, nrcpt=1 (queue active)
Apr 23 04:07:30 ucsXXXXXX postfix/smtp[7321]: 808594B01FD5: to=<michael.kolowicz@company.lan>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.32/0.06/0.03/1.1, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 8418F4B0201E)
Apr 23 04:07:30 ucsXXXXXX postfix/qmgr[3506]: 808594B01FD5: removed
Apr 23 04:07:30 ucsXXXXXX amavis[10268]: (10268-05) Passed CLEAN {RelayedOpenRelay}, [127.0.0.1] <root@ucsXXXXXX.company.lan> -> <root@ucsXXXXXX.company.lan>, Message-ID: <20180423020729.B73644B013BA@ucsXXXXXX.company.lan>, mail_id: vfhBtYLmIUPg, Hits: 0, size: 1027, queued_as: C43244B01F72, 1066 ms
Apr 23 04:07:31 ucsXXXXXX postfix/lmtp[7327]: 8418F4B0201E: to=<michael.kolowicz@company.lan>, relay=127.0.0.1[127.0.0.1]:2003, delay=0.6, delays=0.28/0.01/0.03/0.28, dsn=5.1.1, status=bounced (host 127.0.0.1[127.0.0.1] said: 503 5.1.1 User does not exist (in reply to RCPT TO command))
Apr 23 04:07:31 ucsXXXXXX postfix/cleanup[7319]: 111AD4B0203A: message-id=<20180423020731.111AD4B0203A@ucsXXXXXX.company.lan>
Apr 23 04:07:31 ucsXXXXXX postfix/smtp[7322]: B73644B013BA: to=<root@ucsXXXXXX.company.lan>, orig_to=<root>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.7, delays=0.43/0.03/0.01/1.3, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as C43244B01F72)
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: B73644B013BA: removed
Apr 23 04:07:31 ucsXXXXXX postfix/bounce[7330]: 8418F4B0201E: sender non-delivery notification: 111AD4B0203A
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 111AD4B0203A: from=<>, size=3698, nrcpt=1 (queue active)
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 8418F4B0201E: removed
Apr 23 04:07:31 ucsXXXXXX postfix/local[7331]: C43244B01F72: to=<systemmail@ucsXXXXXX.company.lan>, orig_to=<root@ucsXXXXXX.company.lan>, relay=local, delay=0.45, delays=0.15/0.04/0/0.26, dsn=5.2.2, status=bounced (cannot update mailbox /var/mail/systemmail for user systemmail. error writing message: File too large)
Apr 23 04:07:31 ucsXXXXXX postfix/cleanup[7319]: 3D0294B0201E: message-id=<20180423020731.3D0294B0201E@ucsXXXXXX.company.lan>
Apr 23 04:07:31 ucsXXXXXX postfix/lmtp[7327]: 111AD4B0203A: to=<VeeamLinuxBackup@company.lan>, relay=127.0.0.1[127.0.0.1]:2003, delay=0.25, delays=0.12/0/0.03/0.09, dsn=5.1.1, status=bounced (host 127.0.0.1[127.0.0.1] said: 503 5.1.1 User does not exist (in reply to RCPT TO command))
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 111AD4B0203A: removed
Apr 23 04:07:31 ucsXXXXXX postfix/bounce[7330]: C43244B01F72: sender non-delivery notification: 3D0294B0201E
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 3D0294B0201E: from=<>, size=3624, nrcpt=1 (queue active)
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: C43244B01F72: removed
Apr 23 04:07:31 ucsXXXXXX postfix/local[7331]: 3D0294B0201E: to=<systemmail@ucsXXXXXX.company.lan>, orig_to=<root@ucsXXXXXX.company.lan>, relay=local, delay=0.2, delays=0.09/0/0/0.11, dsn=5.2.2, status=bounced (cannot update mailbox /var/mail/systemmail for user systemmail. error writing message: File too large)
Apr 23 04:07:31 ucsXXXXXX postfix/qmgr[3506]: 3D0294B0201E: removed
Huhu,
Das hier ist ja die entscheidende Zeile. Fehler aus der 500er Reihe sind permanente Fehler, die ein Client (also hier Postfix) nicht erneut versuchen sollte. Daher kann man das auch nicht einfach konfigurieren.
Es sollte also eher versucht werden, die eigentliche Ursache zu beheben:
michael.kolowicz@company.lan?m.
dieses Verhalten hatten wir auch eine ganze Weile. Ursache waren automatisch konfigurierte Updates. Im Falle von Kopano Updates wurden aber die entspr. daemons nicht durchgestartet und der postfix hat mit dem 500er weitere Zustellversuche eingestellt.
Meine Lösung: Keine automatischen Updates mehr an Servern, wo Kopano läuft.
Huhu,
Ich kenne ähnliches Verhalten, vermute aber, dass das Problem des OPs eher im logrotate liegt. Beim logrotate werden die Daemons neu geladen, was dazu führt, dass sie u.a. auch ihre SSL-Zertifikate neu einlesen wollen. Die Daemons laufen als User kopano, sodass man hier vorsichtig sein muss: Datei- und Verzeichnisrechte zu den SSL-Zertifikaten müssen das halt zulassen.
Gruß
mosu
Mir ist nicht ganz klar was ein 5.1.1 User does not exist mit einem nicht neugestalteten Dienst zu tun haben kann.
Danke für die Tipps.
Hier ein Auszug aus dem Kopano-Server Log
Sun Apr 22 18:52:44 2018: [error ] Previous message logged 100 times
Sun Apr 22 18:52:44 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Sun Apr 22 23:47:45 2018: [error ] Previous message logged 100 times
Sun Apr 22 23:47:45 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Mon Apr 23 01:08:27 2018: [=======] Starting kopano-server version 8.5.5 (pid 32025)
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'server_max_keep_alive_requests' is not used anymore.
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Mon Apr 23 01:08:27 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Mon Apr 23 01:08:27 2018: [crit ] Unable to bind to port 236: Address already in use. This is usually caused by another process (most likely another server) already using this port. This program will terminate now.
Mon Apr 23 01:15:01 2018: [error ] Previous message logged 43 times
Mon Apr 23 01:15:01 2018: [warning] LDAP (simple) bind on cn=ucsXXXXXX,cn=dc,cn=computers,dc=company,dc=lan failed: Invalid credentials
Mon Apr 23 01:15:01 2018: [warning] K-1501: Unable to retrieve details from external user source: Failure connecting any of the LDAP servers
Mon Apr 23 01:17:45 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Mon Apr 23 01:17:45 2018: [warning] LDAP (simple) bind on cn=ucsXXXXXX,cn=dc,cn=computers,dc=company,dc=lan failed: Invalid credentials
Mon Apr 23 01:17:45 2018: [warning] Authentication by plugin failed for user "mkolowicz": Trying to authenticate failed: Failure connecting any of the LDAP servers; username = mkolowicz
Mon Apr 23 01:30:01 2018: [warning] LDAP (simple) bind on cn=ucsXXXXXX,cn=dc,cn=computers,dc=company,dc=lan failed: Invalid credentials
Mon Apr 23 01:30:01 2018: [warning] K-1501: Unable to retrieve details from external user source: Failure connecting any of the LDAP servers
Mon Apr 23 01:32:45 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
M
Durch diesen “Neustart” (warum auch immer) werden gewisse Resourcen/Ports nicht freigegeben - danach ist es nicht mehr möglich an irgendjemand was zu senden. Erst wenn ich den Server komplett runterfahre und neustarte, dann klappt es wieder mit der Zustellung.
Wie gesagt, es wäre toll, wenn in solch einem Fall die Mails nicht verworfen werden, sondern zeitverzögert zugestellt würden.
Die Benutzer existieren sowohl auf LDAP-Seite sowie auf Kopano-Seite, denn nach dem Neustart wird ja alles wieder perfekt ausgeführt
Moin,
fuer mich sieht es so aus, als ob um 1:08 versucht wird, kopano-server zu starten, obwohl der noch laeuft. Auf jedenfall beendet sich der sofort wieder.
Die Meldungen davor und danach zeigen aber das eigentliche Problem: kopano kann das LDAP nicht mehr abfragen. Der Zeitpunkt legt nahe, dass es mit der automatischen Erneuerung des /etc/kopano-ldap.secret Passworts (imho alle drei Wochen), bzw. dem Restart des kopano-server Prozesses danach zu tun hat. Mit dem alten PW klappt dann das Binden ans LDAP nicht mehr. Nach einem Reboot ist dann natuerlich wieder alles ok.
Das würde passen - denn von meinem Gefühl her, ist es tatsächlich so, dass es alle 3 Wochen passiert
Wie kann ich das autm. erneuern deaktivieren bzw. was kann man tun, damit der nachfolgene Restart des kopano-server erfolgreich ist?
Die UCR Variable server/password/change erlaubt (default) oder verbietet das Erneuern. Die Abschaltung ist aber imho eine schlechte Loesung. Auch kann ein anderen Benutzer fuer den LDAP Zugriff konfiguriert werden, dessen Pasword dann nicht automatisch rotiert wird. Schliesslich kann der anonyme Zugriff vom Kopano Server auf das LDAP erlaubt werden (ldap/acl/read/* Variablen).
Allerdings sind das alles nur Workarounds. Stattdessen sollte das eigentliche Problem behoben werden. Das Skript was den Neustart versucht ist /usr/lib/univention-server/server_password_change.d/70kopano. Was passiert, wenn das dort benutze Kommando zum Restart von Hand ausgefuehrt wird?
Wenn ich den Befehl service kopano-server restart ausführe, dann kommt es so selben Fehlermeldung/Konstellation:
Tue Apr 24 12:00:04 2018: [error ] Previous message logged 100 times
Tue Apr 24 12:00:04 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Tue Apr 24 15:20:07 2018: [error ] Previous message logged 100 times
Tue Apr 24 15:20:07 2018: [error ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Tue Apr 24 17:00:49 2018: [=======] Starting kopano-server version 8.5.8 (pid 6346)
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'server_max_keep_alive_requests' is not used anymore.
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Tue Apr 24 17:00:49 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Tue Apr 24 17:00:49 2018: [crit ] Unable to bind to port 236: Address already in use. This is usually caused by another process (most likely another server) already using this port. This program will terminate now.
Moin,
da fehlen komplett die Meldungen, die bei Stoppen entstehen, es wird also ziemlich sicher nur versucht kopano-server neu zustarten. Was ist die Ausgabe von service kopano-server status (es sollte die gleiche wie von systemctl status kopano-server sein)? Was sagt journalctl -u kopano-server?
Wann soll ich die Statusinformationen abfragen - wenn er noch normal läuft, oder wenn ich denn “restart” des Dienstes gemacht habe und es zu der Meldung kommt?
Vor dem Restart, also wenn alles noch normal laeuft.
Hier die Ausgaben über den Status:
root@ucs002090:~# service kopano-server status
● kopano-server.service - Kopano Core Storage Server
Loaded: loaded (/lib/systemd/system/kopano-server.service; enabled)
Active: failed (Result: exit-code) since Di 2018-04-24 17:06:38 CEST; 20h ago
Docs: man:kopano-server(8)
man:kopano-server.cfg(5)
man:kopano-admin(8)
Process: 2884 ExecStart=/usr/sbin/kopano-server -F (code=exited, status=255)
Main PID: 2884 (code=exited, status=255)
Apr 24 17:06:37 ucs002090 kopano-server[2884]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 24 17:06:38 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 24 17:06:38 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
root@ucs002090:~# systemctl status kopano-server
● kopano-server.service - Kopano Core Storage Server
Loaded: loaded (/lib/systemd/system/kopano-server.service; enabled)
Active: failed (Result: exit-code) since Di 2018-04-24 17:06:38 CEST; 20h ago
Docs: man:kopano-server(8)
man:kopano-server.cfg(5)
man:kopano-admin(8)
Process: 2884 ExecStart=/usr/sbin/kopano-server -F (code=exited, status=255)
Main PID: 2884 (code=exited, status=255)
Apr 24 17:06:37 ucs002090 kopano-server[2884]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 24 17:06:38 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 24 17:06:38 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
root@ucs002090:~# journalctl -u kopano-server
-- Logs begin at Mi 2018-01-31 22:20:46 CET, end at Mi 2018-04-25 13:58:32 CEST. --
Feb 05 08:36:06 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:36:06 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 05 08:57:48 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:57:48 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 05 08:57:57 ucs002090 kopano-server[2404]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Feb 11 12:58:37 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 11 12:58:37 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 11 12:58:48 ucs002090 kopano-server[2411]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 11 12:58:48 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 11 12:58:48 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 17 01:01:31 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 01:01:31 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 17 23:37:47 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 23:37:47 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 17 23:37:51 ucs002090 kopano-server[2368]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 17 23:37:52 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 17 23:37:52 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
-- Reboot --
Feb 20 22:05:30 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 20 22:05:30 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 20 22:05:37 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 20 22:05:37 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 20 22:06:09 ucs002090 kopano-server[2611]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Feb 21 21:41:55 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 21 21:41:55 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 21 21:41:59 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 21 21:41:59 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 21 21:42:05 ucs002090 kopano-server[2375]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Mär 10 01:10:26 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 10 01:10:26 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Mär 10 08:40:19 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 10 08:40:19 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Mär 10 08:40:33 ucs002090 kopano-server[2637]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Mär 17 15:29:18 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 17 15:29:18 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Mär 17 15:29:26 ucs002090 kopano-server[2406]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Mär 17 15:29:27 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Mär 17 15:29:27 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 01 01:05:12 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 01 01:05:12 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 06 15:52:01 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 06 15:52:01 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 06 15:52:04 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 06 15:52:04 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 06 15:52:06 ucs002090 kopano-server[2384]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 01:08:27 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 01:08:27 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 23 07:29:03 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 07:29:03 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 23 07:29:09 ucs002090 kopano-server[2371]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 07:29:09 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 23 07:29:09 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
-- Reboot --
Apr 23 14:15:52 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 14:15:52 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 23 14:15:58 ucs002090 kopano-server[2564]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 14:16:02 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 23 14:16:02 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 24 17:00:49 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 24 17:00:49 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 24 17:03:20 ucs002090 systemd[1]: Stopped Kopano Core Storage Server.
Apr 24 17:03:23 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 24 17:03:23 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 24 17:06:37 ucs002090 kopano-server[2884]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 24 17:06:38 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 24 17:06:38 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Ok, der Status passt, da ja bei jedem ‘Restart’ der neu gestartete kopano-server Prozess gleich wieder aussteigt. Im Journal sieht man auch, dass garnicht erst versucht wird zu stoppen.
Bitte mal explizit systemctl stop kopano-server ausfuehren, danach nochmal die beiden Kommandos von oben. Schliesslich systemctl start kopano-server und danach wieder die beiden Kommandos.
Nach dem Stoppen des Servers
root@ucs002090:~# service kopano-server status
● kopano-server.service - Kopano Core Storage Server
Loaded: loaded (/lib/systemd/system/kopano-server.service; enabled)
Active: failed (Result: exit-code) since Di 2018-04-24 17:06:38 CEST; 22h ago
Docs: man:kopano-server(8)
man:kopano-server.cfg(5)
man:kopano-admin(8)
Process: 2884 ExecStart=/usr/sbin/kopano-server -F (code=exited, status=255)
Main PID: 2884 (code=exited, status=255)
Apr 24 17:06:37 ucs002090 kopano-server[2884]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 24 17:06:38 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 24 17:06:38 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 25 16:06:00 ucs002090 systemd[1]: Stopped Kopano Core Storage Server.
root@ucs002090:~# journalctl -u kopano-server
-- Logs begin at Mi 2018-01-31 22:20:46 CET, end at Mi 2018-04-25 16:06:15 CEST. --
Feb 05 08:36:06 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:36:06 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 05 08:57:48 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:57:48 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 05 08:57:57 ucs002090 kopano-server[2404]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Feb 11 12:58:37 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 11 12:58:37 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 11 12:58:48 ucs002090 kopano-server[2411]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 11 12:58:48 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 11 12:58:48 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 17 01:01:31 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 01:01:31 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 17 23:37:47 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 23:37:47 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 17 23:37:51 ucs002090 kopano-server[2368]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 17 23:37:52 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 17 23:37:52 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
-- Reboot --
Feb 20 22:05:30 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 20 22:05:30 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Logs begin at Mi 2018-01-31 22:20:46 CET, end at Mi 2018-04-25 16:06:15 CEST. --
Feb 05 08:36:06 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:36:06 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 05 08:57:48 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:57:48 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 05 08:57:57 ucs002090 kopano-server[2404]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Feb 11 12:58:37 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 11 12:58:37 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 11 12:58:48 ucs002090 kopano-server[2411]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 11 12:58:48 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 11 12:58:48 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 17 01:01:31 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 01:01:31 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 17 23:37:47 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 23:37:47 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 17 23:37:51 ucs002090 kopano-server[2368]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 17 23:37:52 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 17 23:37:52 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
-- Reboot --
Feb 20 22:05:30 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 20 22:05:30 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 20 22:05:37 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 20 22:05:37 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 20 22:06:09 ucs002090 kopano-server[2611]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Feb 21 21:41:55 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 21 21:41:55 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 21 21:41:59 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 21 21:41:59 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 21 21:42:05 ucs002090 kopano-server[2375]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Mär 10 01:10:26 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 10 01:10:26 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Mär 10 08:40:19 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 10 08:40:19 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Mär 10 08:40:33 ucs002090 kopano-server[2637]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Mär 17 15:29:18 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 17 15:29:18 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Mär 17 15:29:26 ucs002090 kopano-server[2406]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Mär 17 15:29:27 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Mär 17 15:29:27 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 01 01:05:12 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 01 01:05:12 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 06 15:52:01 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 06 15:52:01 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 06 15:52:04 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 06 15:52:04 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 06 15:52:06 ucs002090 kopano-server[2384]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 01:08:27 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 01:08:27 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 23 07:29:03 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 07:29:03 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 23 07:29:09 ucs002090 kopano-server[2371]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 07:29:09 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 23 07:29:09 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
-- Reboot --
Apr 23 14:15:52 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 14:15:52 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 23 14:15:58 ucs002090 kopano-server[2564]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 14:16:02 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 23 14:16:02 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 24 17:00:49 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 24 17:00:49 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 24 17:03:20 ucs002090 systemd[1]: Stopped Kopano Core Storage Server.
Apr 24 17:03:23 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 24 17:03:23 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 24 17:06:37 ucs002090 kopano-server[2884]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 24 17:06:38 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 24 17:06:38 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 25 16:06:00 ucs002090 systemd[1]: Stopped Kopano Core Storage Server.
Server wieder gestartet:
root@ucs002090:~# systemctl start kopano-server
root@ucs002090:~# service kopano-server status
● kopano-server.service - Kopano Core Storage Server
Loaded: loaded (/lib/systemd/system/kopano-server.service; enabled)
Active: inactive (dead) since Mi 2018-04-25 16:10:23 CEST; 4s ago
Docs: man:kopano-server(8)
man:kopano-server.cfg(5)
man:kopano-admin(8)
Process: 4266 ExecStart=/usr/sbin/kopano-server -F (code=killed, signal=TERM)
Main PID: 4266 (code=killed, signal=TERM)
Apr 25 16:10:23 ucs002090 systemd[1]: Started Kopano Core Storage Server.
root@ucs002090:~# journalctl -u kopano-server
-- Logs begin at Mi 2018-01-31 22:20:46 CET, end at Mi 2018-04-25 16:10:23 CEST. --
Feb 05 08:36:06 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:36:06 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 05 08:57:48 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 05 08:57:48 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 05 08:57:57 ucs002090 kopano-server[2404]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Feb 11 12:58:37 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 11 12:58:37 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 11 12:58:48 ucs002090 kopano-server[2411]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 11 12:58:48 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 11 12:58:48 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 17 01:01:31 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 01:01:31 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Feb 17 23:37:47 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 17 23:37:47 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 17 23:37:51 ucs002090 kopano-server[2368]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Feb 17 23:37:52 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 17 23:37:52 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
-- Reboot --
Feb 20 22:05:30 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 20 22:05:30 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 20 22:05:37 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 20 22:05:37 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 20 22:06:09 ucs002090 kopano-server[2611]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Feb 21 21:41:55 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Feb 21 21:41:55 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Feb 21 21:41:59 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Feb 21 21:41:59 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Feb 21 21:42:05 ucs002090 kopano-server[2375]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Mär 10 01:10:26 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 10 01:10:26 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Mär 10 08:40:19 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 10 08:40:19 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Mär 10 08:40:33 ucs002090 kopano-server[2637]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
-- Reboot --
Mär 17 15:29:18 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Mär 17 15:29:18 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Mär 17 15:29:26 ucs002090 kopano-server[2406]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Mär 17 15:29:27 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Mär 17 15:29:27 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 01 01:05:12 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 01 01:05:12 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 06 15:52:01 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 06 15:52:01 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 06 15:52:04 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 06 15:52:04 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 06 15:52:06 ucs002090 kopano-server[2384]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 01:08:27 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 01:08:27 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 23 07:29:03 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 07:29:03 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 23 07:29:09 ucs002090 kopano-server[2371]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 07:29:09 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 23 07:29:09 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
-- Reboot --
Apr 23 14:15:52 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 23 14:15:52 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 23 14:15:58 ucs002090 kopano-server[2564]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 23 14:16:02 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 23 14:16:02 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 24 17:00:49 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 24 17:00:49 ucs002090 systemd[1]: Started Kopano Core Storage Server.
Apr 24 17:03:20 ucs002090 systemd[1]: Stopped Kopano Core Storage Server.
Apr 24 17:03:23 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 24 17:03:23 ucs002090 systemd[1]: Started Kopano Core Storage Server.
-- Reboot --
Apr 24 17:06:37 ucs002090 kopano-server[2884]: An error occurred (80000007). Please check logfile "/var/log/kopano/server.log" for details.
Apr 24 17:06:38 ucs002090 systemd[1]: kopano-server.service: main process exited, code=exited, status=255/n/a
Apr 24 17:06:38 ucs002090 systemd[1]: Unit kopano-server.service entered failed state.
Apr 25 16:06:00 ucs002090 systemd[1]: Stopped Kopano Core Storage Server.
Apr 25 16:10:23 ucs002090 systemd[1]: Starting Kopano Core Storage Server...
Apr 25 16:10:23 ucs002090 systemd[1]: Started Kopano Core Storage Server.