amuled stop responding without crash

[Raúl Soriano]

Binary package hint: amule

Description: Ubuntu 8.04
Release: 8.04

amule-daemon: 2.2.0~svn20080218-0ubuntu3

Once a download is completed, amule-daemon stops responding without crashing. A running and connected amulegui stops working, new amulegui can't connect.

The only way to recover the daemon is killing it.

Running amule-daemon inside gdb to try and get a backtrace, makes it to not fail on every download, but on the long run it happens too.

Since it doesn't crash, I don't know whether this backtrace is usefull, but once it has stoped working i've hit "control+c" on the gdb console, and done as said in wiki.ubuntu.com/Backtrace

[Raúl Soriano (gatoloko)]

gdb backtrace:

[Raúl Soriano (gatoloko)]

I've found that without the -d parameter (fully daemonize) it crashes less, like running it on gdb.

[Emilio Pozuelo Monfort (pochu)]

Raúl Soriano wrote:
> Once a download is completed, amule-daemon stops responding without
> crashing. A running and connected amulegui stops working, new amulegui
> can't connect.

Could you check if it responds to amuleweb? I wonder if this is an amulegui
issue rather than amuled.

Thanks

[Raúl Soriano (gatoloko)]

In my previous message I talked about "-d" parameter and that was a mistake, it's "-f" parameter. Sorry.

I don't usually use amuleweb, but i've tried activating it and can't get it working. I'll describe the checks i've done until now:

It seems to be running, but I can't connect. I check whether it's launched with amuled just after restarting it.

$ ps afx | grep amule
27190 pts/0 S+ 0:00 | \_ grep amule
27178 ? Ssl 0:01 /usr/bin/amuled -f
27183 ? S 0:00 \_ amuleweb --amule-config-file=/home/gollos/.aMule/amule.conf

When I open the web with a browser (http://ip:4711) it can't connect. After a while checking firewall, amule options, network and everything, I try again to recheck that it's still running and:

$ ps afx | grep amule
27261 pts/0 S+ 0:00 | \_ grep amule
27178 ? Ssl 0:13 /usr/bin/amuled -f

amuleweb has disappeared! So I try to launch it manually. If I launch it with the command shown by the first ps, it shows nothing:

$ amuleweb --amule-config-file=/home/gollos/.aMule/amule.conf
(the cursor is here, blinking)

And, as before, I can't connect. So I stop it with control+c and try to launch it without parameters and now it shows:

$ amuleweb
Esto es amuleweb SVN Mon Feb 18 07:02:15 CET 2008

Creando cliente...
¡Hecho! Conexión establecida con aMuleSVN

----------------------------------------
| Servidor web aMule |
----------------------------------------

Usa 'Help' para la lista de comandos

Servidor web: Iniciado

WSThread: Thread started
aMuleweb$ WSThread: created socket listening on :4711
(the cursor is here, blinking)

Now I can connect, but can't log in with the password I had configured in amule preferences, and under the login form is this text: "No password specified, login will not be allowed."

During all this test, amulegui has worked without changing it's behavior. Don't know what to do next.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Raúl Soriano (gatoloko)]

2008/12/14 Daniel T Chen <email address hidden>

> Is this symptom still reproducible in 8.10 or 9.04?

It isn't. This seem to be fixed in 8.10, at least in the current
amule-daemon package ( 2.2.2-1ubuntu1).

[etali (etali)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.