Synology Protokol Center: zahlreiche Info-Einträge

German Support for Syncovery on Linux etc.
kt1
Posts: 7
Joined: Tue Oct 11, 2022 10:54 am

Synology Protokol Center: zahlreiche Info-Einträge

Post by kt1 »

Hallo zusammen,

auf meiner Synology im Protocol Center sind alle 30 Sekunden die folgenden Einträge enthalten (DSM7 auf DS920+):

Code: Select all

Info  System  11.10.2022 10:02:52  SYSTEM  [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info  System  11.10.2022 10:02:22  SYSTEM  [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info  System  11.10.2022 10:01:53  SYSTEM  [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info  System  11.10.2022 10:01:22  SYSTEM  [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
1.) Frage: bedeutet dass, dass der Service tatsächlich alle 30 sek, neu startet!?
2.) Falls es nur die Info ist, dass der Service läuft: lassen sich diese Einträge unterdrücken? Die Infos, dass Syncovery initial gestartet oder gestoppt wurde, finde ich hilfreich, aber nicht wiederkehrend im Regelbetrieb zur Laufzeit.

Viele Grüße,
Karsten

tobias
Posts: 1589
Joined: Tue Mar 31, 2020 7:37 pm

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by tobias »

Guten Tag,
es könnte mit dem Ausführen von Profilen zusammenhängen, haben Sie da eins, dass alle 30 Sekunden starten?

Oder der Guardian spinnt und startet tatsächlich den Dienst regelmäßig neu.

Am besten mal den Guardian abschalten: bei den Program Settings unter Advanced auf den Knopf
Stop Syncovery Guardian
klicken.

Die Aktivität und den Status des Guardians kann man bei Port 8900 sehen.

kt1
Posts: 7
Joined: Tue Oct 11, 2022 10:54 am

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by kt1 »

Hallo,
vielen Dank für die schnelle Rückmeldung.
Nein, ein alle 30sek startendes Profil habe ich nicht - so verrückt bin ich dann doch nicht ;-)

Woran sehe ich, ob der Guardian den Dienst stets neu startet? In den Logfiles vom Guardian stand folgendes:

Code: Select all

Syncovery Guardian 1.60, Build 11
Status at 23:08:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Daemon Path: /volume1/@appstore/Syncovery/usr/bin/SyncoveryCL, Exists: Y
Mutex Path: /volume1/@apptemp/Syncovery/syncovery$sffs$schedulermutex
Running as user ID: 200874
Additional Information
Temp Path: /tmp/
Command Line: /volume1/@appstore/Syncovery/usr/bin/SyncoveryGuardian start
Allocated Memory: 1,696 kB, Used Memory: 14,112 Bytes
SyncoveryCL Temp Path: /volume1/@apptemp/Syncovery
Log Path: /volume1/@appdata/Syncovery/Logs
Process List (ps) as of 13-10-22 23:07:25:
root 6034 1 0 Sep27 ? 00:06:38 /usr/sbin/ovsdb-server /tmp/synoovs.db --remote=punix:/var/run/openvswitch/db.sock --remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach
Syncove+ 10406 1 0 Oct06 ? 00:06:47 /volume1/@appstore/Syncovery/usr/bin/SyncoveryCL start /INI=/volume1/@appdata/Syncovery/Syncovery.cfg

(...)

Status at 22:54:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:55:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:55:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:55:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:55:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 22:55:45: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 684641
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 684711
Status at 22:55:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 20:55:54
Status at 22:56:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:56:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:56:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:56:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:56:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 22:56:55: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 684711
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 684781
Status at 22:57:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 20:57:04
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) Scheduler is running. Next profile starts on 10/14/2022 at 01:30:00. The Web Server is already running.: Vaultwarden zu 216 Pulse: 684796
Status at 22:57:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 20:57:14
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) Scheduler is running. Next profile starts on 10/14/2022 at 01:30:00. The Web Server is already running.: Vaultwarden zu 216 Pulse: 684801
Status at 22:57:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 20:57:24
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) Scheduler is running. Next profile starts on 10/14/2022 at 01:30:00. The Web Server is already running.: Vaultwarden zu 216 Pulse: 684818
Status at 22:57:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 20:57:34
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) Scheduler is running. Next profile starts on 10/14/2022 at 01:30:00. The Web Server is already running.: Vaultwarden zu 216 Pulse: 684826
Status at 22:57:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 20:57:44
Status at 22:57:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:58:05: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 684826
Status at 22:58:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:58:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:58:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:58:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 22:58:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 684901
Status at 22:59:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 20:59:04
Status at 22:59:15: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 684901
Status at 22:59:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:59:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:59:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 22:59:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 23:00:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 684971
Status at 23:00:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:00:14
Status at 23:00:25: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 684971
Status at 23:00:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:00:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:00:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:01:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 23:01:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 685041
Status at 23:01:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:01:24
Status at 23:01:35: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 685041
Status at 23:01:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:01:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:02:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:02:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 23:02:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 685111
Status at 23:02:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:02:34
Status at 23:02:45: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 685111
Status at 23:02:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:03:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:03:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:03:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 23:03:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 685181
Status at 23:03:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:03:44
Status at 23:03:55: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 685181
Status at 23:04:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:04:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:04:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:04:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 23:04:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 685251
Status at 23:04:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:04:54
Status at 23:05:05: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 685251
Status at 23:05:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:05:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:05:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:05:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Sending command msgEnquireStatus
Status at 23:05:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) : Vaultwarden zu 216 Pulse: 685321
Status at 23:06:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:06:04
Status at 23:06:15: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 685321
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) Scheduler is running. Next profile starts on 10/14/2022 at 01:30:00. The Web Server is already running.: Vaultwarden zu 216 Pulse: 685349
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) Scheduler is running. Next profile starts on 10/14/2022 at 01:30:00. The Web Server is already running.: Vaultwarden zu 216 Pulse: 685350
Status at 23:06:24: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:06:24
Status at 23:06:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:06:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:06:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:07:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:07:14: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:07:25: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status: Mutex=Y Service=Y Pipe=Y Pulse: 685350
Scheduler Msg: tsaSchedulerRunning 9.48n 64 Bit (Syncovery) Scheduler is running. Next profile starts on 10/14/2022 at 01:30:00. The Web Server is already running.: Vaultwarden zu 216 Pulse: 685411
Status at 23:07:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Pulse change detected, FLastPulseAt now:13-10-22 21:07:34
Status at 23:07:44: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:07:54: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Status at 23:08:04: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=10406
Die Meldungen im Synology-Protocol-Center traten interessanterweise seit meinem Post am Dienstag auch nicht mehr durchgehend alle 30sek auf, sondern ungefähr im Stundentakt, dann aber gleich mehrfach z.T. im Abstand von nur wenigen Sekunden:

