Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[redsnake]

Getting various problems when trying to compile amuled 2.3.1 on a CENTOS6.7 system.
Current problem is that when I compile for shared libs, i get an errormessage when I start aMule, that wx libs are incompatible.
THen I tried to compile with static libs, it refuses to configure, it say that alib is missing, although both runtime and devel is installed.
Tried to compile a static zlib-lib, and passing the location to configure, but still not working.
WHen i install the pre-compiled version it seems to stop working after a few minutes, aMuleGUI cannot connect, (it can if I try within a few minutes after amuled is started, but not subsequently)
Now I am getting an error message from aMuleGUI that it uses incorrect protocoll

[GonoszTopi]

It would be a great help in resolving this problem if you could post the error message you get, the configure flags you use, the result of configure run and the list of wx* packages installed. Later I might ask for more...

[HKM]

redsnake as Topi stated you should have provided more details regarding specific errors you encountered while compiling. If we could see it then it would be helpful to resolve the issue. Since you didn't ill post the complete absolute guide for you just follow it and you will be able to deploy aMuleD.

---
Since you have stated you using CentOS6.7 but didn't say if i86/x64 branch ill provide you with both. So download all the packages you require from the links below and place them in /root and complete these steps.

32bit: https://www.mediafire.com/folder/odh5t6vjc2ru1/EL6-i686
64bit: https://www.mediafire.com/folder/kicg8ctrddsn4/EL6-x86_64

1) su
2) cd /root
3) yum install epel-release
4) yum localinstall *aMule*.rpm
5) service amuled start

Now ill assume you understand how to fully setup amule. If not post back here ill walk you though the steps needed to setup IPTables rules, amule.conf, ect.
---

[redsnake]

Ok, sorry, I was/am so frustrated.
System is
CentOS Linux 6.7
Linux 2.6.32-573.26.1.el6.x86_64 on x86_64
wxGTK is 2.8.12-1.el6.rf

Ok, downloaded and installed, however there seems to be the same problem as all the other rpm's I've tested.
They seems to die after 5 minutes.
5 minutes after that that amuled is started there is, i cannot connect to it with aMule-GUI nor AMuleWb or amulecmd, download seems to work, albeit very slow.
daemon is running with 0,5% cpu-load and the webserver with 0%.

Regarding error messages wwhen compiling, it seems that I cannot get the ./configure script to accept the location of wx nor zlib (zlib is wrong version) and wx is compiled with no large files support, those are the libs installed by the packet manager when resolving the libs when installing amule.

Other problems I have is that amuleGUI is claiming that the wrong protocoll is used from time to time.
AmuleGUI is running on a W10-64-Pro box, and is installed from the current windowsinstaller at sourceforge.

[redsnake]

zlib 1.2.8 compiled and installed, et least the files are there.
wxGTK-2.8-12 compiled and installed
[root@seedbox aMule-2.3.1]# ./configure --disable-monolithic --with-toolkit=base --enable-amule-daemon --enable-amulecmd --enable-webserver  --enable-static --with-zlib=/usr/lib64
Gives
checking for zlib >= 1.1.4... no
configure: error: zlib >= 1.1.4 is required for aMule

zlib 1.2.3-29.el6 is installed by default.

[HKM]

Ok do this below and post the output for me so I can see.

1) iptables -L -v -n --line-numbers
2) cat /var/lib/amuled/.aMule/amule.conf
3) cat /var/lib/amuled/.aMule/remote.conf

[redsnake]

Here we go

[HKM]

Sorry I seen your post but wasn't logged in so it showed empty thought you were going to pastebin it or something. I just logged in and see you posted the files by attaching to the post.

---
I looked in your iptables. You have somewhat correct setup but do this please. First thing you want to do is remove the ports you added for aMule and then as root type the two commands below.

1) iptables -A INPUT -p tcp -m state --state NEW --match multiport --dport 4662,4711,4712 -j ACCEPT
2) iptables -A INPUT -p udp -m state --state NEW --match multiport --dport 4665,4672 -j ACCEPT
3) /sbin/service iptables save
4) service iptables restart

This will make it much simple as it will be listed all in each line for tcp/udp as multiport. As you can see you have added additional port 4711 (WEB) and 4712 (EC2). This will save the changes and restart iptables this time opening ports for WEB/EC2.
---

Also What type of arch is aMuleD deployed on? is it router/NAS? For now do this:

