I've been lookng kind of carefully at this for a few days. Here's a summary of what I've seen so far. Note that I start with a blank slate, no existing .aMule dir.
*) Periodically (no pattern I can see yet) there is nothing visible in the log or debug log (via the web). "WARNING: logfile is empty. Something wrong" Sometimes when you start it up it works, other times not... More often not. When it does work the last line often truncates in the middle, often with a garbage character. Buffer problem? (100% repeatable)
*) Settings in preferences (number of connections) appear to be ignored, or at least not saved. I adjust things by hand via .eMule. (100% repeatable)
*) server.met downloaded via the web interface seems not to work. When amuled starts up and I connect via amuleweb, I see a correct-looking list of servers, but status is "now connecting" and it never connects. stdout indicates repeated attempts to connect to "0.0.0.0 : 0". Very quickly if I click around, the web interface will stop responding. Once it's wedged, amuleweb starts spitting out socket errors. (recreated this twice)
*) If I rm the server.met file, everything is stable but with no servers. If I hand-enter a single server, everything works more or less OK for a while, which is what I've been doing. But very quickly a server appears in the server list: "0.0.0.0 : 0"; you can remove it but it always comes right back. (100% repeatable)
*) Eventually after 10-30 hours I'll check the web interface and see that dreaded "Now connecting" message. It never goes away. The web interface will be slow at that point and will eventually stop responding. (This has happened twice)
*) Weirdest thing of all. After running for some number of hours, I run top on the box, and see a load average of 3.0-5.0 and 75% user CPU, 25% sys. Meanwhile no processes actually in the list are showing up as taking any CPU time! By the summary the box looks swamped, but by the process list it looks idle! Crazy. Occasionally amuled blinks up to the top and the most it ever appears to use is 5% CPU. Meanwhile the system is brutally sluggish and obviously struggling.
That's crazy, watching linux bog down while not indicating what process is doing it, seeing the two stats disagree with each other. Never seen that before. Sure enough, on a hunch I kill amuled and instantly everything is normal again. (happened twice)
