You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using aMule 2.3.3 (Debian Bullseye package) for several months and I notice the network traffic stops after 1 day approximately. I know this issue does not contain enough information to fix the problem but maybe it keeps all related issues in the same place.
I'm running aMule 24/7 in my server and I notice the network traffic stops after 1 day approximately. aMule is connected to 1 ed2k server and Kad network, just sharing files, not downloading anything. I only use amuled and amuleweb processes. There aren't traces or errors when that happens, just silence until I restart aMule. In the Web UI I can see it is still connected to both networks.
To fix this issue I configured a cron task that restarts aMule every 2 days, if I don't, aMule stops sharing my files.
The text was updated successfully, but these errors were encountered:
I have been using aMule 2.3.3 (Debian Bullseye package) for several months and I notice the network traffic stops after 1 day approximately. I know this issue does not contain enough information to fix the problem but maybe it keeps all related issues in the same place.
I'm running aMule 24/7 in my server and I notice the network traffic stops after 1 day approximately. aMule is connected to 1 ed2k server and Kad network, just sharing files, not downloading anything. I only use
amuled
andamuleweb
processes. There aren't traces or errors when that happens, just silence until I restart aMule. In the Web UI I can see it is still connected to both networks.To fix this issue I configured a cron task that restarts aMule every 2 days, if I don't, aMule stops sharing my files.
The text was updated successfully, but these errors were encountered: