Deluge Forum

Hey guys.

I just updated from Deluge 1.1.9 to 1.2.0rc3 and I've run into an issue.

Some of my torrents will go for about 5 minutes and then get an error. It doesn't specify the error anywhere I can find, however I've looked at the logs and found this in /var/log/messages:

Nov 6 23:40:12 hostname kernel: [192567.900718] possible SYN flooding on port (port number). Sending cookies.

I'm not sure if its related, but its all i can find. It also doesn't look related because it happens almost exactly every minute.

I've looked for an error log for Deluge but it doesn't seem to log. I assume i need to put it into debug to get info but is there a way to retrieve what error is causing the torrent to stop?

EDIT: Sorry, running ubuntu 9.04 server headless. Plenty of drive space, chmoded the directories to 777, etc.

It seems to still be happening with any torrent at random. I've looked for logs or anything thati t could be and found nothing so far... anyone able to give me a hand? Thanks.

Upgraded to 2.0 RC4 and its still happening. Does anyone have any insight?

kill-9 wrote:Upgraded to 2.0 RC4 and its still happening. Does anyone have any insight?

What error is the torrent status reporting?

What file system are using?

This is a linux kernel failsafe...it's seeing a lot of request traffic and thinks that it's a possible DoS attack.

Here's a thread explaining it and how to turn it off if you so desire. Try turning it off then see if you still get errors. Also, sometimes if you kill Deluge then restart it while it's downloading it will error out on the torrent. A forced recheck fixes it for me.

EDIT:
If you're running headless I'm assuming you have a startup script. Just change the following if you're using an older script: If you have a newer script then change it from warning to debug Here's the latest script from the wiki

I put it in /home/user/.config/deluge/deluge.log and /home/user/.config/deluge/deluge_web.log

When you want to turn logging off just remove the "#" key from the top one to the bottom.
If you want the web client then it's "DAEMON2_ARGS" that you change.

Hope that helps

andar wrote:

kill-9 wrote:Upgraded to 2.0 RC4 and its still happening. Does anyone have any insight?

What error is the torrent status reporting?

What file system are using?

The torrent status is ok, and the file system is EXT4. I didn't think about that at the time actually, I might try an EXT3 drive.

Thanks!

mel wrote:This is a linux kernel failsafe...it's seeing a lot of request traffic and thinks that it's a possible DoS attack.

Here's a thread explaining it and how to turn it off if you so desire. Try turning it off then see if you still get errors. Also, sometimes if you kill Deluge then restart it while it's downloading it will error out on the torrent. A forced recheck fixes it for me.

EDIT:
If you're running headless I'm assuming you have a startup script. Just change the following if you're using an older script:

Code: Select all

#DAEMON1_ARGS="-d"
DAEMON1_ARGS="--loglevel=debug --logfile=<logfile_path> -d"
#DAEMON2_ARGS=""
DAEMON2_ARGS="--loglevel=debug --logfile=<logfile_path> -d"

If you have a newer script then change it from warning to debug

Code: Select all

DAEMON1_ARGS="-d -c /var/lib/deluge -l /var/log/deluged.log -L debug"
DAEMON2_ARGS="-p 9092 -c /var/lib/deluge -l /var/log/deluge-web.log -L debug"

Here's the latest script from the wiki

I put it in /home/user/.config/deluge/deluge.log and /home/user/.config/deluge/deluge_web.log

When you want to turn logging off just remove the "#" key from the top one to the bottom.
If you want the web client then it's "DAEMON2_ARGS" that you change.

Hope that helps

If this was a failsafe though, wouldn't I get a dmesg about it? It should be in SOME sort of log, but I scowered everything and found no mention of any threshhold being crossed. The kernel should at least give a warning about it, should it not?

EDIT: also, something that is strange is it happens no matter how many torrents I have, and usually to the same torrents.

For example, I had a torrent that I had to resume almost a hundred times. During the begining when I first had it I had plenty of torrents going along side it. By the end it was the only one left and it was still erroring. It also wasn't getting alot of traffic.

Seems the "Nov 6 23:40:12 hostname kernel: [192567.900718] possible SYN flooding on port (port number). Sending cookies." messages isn't related to the problems you're having. This wouldn't error out torrents unless of course you're seeing the message all the time but then your internet connection would likely be slow or dead

You're going to have to turn on debugging in Deluge then post the results to pin point the exact cause....my previous post explains how. It could be something as simple as the main tracker listed in the torrent isn't working anymore or it could be an IO issues with EXT4. Without logs it's a guessing game

I've been having this same problem ever since I had to reinstall Ubuntu and started using ext4. However, I found a workaround:

1)Copy .torrent to another folder
2)Remove corrupted torrent with data
3)Re-add torrent
4)Quickly right-click on the torrent that errored before and select Options -->Download Speed Limit --> Set Unlimited.

You might need to set the errored torrent to a lower priority so that it doesn't start right away. I couldn't find an option to not start torrents when Deluge starts.

I hope that helps!

Alright so i cranked the log level and found this when i got an error:

[DEBUG ] 23:53:34 alertmanager:115 file_error_alert: (snip) file (snip)) error: Input/output error
[DEBUG ] 23:53:34 alertmanager:115 tracker_announce_alert: (snip) (http://(snip)/announce) sending announce (stopped)
[DEBUG ] 23:53:34 alertmanager:115 torrent_paused_alert: (snip) paused
[DEBUG ] 23:53:34 torrentmanager:994 on_alert_file_error: (snip) file ((snip)) error: Input/output error

IO issues... think this is EXT4 related?

EDIT: Something even stranger, I'm now getting this: "error: No such file or directory". Of course the files are there