Syncovery crashing on Fedora

[CDR224]

I installed Syncovery on a new Laptop under Fedora 44 KDE Plasma Desktop.

At first, it seened to work. I could define jobs and run them without issues. But then, the next day I couldn't connect to the web page anymore.
Re-installed Syncovery and everything was back ... for a short time. Then the same issue again.

Uninstalled and completely removed everything I could find (config files, etc). Re-installed. Worked. Until the next day ...

[tobias]

Hello,
do you have the latest version 11.15.14?

On Fedora, usually SELinux prevents access to the web GUI, except immediately after (re)installation.

So you need to disable SELinux or allow Syncovery thru it. Unfortunately I don't have instructions for that right now.

I don't think it's a crash really, but please look in the Syncovery logs folder for files like SyncoveryCL_Exceptions.log.

[CDR224]

Thank you for the tips, Tobias.
I looked at the SELinux Troubleshooter and there was nothing about Syncovery there.
And I can't find the Syncovery log file (tried searching, but that involves searching through hundreds of thousands of files and folders on my NAS because the shares are mounted under my home folder ... and I don't know how to exclude those from searching).

As a test, I did a modification in a folder that should be synchronized in real time by one of the Syncovery jobs. Nothing was synchronized, so I think that Syncovery is actually not running. No idea where to look now ...

[CDR224]

Ok, I found this in the list of services:

Code: Select all

syncoverycl.service                                                                       loaded active exited  Syncovery Scheduler Service

[tobias]

Hello,
there should be additional log files, such as WebGUI.log. Please look. There should be a .Syncovery folder containing lots of logs.

You can see the paths that Syncovery uses here:
/etc/SyncoveryCL.conf

It is also interesting to start Syncovery in a terminal and view its output. Because the service usually runs as root, you should probably enter these two lines:
sudo su
SyncoveryCL

and watch.

[CDR224]

This is all that's in the WebGUI.log file:

Code: Select all

17.06.2026 20:33:53.697: No port defined for SSL
17.06.2026 20:33:53.697: Starting Web Server
17.06.2026 20:33:53.697: Added binding with IP=localhost and Port=8999
17.06.2026 20:33:53.697: Plain HTTP Port is 8999
17.06.2026 20:33:53.697: Web server IP localhost, port 8999, Docs path: /usr/lib/Syncovery/WebDocs
18.06.2026 00:00:16.714: Stopping Web Server
18.06.2026 00:00:16.715: Web Server Stopped

The last two lines correspond with the shutdown of the PC. Nothing else from today.

Same thing for Syncovery.cfg-log.txt:

Code: Select all

17-06-26 20:33:47: TTGSQLIniFile.OpenDatabase: /etc/.Syncovery/Syncovery.cfg
17-06-26 20:33:47: /etc/.Syncovery/Syncovery.cfg does not exist yet, checking if a backup exists
17-06-26 20:33:47: Finding Backup File(DBneedstobeclosed:N, CopyBackupToDB:Y, OpenDB:N)
17-06-26 20:33:47: No Backup DB Found
17-06-26 20:33:47: /etc/.Syncovery/Syncovery.cfg: creating new SQL file
17-06-26 20:33:53: TTGSQLIniFile.OpenDatabase: /etc/.Syncovery/Syncovery.cfg
17-06-26 20:33:53: Copied /etc/.Syncovery/Syncovery.cfg to /etc/.Syncovery/Syncovery.cfg.bak
17-06-26 20:33:53: Copied /etc/.Syncovery/Syncovery.cfg to /etc/.Syncovery/CfgBackups/Syncovery.cfg (17-06-26 20.33.53)
17-06-26 20:33:53: /etc/.Syncovery/Syncovery.cfg data string count: 72
17-06-26 20:33:53: /etc/.Syncovery/Syncovery.cfg entry count in section Profiles: 0
17-06-26 20:33:53: Finding Backup File(DBneedstobeclosed:Y, CopyBackupToDB:Y, OpenDB:Y)
17-06-26 20:33:53: Renamed empty file from /etc/.Syncovery/Syncovery.cfg.bak to /etc/.Syncovery/Syncovery.empty.bak-17-06-26 20.33.53
17-06-26 20:33:53: Renamed empty file from /etc/.Syncovery/CfgBackups/Syncovery.cfg (17-06-26 20.33.53) to /etc/.Syncovery/CfgBackups/Syncovery.empty (17-06-26 20.33.53)-17-06-26 20.33.53
17-06-26 20:33:53: No Backup DB Found
18.06.2026 00:00:21: Copied /etc/.Syncovery/Syncovery.cfg to /etc/.Syncovery/Syncovery.cfg.bak
18.06.2026 00:00:21: Copied /etc/.Syncovery/Syncovery.cfg to /etc/.Syncovery/CfgBackups/Syncovery.cfg (18.06.2026 00.00.21)

