Please open a System Log, find transaction that starts with "DNSZoneListUpdate" and paste it here.
On 18.12.08 13:13, "RodneyQ" <[email protected]> wrote: > > > The default user in scalr setting is root, so it suppose to read and > append it to this file. > > -rw-r--r-- 1 bind bind 907 2008-08-27 18:42 named.conf > > On Dec 18, 5:57 pm, Alex Kovalyov <[email protected]> wrote: >> Is the path to named.conf matches the one you entered in settings? >> What does ls -al named.conf say? >> Are you able to edit the file under the user that you entered in settings? >> >> On 18.12.08 11:28, "RodneyQ" <[email protected]> wrote: >> >> >> >>> Yes, all cronjobs are set properly. It can create new zone files >>> inside the zone directory. >>> Only the named.conf is not updated(i.e. no new zones are defined >>> inside this file). >> >>> On Dec 18, 5:19 pm, Alex Kovalyov <[email protected]> wrote: >>>> the dns mgmt code has not been changed in RC3. >>>> Do you have DNSZoneListUpdate cronjob set at all? >> >>>> On 18 дек, 11:14, RodneyQ <[email protected]> wrote: >> >>>>> @Alex: I got no errors or warning the log files. >>>>> Probably some coding that updates the named.conf :) >>>>> Will try to update to RC3, hope this will get rid these error and let >>>>> you know. >>>>> Thanks Alex. >> >>>>> @Nick: my bad, I've check the version im using, it's still RC2 not >>>>> RC3. >> >>>>> Cheers, >>>>> Rodney >> >>>>> On Dec 18, 5:00 pm, Alex Kovalyov <[email protected]> wrote: >> >>>>>> File permissions? >>>>>> What does log say? >> >>>>>> On 18.12.08 10:24, "RodneyQ" <[email protected]> wrote: >> >>>>>>> Hi Alex, >> >>>>>>> Cool. we will be expecting that on the next update. >>>>>>> BTW, any ideas why the zone is not written inside named.conf as what >>>>>>> Nick also stated? >> >>>>>>> Cheers, >>>>>>> Rodney >> >>>>>>> On Dec 18, 4:05 pm, Alex Kovalyov <[email protected]> wrote: >>>>>>>> IPs are assigned from the stack and not sticking to a particular >>>>>>>> instance >>>>>>>> now. >>>>>>>> It will be resolved in the next update. >> >>>>>>>> On 18.12.08 05:08, "RodneyQ" <[email protected]> wrote: >> >>>>>>>>> Hi Again, >> >>>>>>>>> Log shows, that the IP changed to have Elastic IP, after I shutdown >>>>>>>>> the farm running for a day. something weird here :) >> >>>>>>>>> 18-12-2008 02:58:19 INFO i-c67ac3af/trap-hostdown.sh >>>>>>>>> 10.252.61.176 DOWN: Scalr notified me that 10.252.61.176 of role app >>>>>>>>> (Custom role: app, I'm first: 0) is down >>>>>>>>> 18-12-2008 02:58:17 WARN EventObserver IP changed for instance i- >>>>>>>>> c67ac3af. New IP address: 174.129.252.245 >>>>>>>>> 18-12-2008 02:58:17 WARN EventObserver IP changed for instance i- >>>>>>>>> d97ac3b0. New IP address: 174.129.249.16 >>>>>>>>> 17-12-2008 06:50:03 WARN EventObserver IP changed for instance i- >>>>>>>>> c67ac3af. New IP address: 10.252.63.48 >>>>>>>>> 17-12-2008 06:50:03 WARN EventObserver IP changed for instance i- >>>>>>>>> d97ac3b0. New IP address: 10.252.61.176 >>>>>>>>> 17-12-2008 06:47:36 INFO i-c67ac3af/mysql-init.sh Successfully >>>>>>>>> uploaded MySQL data bundle to S3. >>>>>>>>> 17-12-2008 06:47:30 INFO i-c67ac3af/mysql-init.sh Extracting MySQL >>>>>>>>> data snapshot. >> >>>>>>>>> Rodney >> >>>>>>>>> On Dec 18, 9:17 am, RodneyQ <[email protected]> wrote: >>>>>>>>>> Thanks Nick and Alex. >> >>>>>>>>>> @Nick: >>>>>>>>>> I've had to add the same lines like what you did and it >>>>>>>>>> resolves. I'm using RC3 :) >> >>>>>>>>>> @Alex: >>>>>>>>>> bind is working properly and listening on current host. Another >>>>>>>>>> problem, is internal IP is the same with its >>>>>>>>>> external IP (elastic ip checked when the instance were started) >>>>>>>>>> written in the zone. >> >>>>>>>>>> On Dec 18, 1:33 am, Alex Kovalyov <[email protected]> wrote: >> >>>>>>>>>>>> Unfortunately I cannot dig these hosts inside scalr server(but >>>>>>>>>>>> ns1.tm.local is ok). >> >>>>>>>>>>> dig sample.tm.local @localhost doesn't work but dig sample.tm.local >>>>>>>>>>> @ns1.tm.local does? >>>>>>>>>>> May be bind is not listening on localhost? >> >>>>>>>>>>> On 17.12.08 09:03, "cocoy" <[email protected]> wrote: >> >>>>>>>>>>>> I've configured scalr on ec2 and installed bind. When I launch a >>>>>>>>>>>> farm, >>>>>>>>>>>> with mysql and app server it runs ok. My internal domain is >>>>>>>>>>>> tm.local >>>>>>>>>>>> w/ ns1.tm.local set as nameserver. >> >>>>>>>>>>>> An application was created as sample.tm.local. And created the zone >>>>>>>>>>>> file: >> >>>>>>>>>>>> @ 14400 IN SOA server1.tm.local. >>>>>>>>>>>> root.server1.tm.local. >>>>>>>>>>>> ( >>>>>>>>>>>> 2008121702 ; serial, todays date+todays >>>>>>>>>>>> 14400 ; refresh, seconds >>>>>>>>>>>> 7200 ; retry, seconds >>>>>>>>>>>> 86400 ; expire, seconds >>>>>>>>>>>> 300 ) ; minimum, seconds >> >>>>>>>>>>>> sample.tm.local. 14400 IN NS server1.tm.local. >>>>>>>>>>>> ext-app 20 IN A 10.252.66.147 >>>>>>>>>>>> int-app 20 IN A 10.252.66.147 >>>>>>>>>>>> @ 90 IN A 10.252.66.176 >>>>>>>>>>>> ext-mysql 20 IN A 10.252.66.176 >>>>>>>>>>>> ext-mysql-master 20 IN A 10.252.66.176 >>>>>>>>>>>> int-mysql 20 IN A 10.252.66.176 >>>>>>>>>>>> int-mysql-master 20 IN A 10.252.66.176 >> >>>>>>>>>>>> Unfortunately I cannot dig these hosts inside scalr server(but >>>>>>>>>>>> ns1.tm.local is ok). >>>>>>>>>>>> Can you advice what's wrong with the setup? >> >>>>>>>>>>>> Thanks in advance, >>>>>>>>>>>> Rodney > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
