aMule Forum
English => aMule crashes => Topic started by: JustAnotherUser on January 10, 2009, 01:03:18 AM
-
I want to use amuled on my linux pc and remotely control it with the GUI from windows
which works fine as it seems as long as my temp dir is empty
there are a lot of shared files and I also have the upload shown on the remote GUI
but if I have my imported downloads ( only 1474 ;) makes 4446 files in the temp dir ) from emule in the temp dir then
amule will just hang and amuled gives a segmentation fault.
For the importing of the old downloads I used the import feature and this also reseted all files to 0.0% :(
but I don't have the source files anymore so I can't try it again.
Now how do I get amuled to run with my imported downloads ???
-
1474 is overdoing things a bit. Are you saying eMule could handle that? On the same machine?
In theory it should work, at least with amule (which can also be controlled with amulegui), but not with amuled. If you have enough memory and unlimited filehandles, that is. Just use your old temp folder as temp folder, and it should use them automatically. Give it some time on startup, what you call "hang" is probably just the startup. If it really hangs, post the logfile.
-
1474 is overdoing things a bit. Are you saying eMule could handle that? On the same machine?
Yes eMule did a great job ;)
No, not on the same machine.
It was just an old P3 866 running win2003, a whole 160GB HDD for the temp dir, 384MB ram and eMule used at least 120MB of it but that was fine as this PC had nothing else to do.
And yes there where over 1400 files (plus shared files) but about 3/4 where paused/stopped and only some very active files the rest was rare stuff.
I controlled it remotely with VNC a bit laggy but possible with the mirage mirror driver.
Now I have a better one with AMD Sempron 64 LE 1150 and 4GB of ram.
There is also a mythbackend running on it.
In theory it should work, at least with amule (which can also be controlled with amulegui), but not with amuled. If you have enough memory and unlimited filehandles, that is.
Why not with amuled, don't they have the same code base? What is the limit and why?
It would be much better because I normally don't use this PC (only over VNC, there is no monitor connected) it is only for storage (file server), p2p and mythbackend therefore I don't need a GUI and using VNC is really slow I would prefer the remote gui.
I already had some problems with the file handles but that should be no problem anymore (I hope) and 4GB ram should be more than enough.
Just use your old temp folder as temp folder, and it should use them automatically. Give it some time on startup, what you call "hang" is probably just the startup. If it really hangs, post the logfile.
As I mentioned in my first post I managed to trash my old part files :( but the part.met files seem ok.
Now I managed to get all the files in amule I also restarted it but it had hashed some shared files on restart this took awhile (over 2h),
another restart after hashing all files only took ~90sec :).
On the Linux side it seems to run now but the remote gui does not work correctly with amule,
I started the remote GUI over 20 times and this is what I get.
it does
-show shared files (always)
-change priority on shared files but the changes are not reflected by the list a restart of the remote gui is needed
-freeze on statistics screen after some seconds and using 50% of CPU (thread lock up?) or sometime crashes
-incomplete download list or none at all (it did once start with all files)
-shows clients on queue or not
-shows up/down speed (does not update) or not show
-shows connected server in server list or not
-shows empty upload slots (more or less but count is wrong and no info at all) but mostly none at all
If the download list shows some files then the other infos are shown as well if the dl list is empty then the other infos are also not shown and
there are some of these "External Connection: invalid opcode received" with different codes in the log file but only sometimes not on every connection.
Also I don't know what to think of the directory preferences it shows the host file system not the remote one and the shared files also do not show any directory path at all.
-
Also I don't know what to think of the directory preferences it shows the host file system not the remote one and the shared files also do not show any directory path at all.
Yeah, that's yet unimplemented feature. And the errors you described above... well, that's why remote gui is still experimental ;)
-
Hopefully amuled can handle more files and the remote gui will work better in near future ;D
until then I have to stick with VNC and the resource eating amule (over 50% cpu).
-
Why not with amuled, don't they have the same code base? What is the limit and why?
Amuled is linked against wxBase so it can be built on embedded systems (like NAS). There are no wxSockets and Events available, so that part is implemented differently. And the result is a limitation of filehandles + sockets <= 1024 I believe.
Can you run amule instead of amuled ? It can also be connected to with the remote gui.
-
Amuled is linked against wxBase so it can be built on embedded systems (like NAS). There are no wxSockets and Events available, so that part is implemented differently. And the result is a limitation of filehandles + sockets <= 1024 I believe.
So amuled does open a fillehandle for every file even if it is not needed because no up- or download is running,
shouldn't it manage the filehandles dynamically and only open them when they are needed?
Then I can only have far less than 1024 downloads + shared files with amuled at the moment?
Can you run amule instead of amuled ? It can also be connected to with the remote gui.
Amule is running now but it has a very high cpu usage (over 50%) is there anything I can do about this?
I have already removed a lot of stopped files manually from the temp dir (I will re add them when some of the downloads are finished) now there are only 325 left but all are active and there are 811 shared files. Will I get problems with more shared files or only with a big download list or both? Amule becomes really slow with a lot of downloads.
The remote gui is not working correct with amule (I can connect but it does not load the infos or only a part of it) I have tested amuled with about 15 files and it seemed to work.
-
So amuled does open a fillehandle for every file even if it is not needed because no up- or download is running,
shouldn't it manage the filehandles dynamically and only open them when they are needed?
Then I can only have far less than 1024 downloads + shared files with amuled at the moment?
Each download takes a filehandle (shares don't). 1024 is quite a lot usually...
When wxWidgets 3.0 gets available we can probably remove the daemon's limitations.
Amule is running now but it has a very high cpu usage (over 50%) is there anything I can do about this?
Disabling progress bars might help a little.
Will I get problems with more shared files or only with a big download list or both?
It's mostly the downloads.
The remote gui is not working correct with amule (I can connect but it does not load the infos or only a part of it)
What is missing?
-
Each download takes a filehandle (shares don't). 1024 is quite a lot usually...
When wxWidgets 3.0 gets available we can probably remove the daemon's limitations.
Also paused/stopped ones?
For most users this should be enough but there are always exceptions.
With wxWidgets 3.0 you can compile amule also for embedded systems (I love wiki ;)) and you can handle things equally. Great :)
Disabling progress bars might help a little.
I already did that only the percentage remains.
What is missing?
I already mentioned the problems with the remote gui in my 2nd post but that was for the full file list now it's a bit different.
-server list is loaded and complete but the connected server is not bold in the list
-ed2k info shows status, ip, port and id
-status and port are correct
-ip and id are wrong
-amule log and server info are empty
-kad nodes are 0
-nodes stats are not shown
-kad info shows not connected but I have firewalled on amule
-searching seems not to work
-not showing any uploads or downloads atm
-also up/down rate is not shown only 0.0
-all categories are shown as (0/0)
-clients on queue are 0 (0)
-shared files are loaded sometimes but the list is not always complete
-the infos here seem complete except for the directory path which is always empty
-statistics are also shown here and seem ok
-statistics are freezing the remote gui mostly in an instant but not always can also crash sometimes
-preferences directories are from host not the remote ones
The remote gui does some things but mostly nothing at all, totally random.
The best working part of the remote gui is the shared files list.
I just tried amuled it started, hashed some files and is using even more cpu power :-\ (shouldn't it use far less?)
and the remote gui has the same problems here.
-
Paused/stopped ones too, because they are still shared.
Seems the remote gui works bad under such heavy load...
-
Each download takes a filehandle (shares don't).
Paused/stopped ones too, because they are still shared.
Paused/stopped files need a filehandle because they are shared but shared files do not and they are shared, too. ???
Well, this sounds illogical.
Seems the remote gui works bad under such heavy load...
Unfortunately
Is it normal that amule uses that much cpu time?
I just had a look with "top" and it goes up to 80% and is normally around 50% without hashing any files and that on a 2,5Ghz machine.
Currently I have about 3000 sources, 286 files in download and 858 shared ones.
-
Paused/stopped files need a filehandle because they are shared but shared files do not and they are shared, too. ???
Well, this sounds illogical.
Well, a download is a download, no matter if stopped or not. So it's treated like a download.
Is it normal that amule uses that much cpu time?
...
Currently I have about 3000 sources, 286 files in download and 858 shared ones.
With so many downloads, probably yes.