Again, nothing from today. It's as if it never even started ...

After starting from the command-line, it works again:

Code: Select all

SyncoveryCL
16:52:50 SyncoveryCL v11.15.8

Reading config file /etc/SyncoveryCL.conf
Temp folder from /etc/SyncoveryCL.conf: /var/run/.syncoverytemp
16:52:50 Initializing
16:52:50 Opening Database
Changed perms of /var/run/.syncoverytemp to 777, result code =0
16:52:50 Log folder: /etc/.Syncovery/Logs
16:52:50 Configuration File: /etc/.Syncovery/Syncovery.cfg
16:52:50 Limited Free Edition. Remaining Pro Evaluation Days: 28

16:52:50 Initiating interprocess communication as server
16:52:50 Loading profiles
16:52:51 Starting Scheduler. Time Zone: UTC+02:00
16:52:51 Scheduler is running
16:52:51 Starting web server on Slioch
16:52:51 Web server IP localhost, port 8999, Docs path: /usr/lib/Syncovery/WebDocs
16:52:51 Scheduler is running
16:52:51 To stop, enter q + Enter.
16:52:52 Scheduler is running.
16:52:52 Scheduled Jobs: 2. Time Zone: UTC+02:00. Next profile starts on 18.06.2026 at 16:57:51
Wrote /etc/SyncoveryCL.conf with workdir=/etc/.Syncovery and tempdir=/var/run/.syncoverytemp

So it's a problem during startup of the PC?

[tobias]

Hello,
yes, SELinux surely prevents it.

Even if you can't see it in the logs.

Maybe you can create a startup script or similar.

I will also make tests on Fedora soon, I haven't used it in a long time.

[CDR224]

To me, it looks like the starts but then immediately exits. It doesn't seem to fail:

Code: Select all

sudo systemctl status syncoverycl
● syncoverycl.service - Syncovery Scheduler Service
     Loaded: loaded (/etc/systemd/system/syncoverycl.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (exited) since Thu 2026-06-18 17:04:16 CEST; 23min ago
 Invocation: 120df0ce5da04ef482e798a73fb55202
       Docs: https://www.syncovery.com/download/linux/
    Process: 8721 ExecStart=/usr/lib/Syncovery/SyncoveryCL start (code=exited, status=0/SUCCESS)
   Mem peak: 38.4M
        CPU: 8.924s

See: Process: 8721 ExecStart=/usr/lib/Syncovery/SyncoveryCL start (code=exited, status=0/SUCCESS)

I'll have to find out how to set an exception in SELinux. Shouldn't the installer do that?

[tobias]

It might fail because it cannot open port 8999.

But that should be in WebGUI.log really.

I don't have more information right now, but I will make tests on Fedora soon. I hope I can make the installer add the exception.

[CDR224]

Thank you!
Meanwhile, if you already have the syntax to create the exception, I'd love to see it.
Otherwise, I'll see if I can somehow start the service on login. It doesn't need to be running when I'm not logged in.