F5F Stay Refreshed Software Operating Systems Service fails repeatedly with timing issues, restarting after short intervals despite working when active

Service fails repeatedly with timing issues, restarting after short intervals despite working when active

Service fails repeatedly with timing issues, restarting after short intervals despite working when active

I
Ikognito
Member
132
02-08-2023, 01:40 AM
#1
I have a Raspberry Pi 5 with 8GB RAM and Raspberry Pi OS. The problem I'm facing is that qbittorrent-nox, which I installed via apt, frequently crashes after about an hour and a half. My automation script triggers it automatically, but it restarts quickly—around three seconds—but these interruptions hurt seeding and downloading. I checked the logs and saw a systemd service timeout warning. Apparently, when I tried to run qbittorrent-nox manually, it worked without restarting. The logs and service file are available before. I followed standard setup but didn’t make many changes and still don’t fully understand what’s going on. Please help.
I
Ikognito
02-08-2023, 01:40 AM #1

I have a Raspberry Pi 5 with 8GB RAM and Raspberry Pi OS. The problem I'm facing is that qbittorrent-nox, which I installed via apt, frequently crashes after about an hour and a half. My automation script triggers it automatically, but it restarts quickly—around three seconds—but these interruptions hurt seeding and downloading. I checked the logs and saw a systemd service timeout warning. Apparently, when I tried to run qbittorrent-nox manually, it worked without restarting. The logs and service file are available before. I followed standard setup but didn’t make many changes and still don’t fully understand what’s going on. Please help.

I
ImKsaKhaled
Member
70
02-08-2023, 08:59 AM
#2
Check if your system is at full capacity and see if a fresh install helps.
I
ImKsaKhaled
02-08-2023, 08:59 AM #2

Check if your system is at full capacity and see if a fresh install helps.

U
Unmute_
Junior Member
39
02-08-2023, 06:32 PM
#3
The logs indicate a locking issue with the file, not high resource usage.
U
Unmute_
02-08-2023, 06:32 PM #3

The logs indicate a locking issue with the file, not high resource usage.

J
james26665
Senior Member
537
02-08-2023, 07:21 PM
#4
The instructions you're using come from a recommended setup for Raspberry Pi. Guides suggest configuring an umask and launching qbittorrent-nox with the -d flag as a daemon. Ensure you create the user and group qbit via the provided link.
J
james26665
02-08-2023, 07:21 PM #4

The instructions you're using come from a recommended setup for Raspberry Pi. Guides suggest configuring an umask and launching qbittorrent-nox with the -d flag as a daemon. Ensure you create the user and group qbit via the provided link.

S
StrangeAlexis
Junior Member
7
02-10-2023, 12:00 PM
#5
I'm not sure anymore, but it functioned properly. I also noticed the error on Dec 16 at 03:01:30 related to raspberrypi qbittorrent-nox.
S
StrangeAlexis
02-10-2023, 12:00 PM #5

I'm not sure anymore, but it functioned properly. I also noticed the error on Dec 16 at 03:01:30 related to raspberrypi qbittorrent-nox.

X
Xytrixz
Senior Member
552
02-11-2023, 08:32 PM
#6
The locked file may occur when several processes attempt access simultaneously, causing one to close. It can sometimes be fixed by reinstalling, applying a patch, or following Linux-specific installation steps. This command checks core dumps for references to qbittorrent: coredumpctl list | grep qbittorrent. A relevant discussion exists on the forum, though it's an older thread. The solution likely involves a specific method to resolve the issue.
X
Xytrixz
02-11-2023, 08:32 PM #6

The locked file may occur when several processes attempt access simultaneously, causing one to close. It can sometimes be fixed by reinstalling, applying a patch, or following Linux-specific installation steps. This command checks core dumps for references to qbittorrent: coredumpctl list | grep qbittorrent. A relevant discussion exists on the forum, though it's an older thread. The solution likely involves a specific method to resolve the issue.

S
sacapatates
Posting Freak
843
02-12-2023, 05:09 AM
#7
The problem stemmed from a configuration file that wasn't a new file, but one that didn't use the "forking" format, causing it to fail
S
sacapatates
02-12-2023, 05:09 AM #7

The problem stemmed from a configuration file that wasn't a new file, but one that didn't use the "forking" format, causing it to fail

P
phizphi
Junior Member
18
02-12-2023, 08:43 AM
#8
Logical approach, no extra processes spawning from the main one. Appreciate the success!
P
phizphi
02-12-2023, 08:43 AM #8

Logical approach, no extra processes spawning from the main one. Appreciate the success!