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
