On 25/02/14 18:43, Tomasz Buchert wrote:
>
> Hi Evgeni,
> just to let you know that I'm working on this.
> I've tried with miredo in stable (1.2.3) and it starts fine.
> With 1.2.6 I have the same problem as you, so it is some kind
> of regression. I will find it. :)
>
> Thanks for the bug report.
>
> Cheers,
> Tomasz
Hi again,
actually checkconf *outputs* something, but it is not visible in
"systemctl status":
miredo.service - Teredo IPv6 tunneling
Loaded: loaded (/lib/systemd/system/miredo.service; enabled)
Active: failed (Result: exit-code) since Tue 2014-02-25 13:41:49 EST; 1min
40s ago
Process: 1229 ExecStartPre=/usr/sbin/miredo-checkconf -f
/etc/miredo/miredo.conf (code=exited, status=255)
Feb 25 13:41:49 debian systemd[1]: miredo.service: control process exited,
code=exited status=255
Feb 25 13:41:49 debian systemd[1]: Failed to start Teredo IPv6 tunneling.
Feb 25 13:41:49 debian systemd[1]: Unit miredo.service entered failed state.
It is however present in "journalctl":
Feb 25 13:41:49 debian miredo-checkconf[1229]: Invalid host name
“teredo-debian.remlab.net” at line 6: Temporary failure in name resolution
Feb 25 13:41:49 debian miredo-checkconf[1229]: Server address not specified
Feb 25 13:41:49 debian miredo-checkconf[1229]: Could not check config.
Feb 25 13:41:49 debian miredo-checkconf[1229]: Fatal configuration error
Feb 25 13:41:49 debian systemd[1]: miredo.service: control process exited,
code=exited status=255
Feb 25 13:41:49 debian systemd[1]: Failed to start Teredo IPv6 tunneling.
Feb 25 13:41:49 debian systemd[1]: Unit miredo.service entered failed state.
Hmmm, we should inform systemd guys, I think.
But, going back to our bug, it is caused by the missing DNS resolution at an
early
phase of the boot. "After=network.target" is apparently not enough to have
DNS...
I can't find any information how to ensure DNS resolution in systemd.
The workaround for now is to replace name in miredo config with its IP address
(it worked for me at least).
The real solution is either to:
1) find a way to ensure DNS resolution via systemd (I think it may be
impossible)
2) add a loop with timeout inside miredo checkconf that waits for DNS
to finish completely (presupposing that it's just a matter of time)
I'll try to find 1), but ultimately I may go with 2).
Cheers,
Tomasz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
