aMule Forum
English => Distro-Specific Packages => Packages for older versions => Topic started by: jman on June 15, 2008, 01:50:33 AM
-
Hello,
this is my first try with a Slackware package, so there may be issues, namely concerning the file "install/slack-
require" which I copied and pasted from another (recent) slack amule package and changed the gcc/gcc-g++
requirements
Here it is for you brave:
ed2k://|file|aMule-2.2.1.tgz|44197878|28256176B0345D2F8DC7E69286D58B24|/
Please reply with comments &| usage reports.
jman
UPDATE: retired from sharing to some weirdnesses (sorry)
UPDATE2: stripped down bin/*, now the package shrinked from 42Mb to ~6mb ;-)
NEW LINK; ed2k://|file|aMule-2.2.1.tgz|6664842|A00F94B0EEAD97BE589D4AA66D633140|/
UPDATE3: webserver compiled-in
ed2k://|file|aMule-2.2.1.tgz|7704468|445399B7ED800DFDAD699C9D7C036948|/
-
I can't get anything at your new link, and I can't (by searching) find a file named amule-2.2.1.tgz. ???
UPDATE: It's now downloading. Thanks!
-
Hello,
My client went off the server and didn't reconnect to any other while I was away, probably that was the reason.
Now I reconnected and performed a global search: the file (with correct hash) is found.
You can try from now on.
Sorry for the problem, let me know if it works.
jman
-
I downloaded and installed it, and it works. :) Thanks!
Comments:
1. You have to install GeoIP. There's a script to build GeoIP at slackbuilds.org.
2. The compilation doesn't include the webserver.
-
Hi,
thanks for your feedback!
I've built a new package based on your suggestions:
ed2k://|file|aMule-2.2.1.tgz|7704468|445399B7ED800DFDAD699C9D7C036948|/
* web server included (that was my fault...)
* built against a prepackaged version of GeoIP 1.4.4 (I had installed it from src in the first place). The package I used can be found here:
http://www.slacky.eu/index.php?option=com_content&task=view&id=7255&Itemid=65
bye,
jman
-
I downloaded and installed the latest version, and the webserver indeed works properly.
Remaining issues:
1. UPnP doesn't work, apparently because my Slackware 12.1 installation (which is generally complete, except for KDE) is missing some libraries. From the aMule log:
2008-06-15 15:18:05: UPnP.cpp(87): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen libixml.so.2. Check PATH and LD_LIBRARY_PATH.
2008-06-15 15:18:05: UPnP.cpp(87): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen libupnp.so.2. Check PATH and LD_LIBRARY_PATH.
2008-06-15 15:18:05: UPnP.cpp(87): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen libupnp.so.3. Check PATH and LD_LIBRARY_PATH.
2008-06-15 15:18:05: UPnP.cpp(228): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen one or more UPnP component libraries. Check PATH and LD_LIBRARY_PATH.
2008-06-15 15:18:05: amule.cpp(1018): CUPnPException: error(CDynamicLibHandle): Unable to dlopen one or more UPnP component libraries. Check PATH and LD_LIBRARY_PATH.
2. For some reason ED2K won't connect. That's not such a catastrophe for me because I normally just use Kad, which connects OK. I think it connected the first time I ran the previous package you put up, but not thereafter. Maybe it's a transitory thing caused by who knows what. FWIW the log says:
2008-06-15 15:18:05: ServerList.cpp(83): Loading server.met file: /home/jbk/.aMule/server.met
2008-06-15 15:18:06: ServerList.cpp(168): 25 servers in server.met found
2008-06-15 15:18:06: ServerList.cpp(830): Start downloading server list from http://www.gruk.org/server.met.gz
2008-06-15 15:18:06: DownloadQueue.cpp(174): No part files found
2008-06-15 15:18:06: SharedFileList.cpp(352): Found 236 known shared files
2008-06-15 15:18:06: amule.cpp(801): Connecting
2008-06-15 15:18:06: ServerConnect.cpp(111): No valid servers to which to connect found in server list
Dunno why all the servers have suddenly decided to be invalid. That's if I'm right it connected last time.
-
Hi!
Those seems to be not related to the aMule build, I'll try to give you some hint:
1) libxml2 not found, check if you have a description file in "/var/log/packages" named libxml2-something. If (my guess) you're missing the library, download it from:
http://packages.slackware.it/package.php?q=current/libxml2-2.6.31-i486-2
install it, run (as root) "ldconfig -v | grep -i xml" and see if now it's correctly available to your apps (restart the aMule client).
2) Probably the file server.met is fsck'd up. Shut down aMule, delete the file (it is located in ~/.aMule/), restart the client and let it fetch the list. The link that is provided by default works indeed.
hth,
jman
-
Thanks for all the help! (I hope it's helpful to other Slackware users.)
ED2K is connecting again. And I do have libxml2-2.6.31. The oddity is that the aMule log says "Unable to dlopen libixml.so.2" and what I have on my Slack installation is libxml2.so.2, which is a different filename. From Google it appears that libxml and libixml are different, and libixml isn't part of any package normally used with Slackware.
-
Hi!
You're right, I didn't notice that 'i' in the middle of the name :-)
And again, I noticed I had installed libupnp (providing the libixml!) from srcs in past.
You can download the official Slack pkg from here:
http://repository.slacky.eu/slackware-12.1/libraries/libupnp/1.6.6/
good luck, you're almost there :-)
jman
-
It's getting very close. I also had to run sudo ln -s /usr/lib/libupnp.so.3.0.5 /usr/lib/libupnp.so.2, because aMule was looking for the latter file and it wasn't in the package you mention. The final problem is that I get
UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.
I'd imagine that's a router configuration issue but am busy and will worry about it later.
Thanks again for all the help!
-
Hello,
Glad to help, I'm learning too a lot of interesting things :)
I'd probably encounter the same error if I used the uPnP feature.
Right or wrong, it is disabled in my config because I use a static TCP/UDP forwarding setup in the router. I'm not very much into the client configuration, but I think that's a feature to be used instead of the static forwarding (in case one cannot get a High ID the "usual" way).
Googling around (with links to this forum too) I see that different versions of libupnp have different (erratic) behaviours, so YMMV...
jman
-
Someone could update the wiki information about the compilation of aMule (and if you want rpm packaging) in the latest versions of Slackware? With that information is the latest version would be a great contribution
Here wiki page:
http://www.amule.org/wiki/index.php/HowTo_Compile_In_Slackware
You can get help of these old pages:
http://www.amule.org/wiki/index.php/HowTo_Compile_In_Slackware
-
Someone could update the wiki information about the compilation of aMule (and if you want rpm packaging) in the latest versions of Slackware? With that information is the latest version would be a great contribution
Hello, I checked that page a few days ago, those details are still valid, more or less.
Probably it should be slightly updated to eliminate that "more or less" ;)
I'll check that out, maybe I'll just add a section, instead of modifying the existing content.
jman
-
jman, feel free to change/update article on the wiki
-
You can savely remove all info about <2.2.1. It was just the old version why I've set this marker. I you update it to 2.2.1 and svn, and maybe a recent version of the distro, I can start the translation.
-
You can savely remove all info about <2.2.1. It was just the old version why I've set this marker. I you update it to 2.2.1 and svn, and maybe a recent version of the distro, I can start the translation.
Ok, so I'll cut everything I think is not needed anymore and - upon approval of the new page - I can also provide Italian and (maybe) French translation.
jman
-
You can savely remove all info about <2.2.1. It was just the old version why I've set this marker. I you update it to 2.2.1 and svn, and maybe a recent version of the distro, I can start the translation.
Hello,
I think I'm done. Please check the new page at your convenience, so we can start with translations.
Thanks!
bye,
jman
-
I have added the Italian and French translation.
Now please someone update the main wiki page to notify their existence.
Thanks,
jman
-
The final problem is that I get
UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.
I need info on this problem to fix it. If someone is able to provide me the UPnP logs (enable it in preferences) and the libupnp debug logs (must compile it by hand and provide the files IUpnpErrFile.txt and IUpnpInfoFile.txt that are generated at the directory where aMule is run), I would be glad.
Cheers!
-
I need info on this problem to fix it. If someone is able to provide me the UPnP logs (enable it in preferences) and the libupnp debug logs (must compile it by hand and provide the files IUpnpErrFile.txt and IUpnpInfoFile.txt that are generated at the directory where aMule is run), I would be glad.
Hello,
I'll try to shed some light on the issue. The upnp package I've used (downloaded and
compiled with debug msgs) is 1.6.6 from upnp.sf.net.
Then I've recompiled aMule 2.2.1 with upnp support and enabling debug. Performing an
"ldd" on aMule binaries libupnp does not appear (don't know why but probably it is not
an issue).
On startup here it appears the messages hruotland mentioned:
2008-07-08 20:42:53: UPnP.cpp(87): Universal Plug and Play: error(CDynamicLibHandle): Unable to dlopen libupnp.so.2. Check PATH and LD_LIBRARY_PATH.
2008-07-08 20:42:53: UPnP.cpp(91): Universal Plug and Play: Successfully opened libupnp.so.3.
2008-07-08 20:42:53: UPnP.cpp(1063): Universal Plug and Play: bound to 10.0.0.254:49152.
2008-07-08 20:42:53: UPnP.cpp(1134): Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.
Apparently aMule at first is looking for the libupnp .so file belonging to a 1.4.x version
(libupnp.so.2), then correctly detects the installed version (libupnp.so.3 belonging to
libupnp 1.6.x).
I'll attach the file "IUpnpInfoFile.txt" as per your request. The file "IUpnpErrFile.txt"
is created but not populated (sticks to zero bytes).
I've noticed that on file upnp/src/genlib/miniserver/miniserver.c of libupnp srcs there's
such a statement:
#define APPLICATION_LISTENING_PORT 49152
this may be the reason why he's using that port in the first place. Opening the port on
the router doesn't change the erratic behaviour. I didn't find any trace of the other port
(60776), so maybe the choice is based on another logic.
Is it possible that some code in UPnp.cpp should be changed for newer libupnp?
This is as far as I can go :-), hope all this helps
Thanks for your help.
Jman
-
Hi jman,
Could you please try with tomorrow svn tarball? I hope this problem has been fixed.
In fact, I needed the full log to understand what is going on. You must enable it on Preferences->Debug.
Cheers!
-
In fact, I needed the full log to understand what is going on. You must enable it on Preferences->Debug.
Hello,
I've just compiled and installed aMule from tarball aMule-CVS-20080711.tar.bz2
I've activated verbose debugging and selected the "Universal Plug And Play" tick.
The error concerning the old library (libupnp.so.2) has disappeared (cool), but the UPnP discovery still times out:
2008-07-11 19:59:55: UPnPBase.cpp(866): Universal Plug and Play: bound to a.b.c.d:49152.
2008-07-11 19:59:55: UPnPBase.cpp(1238): Universal Plug and Play: UPNP_DISCOVERY_SEARCH_TIMEOUT.
2008-07-11 19:59:55: UPnPBase.cpp(937): Universal Plug and Play: UPnP Error: CUPnPControlPoint::AddPortMapping: Wan Service not detected.
In case something's wrong with my router forwarding policy, here's a recap:
- TCP+UDP on port 49152 (mentioned in the above code and automatically chosen by aMule)
- Standard TCP port
- UDP for extended server requests (i.e. Standard TCP port +3)
- UDP for UPnP
Attached IUpnpInfoFile.txt debug file.
Hope this helps!
Please let me know if I can provide further info, thanks for your time!
jman
-
Hi jman,
Thanks for the IUpnpInfoFile.txt, I appreciate your effort of compiling libupnp in debug mode.
But I still need the upnp debug aMule log. You need to enable debugging UPnP messages in preferences.
Cheers!
-
But I still need the upnp debug aMule log. You need to enable debugging UPnP messages in preferences.
Hi,
I'm sorry for wasting your time with unhelpful posts, but I see no specific upnp log file. I only see the libpunp txt files and a "logfile" in my home (which relevant lines I quotes in my posts), I've also checked the /proc/$PID/fd directory to be sure I was not missing something.
I didn't find anything relevant to debug messages in the prefs of aMule, other the one that you suggested, nor at compile time.
I'll attach this logfile aMule writes, hoping this is what you mean, otherwise please be patient with me ^_^ and explain what I'm doing wrong, thanks!
jman
-
jman,
Nevermind about unhelpfull posts, you are trying to help and I appreciate that.
Please, open aMule, go to Preferences, then click on "Debugging", make sure that "Enable Verbose Debug-Logging" is checked, and check "Universal Plug And Play" in the "Message Categories" box.
Then exit aMule and start it again. The file I need is exactly the file you have sent me, but now it will have the necessary debug messages.
Cheers!
-
The file I need is exactly the file you have sent me, but now it will have the necessary debug messages.
Ok, then I confirm the logfile attached in my latest post has been generated following your instructions (enable uPnP, enable verbose debugging and tick "Universal Plug and Play"), I just cannot get upnp to be more verbose, though.
jman
-
Well, in this case, no device in your local network has answered the broadcast from the upnp library. That means that you have either one or both of the following conditions:
1 - Your router has its upnp feature disabled or does not have it at all. Check the router's documentation. There should be a web interface where you can control all of its features, then check for UPnP ability.
2 - You have a firewall blocking UPnP messages. Make sure you have opened the following ports:
tcp destination 50000 - The UPnP port that is specified in your aMule general preferences, it could be a different number, please check there.
udp destination 1900 - The libUPnP port
udp source 1900 - Also libUPnP, if you enable this, things get faster.
Cheers!
-
1 - Your router has its upnp feature disabled
*cough cough* /me blushes
Well, it turns out that it worked.
In order to earn the community's forgiveness, I'll update the aMule wiki page about UPnP, that still recommends libupnp 1.4.x :)
Thanks again for your effort (and your patience!)
jman
-
lol :D
Thank you for your effort to put things to work, and your collaboration on the wiki is very much appreciated!
Cheers!