On that sipxecs-setup script there is a library called urllib. In the middle of script, after getting master fqdn, master ip and password info, a new /etc/resolv.conf file is created. It makes the primary server as the dns. But at that point urllib does not know new dns configuration. So if it is possible to update urllib dns info, I think we will not have this problem. I don't know python. something like urllib.update
When you abort and do the same thing (sipxecs-setup), urllib loads with new dns coming from /etc/resolv.conf and you don't have this problem. Of course there is another solution, you can change the url in the script with the ip number of master instead of master fqdn. Because you already have this info. _lvnd_ (^_^) 2011/6/9 Kemal Eroğlu <[email protected]>: > My DNS configuration in setup is like this: > > Master Server -> is DNS server - Yes > Nameserver 1 - Company DNS > Nameserver 2 - Empty > > Secondary Server -> is DNS server - Yes > Nameserver 1 - Master Server > Nameserver 2 - Company DNS > > May be it can help you better understand the setup. > > Kemal > > On 9 June 2011 12:01, Michael Picher <[email protected]> wrote: >> >> If DNS is all set on separate machines (i.e., you answer yes to DNS >> question during install) and DNS is configured before installation all works >> properly. If DNS is on openUC systems (and you really should have 2 DNS >> servers) this needs to be fixed. >> I've created a JIRA. Please feel free to comment / >> vote: http://track.sipfoundry.org/browse/XX-9672 >> Thanks, >> Mike >> >> 2011/6/9 Kemal Eroğlu <[email protected]> >>> >>> Yes I tried and it worked, but i need an easier way to do this. >>> >>> Kemal >>> >>> On 9 June 2011 11:41, Michael Picher <[email protected]> wrote: >>>> >>>> Kemal, >>>> Did you test what I suggested doing? >>>> Mike >>>> >>>> 2011/6/9 Kemal Eroğlu <[email protected]> >>>>> >>>>> Hello, >>>>> >>>>> First of all, in this case master is our DNS, but master also has an >>>>> upper DNS which is the DNS we used in our company. >>>>> >>>>> I also think that something is wrong with the DNS resolving mechanism >>>>> of the secondary machine. I used putty when the setup is working and it >>>>> can >>>>> ping the fqdn of primary server; but when it tries to connect the master >>>>> in >>>>> setup, it gives this error. I could not figure out why. >>>>> >>>>> I tried to add a new line to the /etc/hosts of secondary. It is working >>>>> in this condition. But it is not a desired condition to apply this in >>>>> every >>>>> HA setup we do. >>>>> >>>>> I checked both server's /etc/resolv.conf files, they seemed OK to me. >>>>> Secondary server's resolv.conf file is set by the setup script during the >>>>> setup. So it has master IP address as its DNS. I think secondary server >>>>> should query the master fqdn and the master should be able to resolve it >>>>> normally. I found it strange. >>>>> >>>>> Best Regards, >>>>> >>>>> Kemal >>>>> >>>>> On 8 June 2011 22:32, Joe Micciche <[email protected]> wrote: >>>>>> >>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>> Hash: SHA1 >>>>>> >>>>>> > Hello, >>>>>> > I have an extended sipxecs 4.4 HA setup with one primary and one >>>>>> > redundant >>>>>> > server. When I set up the redundant, during sipxecs-setup, in the >>>>>> > last step >>>>>> > it asks for master-fqdn, master-ip and password to get the >>>>>> > configuration >>>>>> > files from master. I provide the information but it gives an error, >>>>>> > "Failure >>>>>> > fetching configuration from master .... Name or service not known.". >>>>>> > It >>>>>> > continuously gives this error, until I abort and redo the >>>>>> > "sipxecs-setup" >>>>>> > from the beginning. I investigated about this and saw that, it >>>>>> > somehow >>>>>> > cannot resolve the fqdn of the master. Did you encounter such an >>>>>> > error or do >>>>>> > you have any idea to fix this? >>>>>> >>>>>> I ran into this exact issue. Check /etc/resolv.conf on the redundant >>>>>> server and make sure you have known good nameservers. Somehow my proxy >>>>>> had a garbage entry in there which prevented it getting config from >>>>>> the >>>>>> core sipxecs server - I removed the bad line and everything worked >>>>>> fine. >>>>>> >>>>>> - -- >>>>>> ================================================================== >>>>>> Joe Micciche [email protected] >>>>>> Red Hat, Inc. http://www.redhat.com >>>>>> Senior Communications Engineer X(81) 44554 >>>>>> +1.919.754.4554 >>>>>> ================================================================== >>>>>> -----BEGIN PGP SIGNATURE----- >>>>>> Version: GnuPG v1.4.11 (GNU/Linux) >>>>>> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ >>>>>> >>>>>> iEYEARECAAYFAk3vzlkACgkQJHjEUGX5D+GL1wCgxIstfwAA9GEitFmbi/Im3Hxa >>>>>> qaoAnRcQFg1x4jAfBTnY2AMBjnc3eS9i >>>>>> =mePE >>>>>> -----END PGP SIGNATURE----- >>>>>> _______________________________________________ >>>>>> sipx-users mailing list >>>>>> [email protected] >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>> >>>>> >>>>> _______________________________________________ >>>>> sipx-users mailing list >>>>> [email protected] >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>>> >>>> >>>> -- >>>> Michael Picher >>>> eZuce >>>> Director of Technical Services >>>> O.978-296-1005 X2015 >>>> M.207-956-0262 >>>> @mpicher <http://twitter.com/mpicher> >>>> www.ezuce.com >>>> >>>> >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> >> >> -- >> Michael Picher >> eZuce >> Director of Technical Services >> O.978-296-1005 X2015 >> M.207-956-0262 >> @mpicher <http://twitter.com/mpicher> >> www.ezuce.com >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
