aMule Forum
English => en_Bugs => Topic started by: GilesBathgate on May 08, 2009, 05:47:53 PM
-
I have been having trouble with 2.2.4 since its release. I have been experiencing fairly regular lockups, after running amuled for about 1hr, I cannot connect to amuled using amulecmd.
I wrote this testscript to prove my problem.
#!/bin/sh
amuled -f
sleep 1m
date
amulecmd -c status
sleep 1h
date
amulecmd -c status
The output of which is so:
amuled: OnInit - starting timer
Initialising aMuled 2.2.4 using wxGTK2 v2.8.7
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
amuled: forking to background - see you
HTTP download thread started
Fri May 8 15:12:44 BST 2009
This is amulecmd 2.2.4
Creating client...
Succeeded! Connection established to aMule 2.2.4
> eD2k: Connected to Sharing Kingdom 1 [89.248.172.54:4500] with HighID
> Kad: Connected (ok)
> Download: 0 bytes/sec
> Upload: 2.52 kB/s
> Clients in queue: 0
> Total sources: 59
Fri May 8 16:12:44 BST 2009
This is amulecmd 2.2.4
Creating client...
The timeout for this operation expired
EC connection failed. Empty reply.
Connection Failed. Unable to connect to localhost:4712
Here is my .aMule/logfile
2009-05-08 15:11:41: amule.cpp(605): Starting aMuled 2.2.4 using wxGTK2 v2.8.7
2009-05-08 15:11:41: ClientCreditsList.cpp(168): Creditfile loaded, 2759 clients are known
2009-05-08 15:11:41: IPFilter.cpp(109): Loading IP-filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2009-05-08 15:11:41: IPFilter.cpp(334): Loaded 5 IP-ranges from '/home/giles/.aMule/ipfilter.dat'. 0 malformed lines were discarded.
2009-05-08 15:11:41: IPFilter.cpp(334): Loaded 0 IP-ranges from '/home/giles/.aMule/ipfilter_static.dat'. 0 malformed lines were discarded.
2009-05-08 15:11:41: ExternalConn.cpp(159): *** TCP socket (ECServer) listening on 0.0.0.0:4712
2009-05-08 15:11:41: MuleUDPSocket.cpp(81): Created Server UDP-Socket at port 2665
2009-05-08 15:11:41: MuleUDPSocket.cpp(81): Created Client UDP-Socket at port 2672
2009-05-08 15:11:41: UPnPBase.cpp(868): Universal Plug and Play: bound to 192.168.2.10:50000.
2009-05-08 15:11:44: UPnPBase.cpp(1225): Universal Plug and Play: Internet Gateway Device Detected.
2009-05-08 15:11:44: UPnPBase.cpp(545): Universal Plug and Play: WAN Service Detected: 'urn:schemas-upnp-org:service:WANIPConnection:1'.
2009-05-08 15:11:44: UPnPBase.cpp(1529): Universal Plug and Play: Successfully retrieved SCPD Document for service urn:schemas-upnp-org:service:WANIPConnection:1, absEventSubURL: http://192.168.2.1:49152/upnp/event/WANIPConnection.
2009-05-08 15:11:44: UPnPBase.cpp(1543): Universal Plug and Play: Successfully subscribed to service urn:schemas-upnp-org:service:WANIPConnection:1, absEventSubURL: http://192.168.2.1:49152/upnp/event/WANIPConnection.
2009-05-08 15:11:44: UPnPBase.cpp(562): Universal Plug and Play: Uninteresting service detected: 'urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1'. Ignoring.
2009-05-08 15:11:44: UPnPBase.cpp(562): Universal Plug and Play: Uninteresting service detected: 'urn:schemas-microsoft-com:service:OSInfo:1'. Ignoring.
2009-05-08 15:11:44: UPnPBase.cpp(1225): Universal Plug and Play: Internet Gateway Device Detected.
2009-05-08 15:11:44: UPnPBase.cpp(1458): Universal Plug and Play: UPNP_EVENT_RECEIVED:
SID: uuid:27b078aa-1dd2-11b2-9b12-adc2b1536ede
Key: 0
Property list:
PossibleConnectionTypes='IP_Routed'
ConnectionStatus='Connected'
ExternalIPAddress='0.0.0.0'
PortMappingNumberOfEntries='1'
2009-05-08 15:11:44: UPnPBase.cpp(1225): Universal Plug and Play: Internet Gateway Device Detected.
2009-05-08 15:11:44: UPnPBase.cpp(1225): Universal Plug and Play: Internet Gateway Device Detected.
2009-05-08 15:11:44: UPnPBase.cpp(1458): Universal Plug and Play: UPNP_EVENT_RECEIVED:
SID: uuid:27b078aa-1dd2-11b2-9b12-adc2b1536ede
Key: 1
Property list:
PortMappingNumberOfEntries='2'
2009-05-08 15:11:44: UPnPBase.cpp(1458): Universal Plug and Play: UPNP_EVENT_RECEIVED:
SID: uuid:27b078aa-1dd2-11b2-9b12-adc2b1536ede
Key: 2
Property list:
PortMappingNumberOfEntries='3'
2009-05-08 15:11:44: UPnPBase.cpp(1458): Universal Plug and Play: UPNP_EVENT_RECEIVED:
SID: uuid:27b078aa-1dd2-11b2-9b12-adc2b1536ede
Key: 3
Property list:
PortMappingNumberOfEntries='4'
2009-05-08 15:11:44: ServerList.cpp(84): Loading server.met file: /home/giles/.aMule/server.met
2009-05-08 15:11:44: ServerList.cpp(169): 7 servers in server.met found
2009-05-08 15:11:44: ServerList.cpp(831): Start downloading server list from http://peerates.net/servers.php
2009-05-08 15:11:44: DownloadQueue.cpp(171): Found 6 part files
2009-05-08 15:11:44: SharedFileList.cpp(352): Found 103 known shared files
2009-05-08 15:11:44: amule.cpp(803): Connecting
2009-05-08 15:11:44: ServerSocket.cpp(754): Connecting to eDonkeyServer No2 (212.63.206.35 - 212.63.206.35:4242) using protocol obfuscation.
2009-05-08 15:11:46: RoutingZone.cpp(208): Read 187 Kad contacts
2009-05-08 15:11:46: Logger.cpp(275): Deleted stale lock file '/home/giles/.aMule/muleLock'.
2009-05-08 15:11:46: ThreadScheduler.cpp(308): ThreadScheduler: Completed task 'AICH Syncronizing', 0 tasks remaining.
2009-05-08 15:11:46: ServerList.cpp(84): Loading server.met file: /home/giles/.aMule/server_auto.met
2009-05-08 15:11:46: ServerList.cpp(171): 0 servers added
2009-05-08 15:11:46: Connected to Kad (firewalled)
2009-05-08 15:11:46: ServerConnect.cpp(342): Lost connection to eDonkeyServer No2 (212.63.206.35:4242)
2009-05-08 15:11:46: ServerConnect.cpp(401): Connection lost
2009-05-08 15:11:46: ServerSocket.cpp(754): Connecting to Sharing Kingdom 2 (89.248.172.50 - 89.248.172.50:4500) using protocol obfuscation.
2009-05-08 15:11:46: ServerConnect.cpp(190): Connected to Sharing Kingdom 2 (89.248.172.50:4500)
2009-05-08 15:11:46: ServerConnect.cpp(342): Lost connection to Sharing Kingdom 2 (89.248.172.50:4500)
2009-05-08 15:11:46: ServerConnect.cpp(401): Connection lost
2009-05-08 15:12:04: Connected to Kad (ok)
2009-05-08 15:12:10: ServerConnect.cpp(463): Connection attempt to eDonkeyServer No2 (212.63.206.35:4242) timed out.
2009-05-08 15:12:10: ServerSocket.cpp(754): Connecting to Sharing Kingdom (93.174.93.242 - 93.174.93.242:4500) using protocol obfuscation.
2009-05-08 15:12:10: ServerConnect.cpp(463): Connection attempt to Sharing Kingdom (93.174.93.242:4500) timed out.
2009-05-08 15:12:10: ServerSocket.cpp(754): Connecting to Sharing Kingdom 3 (89.248.172.86 - 89.248.172.86:4500) using protocol obfuscation.
2009-05-08 15:12:10: ServerConnect.cpp(190): Connected to Sharing Kingdom 3 (89.248.172.86:4500)
2009-05-08 15:12:10: ServerConnect.cpp(342): Lost connection to Sharing Kingdom 3 (89.248.172.86:4500)
2009-05-08 15:12:10: ServerConnect.cpp(401): Connection lost
2009-05-08 15:12:11: ServerConnect.cpp(463): Connection attempt to Sharing Kingdom 2 (89.248.172.50:4500) timed out.
2009-05-08 15:12:11: ServerSocket.cpp(754): Connecting to PEERATES.NET (88.191.50.111 - 88.191.50.111:1111) using protocol obfuscation.
2009-05-08 15:12:11: ServerConnect.cpp(463): Connection attempt to PEERATES.NET (88.191.50.111:1111) timed out.
2009-05-08 15:12:11: ServerSocket.cpp(754): Connecting to Sharing Kingdom 1 (89.248.172.54 - 89.248.172.54:4500) using protocol obfuscation.
2009-05-08 15:12:11: ServerConnect.cpp(190): Connected to Sharing Kingdom 1 (89.248.172.54:4500)
2009-05-08 15:12:12: ServerConnect.cpp(263): Connection established on: Sharing Kingdom 1
2009-05-08 15:12:12: Connected to Sharing Kingdom 1 with HighID
2009-05-08 15:12:12: ServerSocket.cpp(417): New clientid is 3811874126
2009-05-08 15:12:12: ServerMessage: server version 17.15 (lugdunum)
2009-05-08 15:12:44: ExternalConn.cpp(217): New external connection accepted
2009-05-08 15:12:44: ExternalConn.cpp(251): Connecting client: aMulecmd 2.2.4
2009-05-08 15:12:44: ExternalConn.cpp(306): Access granted.
2009-05-08 15:12:44: ExternalConn.cpp(116): External connection closed.
After the hour is up, amuled is still a running process
giles@korma:~$ ps -A | grep amuled
6870 ? 00:02:21 amuled
My system is a fairly standard install of Debian Lenny, and the binaries are from Volstreckers apt source.
-
How are you starting the deamon. I didn't add the code to remove the startup script that's shipped by the packages from orig repo, so maybe it get's started as different user or so. Have you pinned my repo? The versions in orig repos and mine are identical, so it could happen that apt is confused and mixed them.
-
How are you starting the deamon.
as the user giles i run
amuled -f
It is this user that it picks up the config file /home/giles/.aMule/amule.conf and also this user which i run amulecmd
I didn't add the code to remove the startup script that's shipped by the packages from orig repo, so maybe it get's started as different user or so.
I also thought this, i decided to roll back everything at one point and install the debian version 2.2.1, I had no problems with this version.
I then removed the debian version doing an
apt-get --purge remove amule
before installing your version again. I verified that the --purge option successfully removed all the /etc/init.d/amule-daemon scripts and such like.
Have you pinned my repo? The versions in orig repos and mine are identical, so it could happen that apt is confused and mixed them.
I could try this, but I wasn't sure whether this was a configuration option or just a bug.
Ideally I would like someone else to confirm that my testscript works for them.
-
Which test-script?
-
The one I wrote and posted in the first message of this topic. Its a farily basic test, and I am willing to try any other tests that are available, as well as building debug versions of 2.2.4 and anything else that would aid resolving my problem.
I wrote this testscript to prove my problem.
#!/bin/sh
amuled -f
sleep 1m
date
amulecmd -c status
sleep 1h
date
amulecmd -c status
-
Does it work, when you call amulecmd manually? I've almost no experience with amuled. With monolithic it works.
-
Does it work, when you call amulecmd manually? I've almost no experience with amuled. With monolithic it works.
No it dosen' work when done manually, I tried the whole process manually several times before writing the script, I just wrote the script to illustrate the problem and the timings involved. I also hoped that someone else might try the script and post the output so I can determine whether this is a bug or just a configuration problem.
-
I compiled amule 2.2.4 from sources, and I haven't had problems since.
-
I had the same problem. I think the reason was that my ubuntu home folder (~) was encrypted and aMule's conf folder together with the Incoming and Temp folders (.aMule) was inside it. As soon as I moved .aMule to a non-encrypted location the problem ceased.