Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi,
Really need some help here. I manage to make the mldonkey working by downloading and installing the simplified version that from shadowandy's web site and later replaced the "mlnet" with a full version. It works for about 2 weeks and then yesterday I find the mlnet core dead. Tried everything I can but could not get it run again.
Always get the error “nohup: appending to nohup.out” when trying to run "mlnet.sh" manually. The only way I can get it run again is to rename mldonkey directory and setup a new mldonkey directory and then reboot. Today I find the core is dead again. Checked mlnet.log but could not figure out what's wrong. It's pretty annoying if I have to keep remove mldonkey directory and reset as all the downloaded part are wasted. Any idea what could go wrong ?
Thanks
Francis
Offline
I had MLDonkey 2.9.2 "real simple" running for more than 100 days without any problem. Then I've upgraded to 2.9.5 full version and experienced the very same problem as you did. It was running for a while and then is crashed. None of the mlnet processes did exist anymore.
I've "downgraded" to 2.9.5 "real simple" as I actually need BT only. This version seems to be more stable although I have seen it crashing twice in about a month now.
I've already made ShadowAndy aware of this in his blog and he said he'll check for patches or if he had a compile issue with 2.9.5.
So, if you want to run a stable version I recommend 2.9.2 "real simple" although I had the impression that is was slower. When using 2.9.5 try the simplest version that will do for you. Check from time to time if it is still running.
I also thought of a shell script checking periodically (as hourly cron job) whether the mlnet process is alive and if it is not to restart the service. Unfortunately I don't have the Linux knowledge to write such a script. How to check if a process of a known name is still running in a script?
BTW, instead of copying the entire mldonkey directory you can try to delete all *.tmp files and the *.pid file from you mldonkey directory. After that you should be able to start it again by calling mlnet.sh.
Bernhard
Offline
Hi, Bernhard:
Thanks very much for your reply. Very helpful. I manage to make it run the way I mentioned in Andy's blog, i.e., rename mldonkey directory and run mlnet.sh. I will try delete *.tmp and *.pid files as you suggested which should be a lot faster.
I'm running 2.9.5 as you mentioned and since I used both BT and Emule, I upgraded to the "normal" version from the real simply one, which has both. Download speed is really impressive for BT. I may try 2.9.2 and see how it goes.
Regards
Francis
Offline
Update: I reversed to 2.9.3 "normal" version of mlnet and it appears that I have a lot less drop of connection. With 2.9.5, the drop happens every 2-3 hours which is very annoying. 2.9.2 has been running for about 5 hours no issue. Will see tomorrow morning.
I do noticed that the download speed with 2.9.3 has a pattern of spikes with ups and downs and alternate.
Offline
I'm too quick to make conclusion. Still have the same kind of drop using 2.9.3. When checking the mlnet.log, there is nothing unusual and the final few lines says "unknown BT client please report to ..." Does not sounds that this will crash mlnet.
I'm now running short of ideas. Is this a mldonkey problem or DNS-323 problem ? Does anyone else have similar situation ?
Thanks
Offline