Bug#862988: dante-server: Job for danted.service failed because the control process exited with error code during installation
Hi, Peter. El domingo 21 de mayo del 2017 a las 17:28:39 +0300, Peter Pentchev escribió: > > > Yeah, I guess I'll have to fix that at some point, probably before the > > > stretch release. Right after installation, the sample config file for > > > dante-server does not specify any network interfaces at all (obviously, > > > since nothing is known at that point), but then the dante server is > > > automatically started, so it fails, and the installation itself fails. > > > The correct fix would be to make dante-server not start automatically on > > > installation; I'll take a look at this in the next couple of days. > > > > > > In the meantime, could you try to take a look at the /etc/danted.conf > > > file, configure it for your use case (at the very least, specify the > > > listening address, and maybe some rules), then try to start the > > > dante-server service? If this works, if the dante-server service may be > > > started properly, you can then run: > > > > > > dpkg-reconfigure -a > > > > > > ...to let dpkg and apt complete the package installation. > Ahh, so that's what happens when one posts before caffeine... of course, > this was supposed to be: > > dpkg --configure -a > > ...there's nothing that dpkg-reconfigure can do to help. No problem :-) I think that anyway the installation was completed successfully using "aptitude reinstall dante-server". > > > Sorry about that, I keep forgetting about it :( I'll fix it soon. > > > > > > Thanks for your interest in Dante! > > Thanks for your reply. > > > > I added a minimal configuration, specifying the internal and external > > interfaces and then running "aptitude reinstall dante-server". This > > seems to solve the issue with the installation and then the service > > starts without problems: > I'm glad that it worked for you! I've committed the fix to my dante > packaging Git repository, I'll ask the release team for a freeze > exception so that the fix makes it into the next release. > > Thanks for your understanding, and do not hesitate to let me know if > you hit any other problems! Thank you very much! I add below some other comments that may be useful. Do you think it might be a good idea to enable the service at the boot of the operating system? I think it is currently necessary to do "systemctl enable danted" for this happen. Do you think it might be a good idea to use something like: --- # Include Dante defaults if available if [ -f /etc/default/dante ]; then . /etc/default/dante fi --- I think it might be useful if someone wants to start the service with some additional parameter (eg "-d" for debug mode) without having to manually modify the startup script. Thanks for your time. Kind regards, -- Ing. Daniel Bareiro Opción Libre - Soberanía tecnológica para su empresa WWW: http://www.opcion-libre.com.ar Tel: +54 11 5235-3090 Correo-e: conta...@opcion-libre.com.ar signature.asc Description: Digital signature
Bug#862988: dante-server: Job for danted.service failed because the control process exited with error code during installation
control: severity -1 serious control: tags -1 + confirmed pending On Sat, May 20, 2017 at 12:58:42PM -0300, Daniel Bareiro wrote: > On 20/05/17 10:17, Peter Pentchev wrote: > > >> Package: dante-server > >> Version: 1.4.1+dfsg-4 > >> Severity: important > >> > >> Dear Maintainer, > >> > >> I am trying to install dante-server in Debian Stretch but the > >> installations fails with the following error: > >> > >> --- > >> root@defiant:~# aptitude install dante-server > > [snip] > >> Job for danted.service failed because the control process exited with > >> error code. > >> See "systemctl status danted.service" and "journalctl -xe" for details. > >> invoke-rc.d: initscript danted, action "start" failed. > > [snip] > >> may 19 13:21:14 defiant systemd[1]: Starting SOCKS (v4 and v5) proxy > >> daemon (danted)... > >> may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811468) > >> danted[15761]: warning: checkconfig(): no socks authentication metho…t > >> intended? > >> may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811545) > >> danted[15761]: error: checkconfig(): no internal address given for s… > >> clients on > >> may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811565) > >> danted[15761]: alert: mother[1/1]: shutting down > >> may 19 13:21:14 defiant systemd[1]: danted.service: Control process > >> exited, code=exited status=1 > >> may 19 13:21:14 defiant systemd[1]: Failed to start SOCKS (v4 and v5) > >> proxy daemon (danted). > > > Hi, > > Hi, Peter. > > > Yeah, I guess I'll have to fix that at some point, probably before the > > stretch release. Right after installation, the sample config file for > > dante-server does not specify any network interfaces at all (obviously, > > since nothing is known at that point), but then the dante server is > > automatically started, so it fails, and the installation itself fails. > > The correct fix would be to make dante-server not start automatically on > > installation; I'll take a look at this in the next couple of days. > > > > In the meantime, could you try to take a look at the /etc/danted.conf > > file, configure it for your use case (at the very least, specify the > > listening address, and maybe some rules), then try to start the > > dante-server service? If this works, if the dante-server service may be > > started properly, you can then run: > > > > dpkg-reconfigure -a > > > > ...to let dpkg and apt complete the package installation. Ahh, so that's what happens when one posts before caffeine... of course, this was supposed to be: dpkg --configure -a ...there's nothing that dpkg-reconfigure can do to help. > > Sorry about that, I keep forgetting about it :( I'll fix it soon. > > > > Thanks for your interest in Dante! > > Thanks for your reply. > > I added a minimal configuration, specifying the internal and external > interfaces and then running "aptitude reinstall dante-server". This > seems to solve the issue with the installation and then the service > starts without problems: I'm glad that it worked for you! I've committed the fix to my dante packaging Git repository, I'll ask the release team for a freeze exception so that the fix makes it into the next release. Thanks for your understanding, and do not hesitate to let me know if you hit any other problems! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#862988: dante-server: Job for danted.service failed because the control process exited with error code during installation
On 20/05/17 10:17, Peter Pentchev wrote: >> Package: dante-server >> Version: 1.4.1+dfsg-4 >> Severity: important >> >> Dear Maintainer, >> >> I am trying to install dante-server in Debian Stretch but the >> installations fails with the following error: >> >> --- >> root@defiant:~# aptitude install dante-server > [snip] >> Job for danted.service failed because the control process exited with error >> code. >> See "systemctl status danted.service" and "journalctl -xe" for details. >> invoke-rc.d: initscript danted, action "start" failed. > [snip] >> may 19 13:21:14 defiant systemd[1]: Starting SOCKS (v4 and v5) proxy daemon >> (danted)... >> may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811468) >> danted[15761]: warning: checkconfig(): no socks authentication metho…t >> intended? >> may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811545) >> danted[15761]: error: checkconfig(): no internal address given for s… >> clients on >> may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811565) >> danted[15761]: alert: mother[1/1]: shutting down >> may 19 13:21:14 defiant systemd[1]: danted.service: Control process exited, >> code=exited status=1 >> may 19 13:21:14 defiant systemd[1]: Failed to start SOCKS (v4 and v5) proxy >> daemon (danted). > Hi, Hi, Peter. > Yeah, I guess I'll have to fix that at some point, probably before the > stretch release. Right after installation, the sample config file for > dante-server does not specify any network interfaces at all (obviously, > since nothing is known at that point), but then the dante server is > automatically started, so it fails, and the installation itself fails. > The correct fix would be to make dante-server not start automatically on > installation; I'll take a look at this in the next couple of days. > > In the meantime, could you try to take a look at the /etc/danted.conf > file, configure it for your use case (at the very least, specify the > listening address, and maybe some rules), then try to start the > dante-server service? If this works, if the dante-server service may be > started properly, you can then run: > > dpkg-reconfigure -a > > ...to let dpkg and apt complete the package installation. > > Sorry about that, I keep forgetting about it :( I'll fix it soon. > > Thanks for your interest in Dante! Thanks for your reply. I added a minimal configuration, specifying the internal and external interfaces and then running "aptitude reinstall dante-server". This seems to solve the issue with the installation and then the service starts without problems: -- # aptitude reinstall dante-server Se REINSTALARÁN los siguientes paquetes: dante-server 0 paquetes actualizados, 0 nuevos instalados, 1 reinstalados, 0 para eliminar y 0 sin actualizar. Necesito descargar 0 B/373 kB de ficheros. Después de desempaquetar se usarán 0 B. (Leyendo la base de datos ... 162559 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../dante-server_1.4.1+dfsg-4_amd64.deb ... Desempaquetando dante-server (1.4.1+dfsg-4) sobre (1.4.1+dfsg-4) ... Procesando disparadores para systemd (232-23) ... Configurando dante-server (1.4.1+dfsg-4) ... Procesando disparadores para man-db (2.7.6.1-2) ... -- -- # tail -F /var/log/sockd.log | ccze -A May 20 12:42:45 (1495294965.380768) danted[14627]: warning: checkconfig(): no socks authentication methods enabled. This means all socks requests will be blocked after negotiation. Perhaps this is not intended? May 20 12:42:45 (1495294965.396822) danted[14628]: info: Dante/server[1/1] v1.4.1 running -- Thanks for your time. Kind regards, -- Ing. Daniel Bareiro Opción Libre - Soberanía tecnológica para su empresa WWW: http://www.opcion-libre.com.ar Tel: +54 11 5235-3090 Correo-e: conta...@opcion-libre.com.ar signature.asc Description: OpenPGP digital signature
Bug#862988: dante-server: Job for danted.service failed because the control process exited with error code during installation
On Fri, May 19, 2017 at 01:43:37PM -0300, Daniel Bareiro wrote: > Package: dante-server > Version: 1.4.1+dfsg-4 > Severity: important > > Dear Maintainer, > > I am trying to install dante-server in Debian Stretch but the > installations fails with the following error: > > --- > root@defiant:~# aptitude install dante-server [snip] > Job for danted.service failed because the control process exited with error > code. > See "systemctl status danted.service" and "journalctl -xe" for details. > invoke-rc.d: initscript danted, action "start" failed. [snip] > may 19 13:21:14 defiant systemd[1]: Starting SOCKS (v4 and v5) proxy daemon > (danted)... > may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811468) > danted[15761]: warning: checkconfig(): no socks authentication metho…t > intended? > may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811545) > danted[15761]: error: checkconfig(): no internal address given for s… clients > on > may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811565) > danted[15761]: alert: mother[1/1]: shutting down > may 19 13:21:14 defiant systemd[1]: danted.service: Control process exited, > code=exited status=1 > may 19 13:21:14 defiant systemd[1]: Failed to start SOCKS (v4 and v5) proxy > daemon (danted). Hi, Yeah, I guess I'll have to fix that at some point, probably before the stretch release. Right after installation, the sample config file for dante-server does not specify any network interfaces at all (obviously, since nothing is known at that point), but then the dante server is automatically started, so it fails, and the installation itself fails. The correct fix would be to make dante-server not start automatically on installation; I'll take a look at this in the next couple of days. In the meantime, could you try to take a look at the /etc/danted.conf file, configure it for your use case (at the very least, specify the listening address, and maybe some rules), then try to start the dante-server service? If this works, if the dante-server service may be started properly, you can then run: dpkg-reconfigure -a ...to let dpkg and apt complete the package installation. Sorry about that, I keep forgetting about it :( I'll fix it soon. Thanks for your interest in Dante! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#862988: dante-server: Job for danted.service failed because the control process exited with error code during installation
Package: dante-server Version: 1.4.1+dfsg-4 Severity: important Dear Maintainer, I am trying to install dante-server in Debian Stretch but the installations fails with the following error: --- root@defiant:~# aptitude install dante-server Se instalarán los siguiente paquetes NUEVOS: dante-server 0 paquetes actualizados, 1 nuevos instalados, 0 para eliminar y 0 sin actualizar. Necesito descargar 0 B/373 kB de ficheros. Después de desempaquetar se usarán 993 kB. Seleccionando el paquete dante-server previamente no seleccionado. (Leyendo la base de datos ... 157294 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../dante-server_1.4.1+dfsg-4_amd64.deb ... Desempaquetando dante-server (1.4.1+dfsg-4) ... Procesando disparadores para systemd (232-23) ... Configurando dante-server (1.4.1+dfsg-4) ... Job for danted.service failed because the control process exited with error code. See "systemctl status danted.service" and "journalctl -xe" for details. invoke-rc.d: initscript danted, action "start" failed. ● danted.service - SOCKS (v4 and v5) proxy daemon (danted) Loaded: loaded (/lib/systemd/system/danted.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2017-05-19 13:21:14 -03; 14ms ago Docs: man:danted(8) man:danted.conf(5) Process: 15761 ExecStart=/usr/sbin/danted -D (code=exited, status=1/FAILURE) Process: 15755 ExecStartPre=/bin/sh -cuid=`sed -n -e "s/[[:space:]]//g" -e "s/#.*//" -e "/^user\.privileged/{s/[^:]*://p;q;}" /etc/danted.conf`; if [ -n "$uid" ]; then touch /var/run/danted.pid; chown $uid /var/run/danted.pid; fi (code=exited, status=0/SUCCESS) may 19 13:21:14 defiant systemd[1]: Starting SOCKS (v4 and v5) proxy daemon (danted)... may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811468) danted[15761]: warning: checkconfig(): no socks authentication metho…t intended? may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811545) danted[15761]: error: checkconfig(): no internal address given for s… clients on may 19 13:21:14 defiant danted[15761]: May 19 13:21:14 (1495210874.811565) danted[15761]: alert: mother[1/1]: shutting down may 19 13:21:14 defiant systemd[1]: danted.service: Control process exited, code=exited status=1 may 19 13:21:14 defiant systemd[1]: Failed to start SOCKS (v4 and v5) proxy daemon (danted). may 19 13:21:14 defiant systemd[1]: danted.service: Unit entered failed state. may 19 13:21:14 defiant systemd[1]: danted.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error al procesar el paquete dante-server (--configure): el subproceso instalado el script post-installation devolvió el código de salida de error 1 Procesando disparadores para man-db (2.7.6.1-2) ... Procesando disparadores para systemd (232-23) ... Se encontraron errores al procesar: dante-server E: Sub-process /usr/bin/dpkg returned an error code (1) Configurando dante-server (1.4.1+dfsg-4) ... Job for danted.service failed because the control process exited with error code. See "systemctl status danted.service" and "journalctl -xe" for details. invoke-rc.d: initscript danted, action "start" failed. ● danted.service - SOCKS (v4 and v5) proxy daemon (danted) Loaded: loaded (/lib/systemd/system/danted.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2017-05-19 13:21:16 -03; 16ms ago Docs: man:danted(8) man:danted.conf(5) Process: 15865 ExecStart=/usr/sbin/danted -D (code=exited, status=1/FAILURE) Process: 15859 ExecStartPre=/bin/sh -cuid=`sed -n -e "s/[[:space:]]//g" -e "s/#.*//" -e "/^user\.privileged/{s/[^:]*://p;q;}" /etc/danted.conf`; if [ -n "$uid" ]; then touch /var/run/danted.pid; chown $uid /var/run/danted.pid; fi (code=exited, status=0/SUCCESS) may 19 13:21:16 defiant systemd[1]: Starting SOCKS (v4 and v5) proxy daemon (danted)... may 19 13:21:16 defiant danted[15865]: May 19 13:21:16 (1495210876.368422) danted[15865]: warning: checkconfig(): no socks authentication metho…t intended? may 19 13:21:16 defiant danted[15865]: May 19 13:21:16 (1495210876.368495) danted[15865]: error: checkconfig(): no internal address given for s… clients on may 19 13:21:16 defiant danted[15865]: May 19 13:21:16 (1495210876.368514) danted[15865]: alert: mother[1/1]: shutting down may 19 13:21:16 defiant systemd[1]: danted.service: Control process exited, code=exited status=1 may 19 13:21:16 defiant systemd[1]: Failed to start SOCKS (v4 and v5) proxy daemon (danted). may 19 13:21:16 defiant systemd[1]: danted.service: Unit entered failed state. may 19 13:21:16 defiant systemd[1]: danted.service: Failed with result 'exit-code'. Hint: Some lines were ellipsized, use