Your message dated Mon, 2 Jul 2018 10:52:11 -0400 with message-id <cab4xwxyttkbtd+fjttsrvuat7303kpesarh8hdbamb-cfir...@mail.gmail.com> and subject line Re: Bug#902546: amule-daemon: crashes on start: 0.0.0.0 4712 failed - Address already in use has caused the Debian Bug report #902546, regarding amule-daemon: crashes on start: 0.0.0.0 4712 failed - Address already in use to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 902546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902546 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: amule-daemon Version: 1:2.3.2-1+b2 Severity: important Dear Maintainer, After running without peoblems for years, A Mule has stopped working: !2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 4712 failed - Address already in use 2018-06-27 17:37:30: Could not listen for external connections at 0.0.0.0:4712! !2018-06-27 17:37:30: Error creating UDP socket 0.0.0.0 4665 : Address already in use !2018-06-27 17:37:30: MuleUDPSocket: Failed to create valid Server UDP-Socket !2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 4662 failed - Address already in use !2018-06-27 17:37:30: ERROR: Could not listen to TCP port. !2018-06-27 17:37:30: Port 4662 is not available. You will be LOWID !2018-06-27 17:37:30: ERROR: ERROR Port 4662 is not available! !2018-06-27 17:37:30: This means that you will be LOWID. !2018-06-27 17:37:30: Check your network to make sure the port is open for output and input. !2018-06-27 17:37:30: Error creating UDP socket 0.0.0.0 4672 : Address already in use !2018-06-27 17:37:30: MuleUDPSocket: Failed to create valid Client UDP-Socket 2018-06-27 17:37:30: amuled: forking to background - see you 2018-06-27 17:37:30: Loading server.met file: /home/amule/.aMule/server.met -------------------------------------------------------------------------------- A fatal error has occurred and aMule has crashed. But the ports are not in use, according to F User. -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AX.UTF-8, LC_CTYPE=en_AX.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968), LANGUAGE=en_IE:en (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages amule-daemon depends on: ii amule-common 1:2.3.2-1 ii libboost-system1.62.0 1.62.0+dfsg-4 ii libc6 2.24-11+deb9u3 ii libcrypto++6 5.6.4-7 ii libgcc1 1:6.3.0-18+deb9u1 ii libpng16-16 1.6.28-1 ii libreadline7 7.0-3 ii libstdc++6 6.3.0-18+deb9u1 ii libupnp6 1:1.6.19+git20160116-1.2 ii libwxbase3.0-0v5 3.0.2+dfsg-4 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages amule-daemon recommends: ii amule-utils 1:2.3.2-1+b2 ii unzip 6.0-21 amule-daemon suggests no packages. -- Configuration Files: /etc/default/amule-daemon changed: AMULED_USER="amule" AMULED_HOME="/home/amule" RUN_AT_STARTUP="YES" -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = "en_IE:en", LC_ALL = (unset), LANG = "en_AX.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory
--- End Message ---
--- Begin Message ---as confirmed in a private email, a reboot fixed the issue, hence closing On Wed, Jun 27, 2018 at 2:57 PM Sandro Tosi <[email protected]> wrote: > > > !2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 > > 4712 failed - Address already in use > > 2018-06-27 17:37:30: Could not listen for external connections at > > 0.0.0.0:4712! > > !2018-06-27 17:37:30: Error creating UDP socket 0.0.0.0 4665 : Address > > already in use > > !2018-06-27 17:37:30: MuleUDPSocket: Failed to create valid Server > > UDP-Socket > > !2018-06-27 17:37:30: Asio Sockets: CAsioSocketServerImpl bind to 0.0.0.0 > > 4662 failed - Address already in use > [8<] > > But the ports are not in use, according to F User. > > are you absolutely sure there is nothing using those ports, like a > stuck amule process? did u use fuser as root? did you check also via > netstat? what if you reboot the machine where this is running (i know > the impact of this could be high)? do you have an actual backtrace > from amule (the port in use could be a red herring for some other > issue)? > > as you said, amule has worked for you since years, weird something > happened right now out of the blue that's related to the package > version in stable, which we havent touched in months. > > -- > Sandro "morph" Tosi > My website: http://sandrotosi.me/ > Me at Debian: http://wiki.debian.org/SandroTosi > G+: https://plus.google.com/u/0/+SandroTosi -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
--- End Message ---
