I have just tried V0.4 and notice an oddity about it's operation (with the daemon or terminal mode).

After working for a while - several minutes to several hours - I get Zeros for the Horizon, for the Sockets, and for the bandwith. Also, any down/uploads in progress stop. Sometimes, it will restart after 15=>30 minutes. Sometimes not. When it refuses to start, I can shut it down, restart it and everything works fine - for a while - then the Zero stuff happens again.....

Any idea as to what could be happening???
How I could fix it to stay connected?

cheers,
johnd

Hi!

this is indeed odd. Looks like network thread get's blocked in some place... However, I think I know what it might be: if you are using mutella for a while you may have out of date host setvers in AutoConnectSrvX. Clean it up by setting them all to connect1.gnutellanet.com, connect2.gnutellanet.com and so on. Might help.

Let me know how it works.

--Max

Hmmmm. I suspected something like this, so made a script to run when things got weird. The script:
open connect1.bearshare.net
open connect1.gnutellanet.com
open gnet2.ath.cx
open gnutella.fileflash.com
open gnutella-again.hostscache.com
open ghutella.hostscache.com
open public.bearshare.net
open router.limewire.com

This seems to work sometimes, but fails at other times. I conclude that it a "don't care". Some odd observations:
1) The connect1=4.gnutellanet.com don't work for Mutella or gnotella (on a Windoze box). They *never* get me any other hosts or network horizon.
2) I run a SOHO network with all machines behind a Linux firewall/gateway - which does IP masquarade.
This has never presented a problem before. Other programs - including Gnotella & Limewire - work fine. (I'm behind it now.......)

Just this PM, Mutella "hung up" with zeros for everything. I shut it down, started Gnotella on my notebook, found a downloaded a small file....Weird.

You think that this info might help find the cause? I would *really* rather run the Mutella on my Linux box, rather than run gnotella - or other - on one of the ever so crashable Win boxes.....

I do appreciate your response.

cheers,
johnd

Excuse me for fowollowing up my own post, but I just got another clue that might bear on the Mutell behaviour. I was just running Mutella as a daemon & it "hung up" for several hours. When I looked at the process table, I saw that one of the "mutella" entries had a huge life span - almost two hours. When it is working correctly, these process entries seem to have short lives. I assume that they are restarted reguarly. If my guess is correct, some process may be hanging.

The Perl script starts seven "mutella" processes on my system and the "hanging" process # is either 3 or 4 after the process # of the Perl script.

Maybe that could shed some light?

cheers,
johnd

possibly. if you run mutella as daemon, use screen instead. readline library, a part of terminal UI expects a terminal, it cannot work with /dev/nul. if you do so user interface thread eats up 100% of cpu which is not a good thing at all... something like

screen -mdS mutella /usr/local/bin/mutella

should solve your problems I believe.

--Max

If it is the UI that causing the problem, how would that explain the intermittent nature of the
servent "going to sleep" and then going back to normal again later? Wouldn't the 100% CPU usage be a problem which persisted, once initiated?

I don't think that CPU horsepower is really the problem. As I said earlier, I also run Mutella in the terminal mode (direct, without Screen). This should be a low bandwidth User Interface. Less bandwidth than the daemon mode...?..

In order to be sure, I am now running Mutella in the daemon mode, and checking the CPU usage with the "top" utility. The summation of all my user processes - including the Mutella threads - has not exceeded 16%. (Most machines on my LAN network are mostly shut down, my CPU is fast and the Internet connection - handled by my Firewall machine - is via 56K modem).

Seems that I've got lots of horsepower to spare...



For a while, I thought that my Firewall machine might be messin' with me. But, I ran a copy of Shareaza on a windoze box for several days and the problem of the servent "going to sleep" never occurred. Gotta be either something in my Linux box and/or in Mutella..??...
Drat!

If Mutella would connect & up/download like Shareaza, I would be one heck of a happy camper!!!

cheers,
johnd