Deluge not starting anymore, Ubuntu 8.10

[qwerty]

I've been using deluge 1.10 for about a week now after installing the Ubuntu package for 32 bit from this site. All of a sudden, when I try to start deluge, system monitor shows it using up about 20-25% of my processor forever, and nothing ever happens.

After doing some reading on this site and looking through several threads, I've tried uninstalling and then installing deluge again, which didn't work. Then after some more reading, I deleted my .config/deluge folder, and then tried this:

Code: Select all

qwerty@Jerb:~/.config$ deluged -d
qwerty@Jerb:~/.config$ deluge
1.1.0
Killed
qwerty@Jerb:~/.config$ 

The "1.1.0" gets printed to the console, and then the damned thing sits there using 20-25% of my processor and nothing happens.

Please please please help me, I hate how azureus, or "vuze fancy gui piece of crap" looks and works and I want to stick with deluge.

[danii]

run deluged with logging enabled

Code: Select all

deluged -d -L debug

then paste ~/.config/deluge/deluged.log content here it should have some clues to you problem's origin

[qwerty]

Code: Select all

qwerty@Jerb:~$ deluged -d -L debug
[INFO    ] 16:49:30 daemon:36 Deluge daemon 1.1.0
[DEBUG   ] 16:49:30 daemon:37 options: {'loglevel': 'debug', 'quiet': False, 'logfile': None, 'config': None, 'port': None, 'pidfile': None, 'donot': True}
[DEBUG   ] 16:49:30 daemon:38 args: []
[DEBUG   ] 16:49:31 core:79 Core init..
[DEBUG   ] 16:49:31 component:94 Registered Core with ComponentRegistry..
[DEBUG   ] 16:49:31 component:94 Registered PreferencesManager with ComponentRegistry..
[DEBUG   ] 16:49:31 configmanager:79 Getting config 'core.conf'
[WARNING ] 16:49:31 config:242 Unable to load config file: /home/qwerty/.config/deluge/core.conf
[DEBUG   ] 16:49:31 config:244 Config /home/qwerty/.config/deluge/core.conf loaded: {'info_sent': 0.0, 'lsd': True, 'max_download_speed': -1.0, 'send_info': False, 'torrentfiles_location': '/home/qwerty', 'state_location': '/home/qwerty/.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/qwerty/.config/deluge/plugins', 'download_location': '/home/qwerty', '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/qwerty', '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': True, 'enc_out_policy': 1, 'seed_time_ratio_limit': 7.0, 'remove_seed_at_ratio': False, 'autoadd_location': '/home/qwerty', 'max_upload_slots_global': 4, 'config_location': '/home/qwerty/.config/deluge', 'seed_time_limit': 180, 'share_ratio_limit': 2.0, 'random_port': True}
[DEBUG   ] 16:49:31 configmanager:79 Getting config 'core.conf'
[INFO    ] 16:49:31 core:98 Starting XMLRPC server on port 58846
[INFO    ] 16:49:31 core:104 Daemon already running or port not available..

By the way, that command didn't generate a log file, but I figured you just needed the output, so that was from a console.

[johnnyg]

are you already running another deluged?
do a

Code: Select all

killall deluged

before running deluged with debug on.

[qwerty]

I've tried that but it says "no process killed"

Could it have something to do with "[INFO ] 16:49:31 core:104 Daemon already running or port not available.."?

[johnnyg]

I've tried that but it says "no process killed"

Could it have something to do with "[INFO ] 16:49:31 core:104 Daemon already running or port not available.."?

yes, it means something is using that port.
change the port under Preferences->Daemon.

[qwerty]

Deluge won't start, so how would I get into preferences?

[johnnyg]

Deluge won't start, so how would I get into preferences?

haha good point.
when deluged isn't running, open up

Code: Select all

~/.config/deluge/core.conf

and find this section (lines 31-33 for me)

Code: Select all

sS'daemon_port'
p13
I58846 

and change 58846 to something else.
then try running deluge.

[qwerty]

Um ok, I didn't have a core.conf file in /home/qwerty/.config/deluge, so I made one and specified a different port, and it didn't work, deluge didn't seem to notice the file I created.

I uninstalled 1.1.1, and installed version 0.5.9.3-1 from synaptic, and that works, but it's old

So what could be the difference between the two versions that causes deluge to not start? I used to have 1.1.0 working just fine and then without me messing with deluge, it stopped working.

Is there a dependency that likely got messed up that I should try reinstalling?

[johnnyg]

Either it didn't install properly or you have another service using port 58846.
You can't create a core.conf as it's a pickled file, so your best bet it to work out what's using the default port.