Linux: Still transferring data after shutdown deluge

General support for problems installing or using Deluge
Post Reply
mcourteaux

Linux: Still transferring data after shutdown deluge

Post by mcourteaux »

Hi,

After I exited Deluge (File -> Quit), the process deluge is gone. But there are still a lot of connections, transferring at a low speed.
All connections are running at PID (Process ID) 0 by root.
So, I can't kill it. I always was in trouble with my internet connection with a limit of 120 GB/month.
Then I figured it out it was deluge still transferring with a kind of hidden process. Nethogs shows what is going on:

Image

And here is my process list:

Code: Select all

  PID TTY          TIME CMD
    1 ?        00:00:00 init
    2 ?        00:00:00 kthreadd
    3 ?        00:00:00 ksoftirqd/0
    4 ?        00:00:00 migration/0
    5 ?        00:00:00 watchdog/0
    6 ?        00:00:00 migration/1
    7 ?        00:00:00 ksoftirqd/1
    8 ?        00:00:00 watchdog/1
    9 ?        00:00:01 events/0
   10 ?        00:00:00 events/1
   11 ?        00:00:00 cpuset
   12 ?        00:00:00 khelper
   13 ?        00:00:00 netns
   14 ?        00:00:00 async/mgr
   15 ?        00:00:00 pm
   17 ?        00:00:00 sync_supers
   18 ?        00:00:00 bdi-default
   19 ?        00:00:00 kintegrityd/0
   20 ?        00:00:00 kintegrityd/1
   21 ?        00:00:00 kblockd/0
   22 ?        00:00:00 kblockd/1
   23 ?        00:00:00 kacpid
   24 ?        00:00:00 kacpi_notify
   25 ?        00:00:00 kacpi_hotplug
   26 ?        00:00:00 ata_aux
   27 ?        00:00:00 ata_sff/0
   28 ?        00:00:00 ata_sff/1
   29 ?        00:00:00 khubd
   30 ?        00:00:00 kseriod
   31 ?        00:00:00 kmmcd
   32 ?        00:00:00 khungtaskd
   33 ?        00:00:00 kswapd0
   34 ?        00:00:00 ksmd
   35 ?        00:00:00 aio/0
   36 ?        00:00:00 aio/1
   37 ?        00:00:00 ecryptfs-kthrea
   38 ?        00:00:00 crypto/0
   39 ?        00:00:00 crypto/1
   53 ?        00:00:00 kstriped
   54 ?        00:00:00 kmpathd/0
   55 ?        00:00:00 kmpathd/1
   56 ?        00:00:00 kmpath_handlerd
   57 ?        00:00:00 ksnapd
   58 ?        00:00:02 kondemand/0
   59 ?        00:00:02 kondemand/1
   60 ?        00:00:00 kconservative/0
   61 ?        00:00:00 kconservative/1
  298 ?        00:00:00 scsi_eh_0
  299 ?        00:00:00 scsi_eh_1
  300 ?        00:00:00 scsi_eh_2
  301 ?        00:00:00 scsi_eh_3
  302 ?        00:00:00 scsi_eh_4
  303 ?        00:00:00 scsi_eh_5
  327 ?        00:00:00 v86d
  328 ?        00:00:00 cqueue
  375 ?        00:00:00 jbd2/sda5-8
  376 ?        00:00:00 ext4-dio-unwrit
  377 ?        00:00:00 ext4-dio-unwrit
  409 ?        00:00:00 flush-8:0
  437 ?        00:00:00 upstart-udev-br
  440 ?        00:00:00 udevd
  591 ?        00:00:00 udevd
  614 ?        00:00:00 udevd
  732 ?        00:00:00 kmemstick
  733 ?        00:00:00 kpsmoused
  764 ?        00:00:00 cfg80211
  798 ?        00:00:00 irq/23-lis3lv02
  806 ?        00:00:00 iwlagn
  841 ?        00:00:00 hd-audio0
  863 ?        00:00:01 phy0
 1002 ?        00:00:02 mount.ntfs
 1007 ?        00:00:00 mount.ntfs
 1026 ?        00:00:00 rsyslogd
 1041 ?        00:00:00 dbus-daemon
 1050 ?        00:00:00 NetworkManager
 1051 ?        00:00:00 avahi-daemon
 1052 ?        00:00:00 gdm-binary
 1053 ?        00:00:00 avahi-daemon
 1067 ?        00:00:00 modem-manager
 1097 ?        00:00:00 cupsd
 1120 ?        00:00:00 console-kit-dae
 1188 ?        00:00:00 gdm-simple-slav
 1190 tty4     00:00:00 getty
 1194 tty5     00:00:00 getty
 1204 tty2     00:00:00 getty
 1205 tty3     00:00:00 getty
 1209 tty6     00:00:00 getty
 1211 ?        00:00:00 acpid
 1226 ?        00:00:00 cron
 1227 ?        00:00:00 atd
 1257 ?        00:00:00 wpa_supplicant
 1258 tty7     00:04:22 Xorg
 1270 ?        00:00:00 hddtemp
 1448 tty1     00:00:00 getty
 1466 ?        00:00:00 dbus-launch
 1487 ?        00:00:00 gdm-session-wor
 1490 ?        00:00:00 upowerd
 1502 ?        00:00:00 rtkit-daemon
 1513 ?        00:00:00 polkitd
 1569 ?        00:00:00 gnome-screensav
 1600 ?        00:00:00 gnome-keyring-d
 1619 ?        00:00:00 gnome-session
 1649 ?        00:00:00 ssh-agent
 1652 ?        00:00:00 dbus-launch
 1653 ?        00:00:00 dbus-daemon
 1658 ?        00:00:03 gconfd-2
 1662 ?        00:00:00 gnome-power-man
 1664 ?        00:00:01 gnome-settings-
 1674 ?        00:00:00 gvfsd
 1679 ?        00:00:00 polkit-gnome-au
 1685 ?        00:00:02 nm-applet
 1686 ?        00:00:00 gvfs-fuse-daemo
 1687 ?        00:00:00 pulseaudio
 1692 ?        00:00:17 nautilus
 1693 ?        00:02:54 compiz
 1694 ?        00:00:07 gnome-panel
 1702 ?        00:00:00 bluetooth-apple
 1706 ?        00:00:00 gnome-screensav
 1732 ?        00:00:01 notify-osd
 1750 ?        00:00:00 gvfsd-trash
 1752 ?        00:00:00 bonobo-activati
 1755 ?        00:00:00 gconf-helper
 1771 ?        00:00:02 cpufreq-applet
 1773 ?        00:00:05 wnck-applet
 1774 ?        00:00:00 trashapplet
 1775 ?        00:00:00 gvfs-gdu-volume
 1776 ?        00:00:00 sh
 1777 ?        00:00:01 gtk-window-deco
 1779 ?        00:00:00 udisks-daemon
 1780 ?        00:00:00 udisks-daemon
 1783 ?        00:00:00 gvfs-afc-volume
 1787 ?        00:00:00 gvfs-gphoto2-vo
 1789 ?        00:00:01 syndaemon
 1801 ?        00:00:06 sensors-applet
 1802 ?        00:00:01 clock-applet
 1803 ?        00:00:00 notification-ar
 1804 ?        00:00:00 indicator-apple
 1805 ?        00:00:00 indicator-apple
 1806 ?        00:00:38 multiload-apple
 1807 ?        00:00:00 python
 1817 ?        00:00:00 gvfsd-metadata
 1818 ?        00:00:00 indicator-messa
 1821 ?        00:00:00 indicator-sound
 1823 ?        00:00:00 indicator-appli
 1830 ?        00:00:00 gvfsd-burn
 1833 ?        00:00:00 indicator-me-se
 1836 ?        00:00:00 indicator-sessi
 1903 ?        00:00:00 gdu-notificatio
 1920 ?        00:00:00 applet.py
 1926 ?        00:00:00 update-notifier
 1931 ?        00:00:00 system-service-
 1946 ?        00:00:47 eog
 2440 ?        00:03:21 nethogs
 2475 ?        00:00:00 firefox
 2479 ?        00:00:00 run-mozilla.sh
 2483 ?        00:00:57 firefox-bin
 2521 ?        00:00:00 sh
 2522 ?        00:00:07 gnome-terminal
 2525 ?        00:00:00 gnome-pty-helpe
 2526 pts/1    00:00:00 bash
 2545 pts/1    00:01:50 nethogs
 2620 ?        00:00:00 thunderbird
 2625 ?        00:00:00 run-mozilla.sh
 2629 ?        00:00:04 thunderbird-bin
 2791 pts/4    00:00:00 bash
 2810 pts/4    00:00:00 ps
