QNAP NAS recurrent error

English Support for Syncovery on Linux etc.
Post Reply
Taels
Posts: 6
Joined: Sun Apr 03, 2022 4:13 pm

QNAP NAS recurrent error

Post by Taels »

I just did a clean reinitialization of my QNAP NAS, installed the last version of Syncovery and I am getting dozens of this error message:

Warning 2022-04-03 13:30:50 System 127.0.0.1 --- --- [Syncovery 9.47f, build 380, English] Stopping, possibly an unneeded extra invocation.

Important: Syncovery is working just fine. Already did dozens of backup jobs. But I am still getting dozens of these errors even though no jobs are running.

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

Re: QNAP NAS recurrent error

Post by tobias »

Hello,
I know that these messages can occur a few times during or after installation, but they should eventually stop.

Maybe the QNAP operating system can't detect that Syncovery is running and it's trying to start it repeatedly, or Syncovery's own Guardian is doing that.

What status does the QNAP App Center show for Syncovery? Maybe it helps to stop and restart Syncovery from there?

Can you check the Guardian status at port 8900?
For example,
http://192.168.12.45:8900/

If the page does not show, then the Guardian is not installed, so that would be fine.

Taels
Posts: 6
Joined: Sun Apr 03, 2022 4:13 pm

Re: QNAP NAS recurrent error

Post by Taels »

Syncovery is running according to App Center. Its icon is on the QNAP dashboard.

I will try to stop it and restart it again.

Guardian status shows this:

Syncovery Guardian 1.60, Build 11

Status at 23:40:34: MutexOK=Y, PipeStatusOK=Y, ServiceOK=N, PID=

Daemon Path: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/SyncoveryCL, Exists: Y
Mutex Path: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/.Syncovery/tmp/syncovery$sffs$schedulermutex
Running as user ID: 0

Additional Information

Temp Path: /tmp/
Command Line: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/SyncoveryGuardian start

Allocated Memory: 1,760 kB, Used Memory: 17,024 Bytes

SyncoveryCL Temp Path: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/.Syncovery/tmp
Log Path: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/Logs

Process List (ps) as of 3-4-22 23:40:34:

0


Click here to see the log files.

Click here to see the thread report (can take 30 seconds).


Click here to start the SyncoveryCL daemon.

Click here to stop the SyncoveryCL daemon gracefully.

Click here to send a STOP signal to the SyncoveryCL daemon.

Click here to kill the SyncoveryCL daemon.

Click here to terminate the Guardian process.



Guardian Activity Log:


2-4-22 21:09:40 INFO: Guardian Service Started
2-4-22 21:17:18 ERROR: Service not running - need to start service.
2-4-22 21:17:18 INFO: Starting service/daemon in /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/SyncoveryCL
2-4-22 21:17:34 ERROR: Service not running - need to start service.
2-4-22 21:17:34 INFO: Starting service/daemon in /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/SyncoveryCL
2-4-22 21:19:01 ERROR: Service not running - need to start service.
2-4-22 21:19:01 INFO: Starting service/daemon in /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/SyncoveryCL
[...]

Initial output: 21:09:36 SyncoveryCL v9.47f

Reading config file /etc/SyncoveryCL.conf
Temp folder from /etc/SyncoveryCL.conf: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/.Syncovery/tmp
21:09:36 Initializing
21:09:38 Log folder: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/Logs
21:09:38 Configuration File: /share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/Syncovery.cfg
21:09:39 Licensed to: [my email]

TMP=/share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/.Syncovery/tmp
MUTEX=/share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/.Syncovery/tmp
LOGS=/share/CE_CACHEDEV1_DATA/.qpkg/SyncoveryCL/Logs


Detailed Activity Log:

Sending command msgEnquireStatus
Status at 20:52:26: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Scheduler Msg: tsaSchedulerRunning 9.47f 64 Bit (admin) : Backup hidden Pulse: 85351
Status at 20:52:36: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Pulse change detected, FLastPulseAt now:3-4-22 23:52:36
Status at 20:52:46: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:52:56: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:53:06: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:53:16: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:53:26: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status: Mutex=Y Service=Y Pipe=Y Pulse: 85351
Sending command msgEnquireStatus
Status at 20:53:36: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Scheduler Msg: tsaSchedulerRunning 9.47f 64 Bit (admin) : Backup hidden Pulse: 85421
Status at 20:53:46: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Pulse change detected, FLastPulseAt now:3-4-22 23:53:46
Status at 20:53:56: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:54:06: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:54:16: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:54:26: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:54:36: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status: Mutex=Y Service=Y Pipe=Y Pulse: 85421
Sending command msgEnquireStatus
Status at 20:54:46: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Scheduler Msg: tsaSchedulerRunning 9.47f 64 Bit (admin) : Backup hidden Pulse: 85491
Status at 20:54:56: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Pulse change detected, FLastPulseAt now:3-4-22 23:54:56
Status at 20:55:06: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:55:16: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:55:26: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:55:36: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status at 20:55:46: MutexOK=Y, PipeStatusOK=Y, ServiceOK=Y, PID=32093
Status: Mutex=Y Service=Y Pipe=Y Pulse: 85491
[...]

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

Re: QNAP NAS recurrent error

Post by tobias »

Hi,
OK, it seems that the Guardian is malfunctioning.

You don't actually need it. Just stop it. You can stop it permanently from the Program Settings dialog in Syncovery, tab sheet "Advanced". There is a button "Stop Syncovery Guardian". Which also means it won't be restarted on the next boot.

If you have the Guardian as a separate app in the QNAP App Center, please stop it there too.

Post Reply