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?