Code: Select all

Info System 13.10.2022 23:09:13 SYSTEM [] Guardian Service Stopped.
Info System 13.10.2022 23:06:22 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 23:06:22 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 22:57:38 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 22:57:30 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 22:57:13 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 22:57:09 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 22:05:34 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 22:05:34 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 21:57:32 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 21:57:30 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 21:57:21 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 21:57:17 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 21:39:09 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 20:58:14 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 20:57:32 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 20:57:11 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started. 
Info System 13.10.2022 20:57:11 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 19:58:16 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 19:57:27 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 19:57:18 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 19:57:11 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 18:58:13 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 18:57:31 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 18:57:14 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 18:57:10 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 17:58:16 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 17:57:31 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 17:57:20 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 17:57:15 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 16:58:14 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 16:57:53 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Den Guardian habe ich nun mal abgeschaltet ... in Bezug auf die Meldungen im Protocol Center scheint nun tatsächlich Ruhe zu sein. Aber den Guardian brauchen wir eigentlich schon, oder? Gibt es weitere Protokolle, die ich sichten könnte?
Ich bin nicht so sicher, ob ich Syncovery beim Upgrade von DSM6 auf DSM7 deinstalliert hatte. Kann es damit zusammenhängen?

kt1
Posts: 7
Joined: Tue Oct 11, 2022 10:54 am

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by kt1 »

