Ups, I was talking about peer-limit-global but I meant open-file-limit. peer-limit-global was set to 65535. When I set it to 240, it seems to work fine (even if my set of torrents couldn't reach 240 in summary, because they all have per-torrent peer limit).
Question #2: I had an incorrent listen ...
Search found 6 matches
- Sun Nov 11, 2012 4:05 pm
- Forum: General
- Topic: Couldn't create socket: Too many open files (fdlimit.c:683)
- Replies: 12
- Views: 15887
- Sat Nov 10, 2012 9:54 pm
- Forum: General
- Topic: Couldn't create socket: Too many open files (fdlimit.c:683)
- Replies: 12
- Views: 15887
Re: Couldn't create socket: Too many open files (fdlimit.c:6
I haven't changed the settings for ages, that's the weird thing... No installation nor upgrade of whatever.
peer-limit-global was always 128 in my conf and never had any trouble. After this started to happen I tried to increase it to 256 but it didn't help...
This transmission-daemon is actually ...
peer-limit-global was always 128 in my conf and never had any trouble. After this started to happen I tried to increase it to 256 but it didn't help...
This transmission-daemon is actually ...
- Sat Nov 10, 2012 9:47 am
- Forum: General
- Topic: Couldn't create socket: Too many open files (fdlimit.c:683)
- Replies: 12
- Views: 15887
Re: Couldn't create socket: Too many open files (fdlimit.c:6
Nothing special, still the same...
It's not the limit, there's no global limit for peers, only some torrents have their own limit for peers.
It's not the limit, there's no global limit for peers, only some torrents have their own limit for peers.
- Fri Nov 09, 2012 10:53 am
- Forum: General
- Topic: Couldn't create socket: Too many open files (fdlimit.c:683)
- Replies: 12
- Views: 15887
Re: Couldn't create socket: Too many open files (fdlimit.c:6
And one more thing: there's also lots of
in the log.
Code: Select all
Couldn't set source address 2001:0:5ef5:79fb:283c:ceb:a9b6:b86d on 991: Cannot assign requested address (net.c:269)
- Fri Nov 09, 2012 10:33 am
- Forum: General
- Topic: Couldn't create socket: Too many open files (fdlimit.c:683)
- Replies: 12
- Views: 15887
Couldn't create socket: Too many open files (fdlimit.c:683)
Hello,
I'm running transmission-daemon (2.72) on openwrt. In the past two days I started getting these messages in the log:
Couldn't create socket: Too many open files (fdlimit.c:683)
I've never had any problems with that, even if I was seeding much more torrents than I do now. The set of my ...
I'm running transmission-daemon (2.72) on openwrt. In the past two days I started getting these messages in the log:
Couldn't create socket: Too many open files (fdlimit.c:683)
I've never had any problems with that, even if I was seeding much more torrents than I do now. The set of my ...
- Fri Apr 15, 2011 10:04 am
- Forum: Support
- Topic: Trackerless torrents eat 100% CPU
- Replies: 0
- Views: 1249
Trackerless torrents eat 100% CPU
Hello,
I'm running transmission-daemon 2.12 (11412) on OpenWrt Backfire (10.03.1-rc4, r24045) on RouterStation. Works perfectly. Recently I started using trackerless torrents (via magnet links) and here came the problem: After several hours of a run of transmission-daemon (usually 24 hours or so ...
I'm running transmission-daemon 2.12 (11412) on OpenWrt Backfire (10.03.1-rc4, r24045) on RouterStation. Works perfectly. Recently I started using trackerless torrents (via magnet links) and here came the problem: After several hours of a run of transmission-daemon (usually 24 hours or so ...