Test environment: Raspberry Pi 400 running Raspberry OS (Debian 13 trixie). Wondering if this bug is architecture-specific.
uname -a
Linux raspberrypi 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1 (2026-03-11) aarch64 GNU/Linux
Steps to reproduce:
launch amuled -f --ec-config
connect to the daemon using amulegui, search for a popular file and download it. File is ~3GB in case it matters.
The file can reach 99% downloaded, but nothing is written to disk in Temp folder:
test@raspberrypi:~/.aMule/Temp $ ll
total 8
-rw-rw-r-- 1 test test 0 jun 4 21:40 001.part
-rw-rw-r-- 1 test test 327 jun 4 21:40 001.part.met
-rw-rw-r-- 1 test test 327 jun 4 21:40 001.part.met.bak
Also, the CPU usage stays very high during the download and when it reaches 99% completed. Even at this point, the part file is still 0 bytes, and the file gets stuck.
2026-06-04 21:39:34: amuleAppCommon.cpp(416): Initialising aMuleD GIT compiled with wxBase(GTK3) v3.2.8 and Boost 1.83 (Debugging) (Snapshot: rev. 3.0.0-pre-94-gf936bc5c6)
2026-06-04 21:39:34: amuleAppCommon.cpp(463): Checking if there is an instance already running...
2026-06-04 21:39:34: amuleAppCommon.cpp(494): No other instances are running.
2026-06-04 21:39:34: amule.cpp(580):
2026-06-04 21:39:34: EC configuration
2026-06-04 21:39:38: amule.cpp(583): Password set and external connections enabled.
2026-06-04 21:39:38: ClientCreditsList.cpp(158): Creditfile loaded, 24 clients are known
2026-06-04 21:39:38: ExternalConn.cpp(413): *** TCP socket (ECServer) listening on 0.0.0.0:4712
2026-06-04 21:39:38: MuleUDPSocket.cpp(79): Created Server UDP-Socket at port 4665
2026-06-04 21:39:38: ListenSocket.cpp(63): ListenSocket: Ok.
2026-06-04 21:39:38: MuleUDPSocket.cpp(79): Created Client UDP-Socket at port 4672
2026-06-04 21:39:38: amuled.cpp(176): amuled: forking to background - see you
2026-06-04 21:39:38: ServerList.cpp(96): Loading server.met file: /home/test/.aMule/server.met
!2026-06-04 21:39:38: ServerList.cpp(182): 9 servers in server.met found
2026-06-04 21:39:38: DownloadQueue.cpp(109): Loading temp files from /home/test/.aMule/Temp.
2026-06-04 21:39:38: DownloadQueue.cpp(159): All PartFiles Loaded.
2026-06-04 21:39:38: DownloadQueue.cpp(162): No part files found
2026-06-04 21:39:38: SharedFileList.cpp(404): Found 1 known shared file
2026-06-04 21:39:38: amuled.cpp(161): amuled: OnInit - starting timer
2026-06-04 21:39:38: LibSocketAsio.cpp(1585): Asio thread 1 started
2026-06-04 21:39:38: LibSocketAsio.cpp(1585): Asio thread 2 started
2026-06-04 21:39:38: LibSocketAsio.cpp(1585): Asio thread 3 started
2026-06-04 21:39:38: LibSocketAsio.cpp(1585): Asio thread 4 started
2026-06-04 21:39:38: IPFilter.cpp(113): Loading IP filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2026-06-04 21:39:38: IPFilter.cpp(333): Loaded 0 IP-ranges from '/home/test/.aMule/ipfilter.dat'.
2026-06-04 21:39:38: IPFilter.cpp(333): Loaded 0 IP-ranges from '/home/test/.aMule/ipfilter_static.dat'.
2026-06-04 21:39:38: IPFilter.cpp(534): IP filter is ready
!2026-06-04 21:39:38: IPFilter.cpp(544): Connecting
2026-06-04 21:39:38: ServerSocket.cpp(707): Connecting to eMule Security (45.82.80.155 - 45.82.80.155:5687) using protocol obfuscation.
2026-06-04 21:39:38: RoutingZone.cpp(209): Read 198 Kad contacts
!2026-06-04 21:39:38: amule.cpp(2212): Kad started.
2026-06-04 21:39:39: ServerConnect.cpp(198): Connected to eMule Security (45.82.80.155:5687)
2026-06-04 21:39:39: HTTPDownload.cpp(353): Downloaded https://api.github.com/repos/amule-org/amule/releases/latest (15724 bytes)
2026-06-04 21:39:39: amule.cpp(1967): Your copy of aMule is up to date.
2026-06-04 21:39:40: ServerSocket.cpp(707): Connecting to eMule Sunrise (176.123.5.89 - 176.123.5.89:4725) using protocol obfuscation.
2026-06-04 21:39:40: ServerConnect.cpp(198): Connected to eMule Sunrise (176.123.5.89:4725)
!2026-06-04 21:39:40: amule.cpp(2214): Kad stopped.
!2026-06-04 21:39:40: amule.cpp(2224): Connected to Kad (firewalled)
2026-06-04 21:39:48: ServerSocket.cpp(201): WARNING: eMule Security (45.82.80.155:5687) - NG : You have a lowid. Please review your network config and/or your settings.
!2026-06-04 21:39:48: ServerConnect.cpp(274): Connection established on: eMule Security
!2026-06-04 21:39:48: amule.cpp(2198): Connected to eMule Security with LowID
2026-06-04 21:39:48: ServerSocket.cpp(362): New clientid is YYYYYYYYYYYYYYYYY
!2026-06-04 21:39:48: ServerSocket.cpp(364): WARNING: You have received Low-ID!
2026-06-04 21:39:48: ServerSocket.cpp(365): Most likely this is because you're behind a firewall or router.
2026-06-04 21:39:48: ServerSocket.cpp(366): For more information, please refer to https://amule-org.github.io/docs
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: server version 17.15 (lugdunum)
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: Welcome to eMule Security! <> www.emule-security.org
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: Download Safe Serverlist > http://www.emule-security.org/serverlist/
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: IP-filter > http://www.emule-security.org/e107_plugins/faq/faq.php?0.cat.2.1
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: nodes.dat > http://www.emule-security.org/e107_plugins/faq/faq.php?0.cat.6.6
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: Ip-To-Country database> http://www.emule-security.org/e107_plugins/faq/faq.php?0.cat.7.10
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: eMule MODs > http://www.emule-security.org/modb/
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: VPN with port forwarding (for High ID) > https://bit.ly/4hpqBCI
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: Disclaimer: This server is only indexing file-hashes, and no contains any files,
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: not directly involved in the exchange of files between users of p2p-network.
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: Administration of server is not responsible for the contents of files
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: shared by connected to the server users. Please do not share
2026-06-04 21:39:48: amule.cpp(1809): ServerMessage: copyrighted material, DRM protected media, viruses or other harmful files!
2026-06-04 21:40:24: ExternalConn.cpp(490): New external connection accepted
2026-06-04 21:40:24: ExternalConn.cpp(522): Connecting client: amule-remote 0x0001
2026-06-04 21:40:24: ExternalConn.cpp(661): Access granted.
!2026-06-04 21:40:53: DownloadQueue.cpp(373): Downloading XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2026-06-04 21:41:17: ExternalConn.cpp(323): External connection closed.
2026-06-04 21:41:27: ExternalConn.cpp(490): New external connection accepted
2026-06-04 21:41:27: ExternalConn.cpp(522): Connecting client: amule-remote 0x0001
2026-06-04 21:41:27: ExternalConn.cpp(661): Access granted.
On the other side, if I do the same test with amule monolithic, it works ok: the Temp file is allocated from the beginning, and it downloads correctly until 100% completed.
Happy to help debug this, just let me know what to do. (Please note that I have limited free time and the moment, but I will do my best to respond asap)
Test environment: Raspberry Pi 400 running Raspberry OS (Debian 13 trixie). Wondering if this bug is architecture-specific.
Steps to reproduce:
launch amuled -f --ec-config
connect to the daemon using amulegui, search for a popular file and download it. File is ~3GB in case it matters.
The file can reach 99% downloaded, but nothing is written to disk in Temp folder:
Also, the CPU usage stays very high during the download and when it reaches 99% completed. Even at this point, the part file is still 0 bytes, and the file gets stuck.
On the other side, if I do the same test with amule monolithic, it works ok: the Temp file is allocated from the beginning, and it downloads correctly until 100% completed.
Happy to help debug this, just let me know what to do. (Please note that I have limited free time and the moment, but I will do my best to respond asap)