Update:
Die Ruhe war nur von kurzer Dauer. Trotz gestopptem Guardian geht es mit den Einträgen weiter:

Code: Select all

Info System 13.10.2022 23:58:15 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 23:57:30 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 23:57:21 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 23:57:16 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 13.10.2022 23:09:13 SYSTEM [] Guardian Service Stopped.
Da auf Port 8900 nun keine Webseite mit Protokoll mehr erreichbar ist, gehe ich davon aus, dass der Service auch wirklich gestoppt ist. Der Guardian ist es demnach eher nicht ...
Im Scheduler ist derzeit nur ein Eintrag aktiv, täglich um 1:30 Uhr - der wird es auch nicht sein.

tobias
Posts: 1589
Joined: Tue Mar 31, 2020 7:37 pm

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by tobias »

Hi,
prinzipiell kann diese Meldung jedes Mal kommen, wenn ein Profil gestartet wird. Ich werde das untersuchen

kt1
Posts: 7
Joined: Tue Oct 11, 2022 10:54 am

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by kt1 »

prima, vielen Dank. Derzeit sind einmal pro Stunde jeweils 4 Einträge zu sehen, manchmal auch zwischendurch.
Ich sehe nicht, dass Syncovery permanent einen relevanten System load erzeugt, aber die Einträge machen das Protokoll halt ziemlich unübersichtlich ;-)

stg66
Posts: 7
Joined: Mon Feb 22, 2021 9:01 pm

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by stg66 »

