Deluge doesn't start on debian/enlightenment

[eromog]

Hi, i'm currently using deluge 1.1.9 on a debian squeeze with the e17 (enlightenment) environment. But deluge doesn't start if i click on his icon. With the command line, it shows me only the version of deluge and wait... So if anyone has an idea of the solution for this trouble, i'll be very grateful

Code: Select all

$ deluge
1.1.9

[danii]

try running deluge with logging enabled to try and pinpoint the source of your problem check the FAQ http://dev.deluge-torrent.org/wiki/Faq# ... ingenabled

[eromog]

Thank you to take time to try to help me.

I try this method and this is what i get on command line :

Code: Select all

[INFO    ] 02:30:22 daemon:48 Deluge daemon 1.1.9
[DEBUG   ] 02:30:22 daemon:49 options: {'loglevel': 'debug', 'quiet': False, 'logfile': None, 'config': None, 'port': None, 'pidfile': None, 'donot': True}
[DEBUG   ] 02:30:22 daemon:50 args: []
[DEBUG   ] 02:30:23 core:91 Core init..
[DEBUG   ] 02:30:23 component:106 Registered Core with ComponentRegistry..
[DEBUG   ] 02:30:23 component:106 Registered PreferencesManager with ComponentRegistry..
[DEBUG   ] 02:30:23 configmanager:91 Getting config 'core.conf'
[WARNING ] 02:30:23 config:251 Unable to load config file: /home/mog/.config/deluge/core.conf
[DEBUG   ] 02:30:23 config:253 Config /home/mog/.config/deluge/core.conf loaded: {'info_sent': 0.0, 'lsd': True, 'max_download_speed': -1.0, 'send_info': False, 'torrentfiles_location': '/home/mog', 'state_location': '/home/mog/.config/deluge/state', 'stop_seed_at_ratio': False, 'max_active_limit': 8, 'enc_in_policy': 1, 'queue_new_to_top': False, 'ignore_limits_on_local_network': True, 'rate_limit_ip_overhead': True, 'peer_tos': '0x00', 'daemon_port': 58846, 'natpmp': True, 'autoadd_enable': False, 'upnp': True, 'utpex': True, 'max_download_speed_per_torrent': -1, 'max_active_seeding': 5, 'allow_remote': False, 'outgoing_ports': [0, 0], 'max_half_open_connections': 50, 'enabled_plugins': [], 'plugins_location': '/home/mog/.config/deluge/plugins', 'download_location': '/home/mog', 'compact_allocation': False, 'max_upload_speed': -1.0, 'max_connections_global': 200, 'enc_prefer_rc4': True, 'listen_ports': [6881, 6891], 'dht': True, 'move_completed_path': '/home/mog', 'stop_seed_ratio': 2.0, 'max_active_downloading': 3, 'prioritize_first_last_pieces': False, 'max_upload_speed_per_torrent': -1, 'auto_managed': True, 'enc_level': 2, 'copy_torrent_file': False, 'max_connections_per_second': 20, 'max_connections_per_torrent': -1, 'move_completed': False, 'proxies': {'peer': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}, 'web_seed': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}, 'tracker': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}, 'dht': {'username': '', 'password': '', 'hostname': '', 'type': 0, 'port': 8080}}, 'dont_count_slow_torrents': False, 'add_paused': False, 'random_outgoing_ports': True, 'max_upload_slots_per_torrent': -1, 'new_release_check': False, 'enc_out_policy': 1, 'seed_time_ratio_limit': 7.0, 'remove_seed_at_ratio': False, 'autoadd_location': '/home/mog', 'max_upload_slots_global': 4, 'config_location': '/home/mog/.config/deluge', 'seed_time_limit': 180, 'share_ratio_limit': 2.0, 'random_port': True}
[DEBUG   ] 02:30:23 configmanager:91 Getting config 'core.conf'
[INFO    ] 02:30:23 core:110 Starting XMLRPC server on port 58846
[INFO    ] 02:30:23 core:116 Daemon already running or port not available..

I think the two last lines are causes of problems, but i don't think they could make troubles to the UI. Plus, the 58446 port is open on my router.

[johnnyg]

That error is saying that another program is using that port (most likely another instance of deluged).
You shouldn't open port 58846 on your router as the outside world will be able to connect to your daemon (unless this is what you want).

To find out what program is running on 58846, run

Code: Select all

sudo fuser -n tcp 58846

it should print out something like:

Code: Select all

58846/tcp:            2328

where that second number (2328 in the above example) is the pid of the process running on that port.

you can then run (substituting 2328 for whatever fuser returned)

Code: Select all

ps 2328

to find out more info about what that process is.

EDIT: just read the original post.

I'd suggest doing the following:

1. Work out what the other program is that's running on port 58846
2. If it's another instance of deluged (which it most likely is) kill it, if it's not consider changing deluge's daemon port.
3. Double check that no instance of deluge is running by typing

   Code: Select all

   ps aux | grep deluge

4. Run deluge daemon with logging enabled:

   Code: Select all

   deluged -L debug -d

   or I prefer to do

   Code: Select all

   deluged -L debug -l deluge-daemon.log

   in one terminal
   and

   Code: Select all

   tail -f deluge-daemon.log

   in another
5. If you see any errors post them here otherwise it everything looks fine kill deluged.
6. Now run

   Code: Select all

   deluge -L debug

   (this will run the UI with debugging info)
7. Post the above

let us know how you go

[eromog]

I try the following command before and after trying to launch deluged:

Code: Select all

# fuser -n tcp 58846

It doesn't print anything.

I also try a netstat -tnlp to know what processes use tcp:

Code: Select all

# netstat -tnlp
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      2555/exim4      
tcp        0      0 0.0.0.0:901             0.0.0.0:*               LISTEN      2575/inetd      
tcp6       0      0 :::445                  :::*                    LISTEN      2591/smbd       
tcp6       0      0 ::1:6600                :::*                    LISTEN      2857/mpd        
tcp6       0      0 :::139                  :::*                    LISTEN      2591/smbd