|Anonymous | Login | Signup for a new account||2019-03-19 08:40 WET|
|Main | My View | View Issues | Change Log | Roadmap | Docs | My Account|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000072||[MyDNS-NG] Global||minor||always||2013-02-13 21:47||2014-08-07 19:00|
|Summary||0000072: mydns-22.214.171.124: ipv6_listener bind failed|
running on Centos6 64 bits.
When starting a server with ipv6 network configuration mydns won't start on boot.
When disabling ipv6 there is no issue.
/etc/init.d/mydns stop; /etc/init.d/network restart; /etc/init.d/mydns start
Feb 6 16:34:44 auth3 mydns: ipv6_listener: bind on socket 6
(UDP): failed 2002:1af9:4040:a012:2::53+53: Cannot assign requested address
(ipv6 address mentioned here is fake)
After some test it seems like there needs to be some time between the network and mydns startup
/etc/init.d/mydns stop; /etc/init.d/network restart; sleep 5; /etc/init.d/mydns start
|Tags||No tags attached.|
This really isnt a mydns bug per-se except for the fact that it doesnt handle it gracefully. Ill see if i can find a way to make it silently ignore the fact that the address cant be bound, and bind it automatically when it becomes available.
Most (network) programs will "exit", if the network interface you explicitly specific to bind to is not available -- this is what is happening here.
May also be able to set a network-up dependancy order on the rc scripts possibly. Will look into ways to fix it and report back at some point. Deescalation the priority of this for now - will attempt a fix as time permits.
|2013-02-13 21:47||jushal||New Issue|
|2014-08-05 23:47||jameno123||Note Added: 0000205|
|2014-08-05 23:47||jameno123||Assigned To||=> jameno123|
|2014-08-05 23:47||jameno123||Status||new => acknowledged|
|2014-08-05 23:47||jameno123||Priority||normal => low|
|2014-08-07 19:00||jameno123||version||=> 126.96.36.199|
|2014-08-07 19:00||jameno123||Target Version||=> 1.2.9|
|Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group|