Ich habe genau die gleichen, überflüssigen (?) Protokolleinträge :(
gibt es inzwischen eine Lösung?

tobias
Posts: 1589
Joined: Tue Mar 31, 2020 7:37 pm

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by tobias »

Habt Ihr schon die aktuelle Version 9.49i?

kt1
Posts: 7
Joined: Tue Oct 11, 2022 10:54 am

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by kt1 »

Ja, 9.49i hatte ich schon vor ein paar Tagen installiert - brachte aber diesbezüglich keine Veränderung:

Code: Select all

07.02.2023 19:13:31
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 19:13:03
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 19:11:06
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 19:11:05
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 18:57:33
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 18:57:21
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 18:57:21
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 18:57:09
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 17:58:10
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 17:57:16
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 17:57:05
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 17:57:05
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 16:58:12
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 16:57:23
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 16:57:20
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 16:57:09
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 15:57:33
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 15:57:19
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 15:57:04
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 15:57:04
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 14:57:34
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 14:57:22
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 14:57:20
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
07.02.2023 14:57:08
[Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.

stg66
Posts: 7
Joined: Mon Feb 22, 2021 9:01 pm

Re: Synology Protokol Center: zahlreiche Info-Einträge

Post by stg66 »

ich habe das Update gerade gemacht - hier auch ohne Änderung.
Protokolleinträge ohne Ende.
Was mir auffällt: aller fünf Minuten zwei Einträge. Und ich habe zwei aktive Profile...

Stufe Protokoll Uhrzeit Benutzer Ereignis
Info System 2023/02/07 19:50:11 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:50:06 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:45:12 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:45:06 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:40:11 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:40:05 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:36:12 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:36:09 SYSTEM [Syncovery 9.49i, build 428, English] Running normally. Config file=/volume1/@appdata/Syncovery/Syncovery.cfg.
Info System 2023/02/07 19:36:09 SYSTEM [Syncovery 9.49i, build 428, English] Licensed to: Xxxx Yyyy.
Info System 2023/02/07 19:36:09 SYSTEM System successfully started [Syncovery].
Info System 2023/02/07 19:36:09 SYSTEM [Syncovery] Status after starting: .
Info System 2023/02/07 19:36:08 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:36:07 SYSTEM [Syncovery] Status before starting: .
Info System 2023/02/07 19:36:05 SYSTEM System successfully stopped [Syncovery].
Info System 2023/02/07 19:36:04 SYSTEM [Syncovery] Status after stopping: .
Info System 2023/02/07 19:36:00 SYSTEM [Syncovery 9.49i, build 428, English] Running normally. Config file=/volume1/@appdata/Syncovery/Syncovery.cfg.
Info System 2023/02/07 19:36:00 SYSTEM [Syncovery 9.49i, build 428, English] Licensed to: Xxxx Yyyy.
Info System 2023/02/07 19:36:00 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:35:58 SYSTEM [Syncovery] Status before stopping: .
Info System 2023/02/07 19:35:57 SYSTEM Package [Syncovery] has been successfully updated.
Info System 2023/02/07 19:35:57 SYSTEM System successfully started [Syncovery].
Info System 2023/02/07 19:35:57 SYSTEM [Syncovery] Status after starting: .
Info System 2023/02/07 19:35:57 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:35:56 SYSTEM [Syncovery] Status before starting: .
Info System 2023/02/07 19:35:55 SYSTEM [Syncovery] Status at end of post_install: .
Info System 2023/02/07 19:35:55 SYSTEM [Syncovery] SET /WEBSERVER=localhost result: warning: /bin/sh: setlocale: LC_ALL: cannot change locale (en_GB.UTF-8)
Info System 2023/02/07 19:35:54 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:35:53 SYSTEM [Syncovery] SET /TempPath result: warning: /bin/sh: setlocale: LC_ALL: cannot change locale (en_GB.UTF-8)
Info System 2023/02/07 19:35:52 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:35:51 SYSTEM [Syncovery] SET /DatabasePath result: warning: /bin/sh: setlocale: LC_ALL: cannot change locale (en_GB.UTF-8)
Info System 2023/02/07 19:35:49 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:35:48 SYSTEM [Syncovery] SET /LogFolder result: warning: /bin/sh: setlocale: LC_ALL: cannot change locale (en_GB.UTF-8)
Info System 2023/02/07 19:35:47 SYSTEM [Syncovery 9.49i, build 428, English] SyncoveryCL v9.49i started.
Info System 2023/02/07 19:35:46 SYSTEM [Syncovery] System details: Linux SynNAS 4.4.180+ #42962 SMP Tue Oct 18 15:05:01 CST 2022 x86_64 GNU/Linux synology_apollolake_918+.
Info System 2023/02/07 19:35:46 SYSTEM [Syncovery] File details: -r-xr-xr-x 1 Syncovery Syncovery 26217880 Dec 14 20:08 usr/bin/SyncoveryCL.
Info System 2023/02/07 19:35:46 SYSTEM [Syncovery] Installing to /volume1/@appstore/Syncovery.
Info System 2023/02/07 19:35:43 SYSTEM [Syncovery] Status before installation: .
Info System 2023/02/07 19:35:41 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 2023/02/07 19:35:38 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 2023/02/07 19:35:36 SYSTEM System successfully stopped [Syncovery].
Info System 2023/02/07 19:35:36 SYSTEM [Syncovery] Status after stopping: .
Info System 2023/02/07 19:35:34 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 2023/02/07 19:35:33 SYSTEM [Syncovery] Status before stopping: .
Info System 2023/02/07 19:35:32 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 2023/02/07 19:35:24 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 2023/02/07 19:35:11 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 2023/02/07 19:35:05 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.
Info System 2023/02/07 19:30:11 SYSTEM [Syncovery 9.48n, build 418, English] SyncoveryCL v9.48n started.

Post Reply