Transmission v4.0.5-26: Too many open files error #5999
Comments
|
hey @flerbert12983, the logs would really help with this as it may be an upstream issue. To get the install and the service logs you can do the following:
|
|
@flerbert12983, additionally, based on a similarly reported issue upstream (transmission/transmission#5385), perhaps you can also gather the following output while you are connected via SSH to your NAS:
Once you have this output you can also attach to this ticket. |
|
Thanks, Michael! I have added the install log. I will update the service log once I start getting the errors again. They're not in the current long since I rebooted yesterday. Number of file descriptors linked to the /dev/urandom device: It does look like some kind of upstream Transmission issue, since something or the same happens on the Mac. |
|
@flerbert12983, appreciate you supplying the details. I've done a bit of cleanup to break the install log up into collapsable sections for readability. |
mreid-tt
changed the title
|
@flerbert12983, I've asked about this issue in the upstream ticket and it was suggested to check for a particular torrent scripts setting. While it does not seem to be the root cause of the issue, if you have the time, I'd like you to capture the output of this command: |
|
@mreid-tt As for the service log, there is a lot of personal information in there, too much to clean up and post. I'll give what I feel comfortable with: This error came repeatedly: Then hours later came this error: Eventually came errors like this: And couldn't save messages And eventually the The web interface not loading when I tried it, though it will load on later tries: Nothing here is jumping out at me as a root cause. It's just the error coming up for no clear reason after the app runs for a bit. I tried to mark this up in a more readable fashion than before. Sorry, my first github bug report. |
|
@flerbert12983, I appreciate your ongoing contributions to this matter. Your follow-up has been invaluable. While we haven't identified a definitive solution yet, I will persist in addressing this issue on the upstream ticket. Depending on your availability of free time, conducting an experiment to pinpoint when this issue originated could be beneficial. One approach is to downgrade to the earliest available version of Transmission v4. This can be achieved through two methods:
Alternatively, if you prefer a more cautious approach, you may opt for using a VirtualDSM. Here are the high-level steps:
By pursuing either option, you can hopefully determine whether the issue persists with Transmission v4.0.2 and assess the state of the logs and file descriptors for confirmation. |
|
Thanks. I downgraded to 4.0.2 I'll see how it goes. |
|
4.0.2 has been steady so far. No "too many open files" errors. |
|
Good to hear, what is the output of the file descriptors command from earlier? Also, in the service log besides the actual error (which shouldn't be there), you mentioned a warning which seemed to precede it, does this feature in your log at all? |
|
Can confirm that downgrade from 4.0.3 to 4.0.2 fixed this issue. Anyone tried the new release v4.0.5? I think one of commits here should be the cause: transmission/transmission@4.0.2...4.0.3 |
|
I have not tried 4.03 recently. I only ran into issues with 4.05 on Synology. I am, however, rock solid with 4.02 right now. |
To nail this down, I could create a package for each commit (or each day) between 4.0.2...4.0.3. Is there anyone willing to do the testing? |
|
As a first attempt I uploaded the previous versions 4.0.2 and 4.0.3 as they were removed from the Synocommunity repository (see https://synocommunity.com/package/transmission) These are not active because you need to manually download the SPK files anyway. |
Is this a new Bug?
Package Name
Transmission
Package Version
4.0.5-26 and previous 2 or 3 versions
Device Model
DS1821+
Device Architecture
x86_64
Firmware Version
DSM 7.2.1-69057 Update 3
What happened?
I get a bunch of errors like these:
Currently seeding 4000 files. It was working with more in earlier versions, but I cut back to see if it helped. It did not.
This is running on an encrypted share. Might that be the issue?
Reproduction steps
Install Log
install transmission 4.0.4-23
upgrade to transmission 4.0.4-24
upgrade to transmission 4.0.5-25
upgrade to transmission 4.0.5-26
Service Log
Other Logs
The text was updated successfully, but these errors were encountered: