You are not logged in.

#1 2022-02-20 02:45:26

amghwk
Member
Registered: 2020-05-23
Posts: 43

[Solved] Rslsync Not Working Anymore - Exit Code 127

Been using Resilio Sync without problems all these months on my HP Pavilion Gaming 15 laptop with KDE Desktop with my Arch.

Today I noticed that I couldn't access the rslsync webGUI.

Systemctl status shows the following output:

× rslsync.service - Resilio Sync service
     Loaded: loaded (/usr/lib/systemd/system/rslsync.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sun 2022-02-20 10:30:04 +08; 5min ago
   Main PID: 516 (code=exited, status=127)
        CPU: 1ms

Feb 20 10:30:04 pavilion systemd[1]: Started Resilio Sync service.
Feb 20 10:30:04 pavilion rslsync[516]: /usr/bin/rslsync: error while loading shared libraries: libcrypt.so.1:>
Feb 20 10:30:04 pavilion systemd[1]: rslsync.service: Main process exited, code=exited, status=127/n/a
Feb 20 10:30:04 pavilion systemd[1]: rslsync.service: Failed with result 'exit-code'.

I have checked if I have anything missing from libcrypt packages but all three were already installed.

Problem, is all these time, it was working normally.

Maybe one of the Arch updates messed it up. I didn't install anything new for the past few weeks on my Arch system.

Last edited by amghwk (2022-02-20 05:06:21)

Offline

#2 2022-02-20 02:47:28

loqs
Member
Registered: 2014-03-06
Posts: 18,983

Re: [Solved] Rslsync Not Working Anymore - Exit Code 127

Offline

#3 2022-02-20 04:43:58

amghwk
Member
Registered: 2020-05-23
Posts: 43

Re: [Solved] Rslsync Not Working Anymore - Exit Code 127

Still doesn't work. The libcrypt message is gone. But now...

× rslsync.service - Resilio Sync service
     Loaded: loaded (/usr/lib/systemd/system/rslsync.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sun 2022-02-20 12:38:21 +08; 5min ago
    Process: 518 ExecStart=/usr/bin/rslsync --nodaemon --config /etc/rslsync.conf (code=exited, status=1/FAIL>
   Main PID: 518 (code=exited, status=1/FAILURE)
        CPU: 6ms

Feb 20 12:38:21 pavilion systemd[1]: Started Resilio Sync service.
Feb 20 12:38:21 pavilion rslsync[518]: [20220220 12:38:21.867] Can't parse config file "/etc/rslsync.conf": ">
Feb 20 12:38:21 pavilion rslsync[518]: [20220220 12:38:21.867] Can't parse config file "/etc/rslsync.conf": ">
Feb 20 12:38:21 pavilion rslsync[518]: Error: config file "/etc/rslsync.conf" is emptyError: config file "/et>
Feb 20 12:38:21 pavilion systemd[1]: rslsync.service: Main process exited, code=exited, status=1/FAILURE
Feb 20 12:38:21 pavilion systemd[1]: rslsync.service: Failed with result 'exit-code'.

Problem is, why this all happening now? All this time it was working well.

I guess this is the problem with a rolling release. Anything can break after update I guess.

Last edited by amghwk (2022-02-20 04:47:01)

Offline

#4 2022-02-20 05:06:03

amghwk
Member
Registered: 2020-05-23
Posts: 43

Re: [Solved] Rslsync Not Working Anymore - Exit Code 127

Nevermind. I just uninstalled and reinstalled rslsync. Now it's working.

Offline

Board footer

Powered by FluxBB