1) cd /var/lib/amuled/.aMule/
2) rm -rf /var/lib/amuled/.aMule/shareddir.dat
3) chown -R amuled:amuled *

I don't know if you sharing anything so this will remove all the absolute path to dirs that is being shared. Just incase you shared file its hashing it thus slowing down everything which can be bottleneck if its over the network allocated on different location than current unit where its deployed.

Now you should be able to access aMuleWEB (127.0.0.1:4711) also try the aMuleGUI (127.0.0.1:4712) to make sure its working fully. Also you can connect to aMuleD via aMuleCLI from console in addition to that. Post back if you still having problem.

[redsnake]

Ok, amule is running on a headless server, mini-itx with a 4-core celeron no HT.
Meaning that I cant connect locally since there is no screen and no desktop etc installed.
aMule is connected (DOWNLOADING AND UPLOADING) to the world thru a vpn (tun0) (openVPN), only access to amule with amulegui and web is from internal net, where everything should be opened, the only opened ports in the vpn is amule (4662, 4665 and 4672) and the transmissionbt-port.
I am also using a transmission remote gui to connect to transmission, without any problems or hickups.
Its only aMule that miss-behaves.
Transmission down and upploads without any problems.
I am managing the server with webmin, no problems there either.
I am using "Arnos IP-Tables and Firewall script.
Temp-files and finished files sits on a locally mounted raid-6 array (LinuxRaid (MD)).
System disk is a small 60G ssd.

This is a new server, the old one worked as a charm basically the same setup, same software and same OS, just different MoBo and larger disk in the new one.

[HKM]

lol you mean local headless ITX setup like this? I have 15 nodes total 1local/14remote all deployed on CentOS running aMule right now. Since I upload near 450-500GB per day now routing those though OVPN would be waste of bandwidth and reduce speed. Far as accessing goes majority of us just SSH2 into the nodes and do everything we need via as no need for vnc+xde since you can do all via cli. I rarely even use aMuleGUI/aMuleWEB most of all is fully propagated as its connected to each other via NFS. But anyways so I assume everything is now working fully on your end?

This is just the box you see in the photo.

Code: [Select]

Uptime: 1 Days 16:43 hours
Uploaded Data: 193.987 GB
   eMule: 182.679 GB
   aMule: 10.789 GB
   lphant: 671.85 MB
Total Overhead: 514.09 MB (20.01M)
File Request Overhead: 438.77 MB (19.16M)
Source Exchange Overhead: 45 kB (837)
Server Overhead: 134 kB (147)
Kad Overhead: 72.99 MB (814k)
Crypt overhead: 7.41 MB
Active Uploads: 25
Successful sessions: 10858
Failed sessions: 460
Average time: 5:45 mins
Average upload rate: 1.35 MB/s
Max upload rate: 4.24 MB/s
Filtered: 2955
Banned: 3
Number of Files: 494
Total size of Files: 136.694 GB


[redsnake]

Well, it seems to be working, however aMulegui updates evwery 30-60 minutes or so, aMulecomd doesnt work after 5 minutes or so.
So something surely happens some 5 minutes after the daemon is launched, if I close and reopen aMueGUI it will not reconnect.
If it helps I can do some wireshark traces on the connection between the gui and the daemon.

[redsnake]

Some more info, this is from amulecmd, when trying to add a link
This is amulecmd 2.3.1

Creating client...
EC connection failed. Empty reply.
Connection Failed. Unable to connect to 192.168.10.199:4712
Press any key to continue . . .

Together with a wireshark capture from the same session.
Wireshark 2.0.3

[HKM]

Hmmm if aMuleCLI/aMuleGUI is able to connect to aMuleD when you first start then its setup correctly to some point. I mean I looked at your amule.conf/remote.conf as you setup correctly. Now I don't know why it would cause aMuleGUI to update 30-60mins thats crazy as it updates in real time but only exception I know of refresh interval rate that apply for aMuleWEB.

Disable OpenVPN and try to run aMule directly without routing it also do full iptables flush and lets see what happens vanilla.

1) service openvpn stop
2) service iptables stop

See if this works correctly if something was being filtered before. If it works post back and we will work on adding sensible iptables policies after fully flushed below.

1) /sbin/service iptables save
2) cp /etc/sysconfig/iptables /etc/sysconfig/iptables.bkp
3) iptables -F

[redsnake]

Actually installed mlDonkey, this evening, and it works correctly.