So, how to stop this transferring?

Thanks
loki
Moderator
Moderator
Posts: 787
Joined: Tue Dec 04, 2007 3:27 pm
Location: MI, USA

Re: Linux: Still transferring data after shutdown deluge

Post by loki »

I imagine those are either requests to your machine for a piece of the torrent you were sharing or the very last updates or requests for updates from the tracker. Either of which do stop after very short time (it looks like) and use barely any bandwidth.
mcourteaux

Re: Linux: Still transferring data after shutdown deluge

Post by mcourteaux »

@loki: Thank you very much. That will be indeed the problem. So, the question is: "Does Deluge tell the tracker he stopped?"
Because, if I close Deluge, it is immediately gone. While, in Transmission (Linux) he first tells the tracker he will leave, which takes about ten seconds.
So, when a peer gets a new announcement from the tracker, he will stop trying to connect me?
nox
New User
New User
Posts: 3
Joined: Tue Dec 14, 2010 1:30 pm

Re: Linux: Still transferring data after shutdown deluge

Post by nox »

i'm trying it too right now.. closed deluge and it's been transferring for 20mins and goes on..

Image
Cas
Top Bloke
Top Bloke
Posts: 3679
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: Linux: Still transferring data after shutdown deluge

Post by Cas »

nox wrote:i'm trying it too right now.. closed deluge and it still transferring for 10mins..
This is stretching the definition of transferring, those data rates are minuscule so are probably just protocol request packets rather than any real data transfer.

You can use wireshark to sniff the packets.
Post Reply