Hi Nick
i tried a the logs for error & fatal after reconfiguring the farm and
application.
but there isn't any error or fatal logs..

---*** please note that the first created application DNS zone status
is still sowing the status as "Pending delete"***---

is there any other package that concern with the updating of the
named.conf?





On Jul 30, 3:02 pm, Nickolas Toursky <[email protected]> wrote:
> Kiran,
>
> CONNECTION is an internal libssh string, this is ok.
>
> Please keep enabled only ERROR and FATAL log levels and post messages here.
>
> Nick
>
> 2009/7/30 kiran <[email protected]>:
>
>
>
> > Hi Nick,
> > Here is the details of the Crontab for DNS
> > ---------
> > */6 * * * * /usr/bin/php -q /var/scalr/app/cron/cron.php --
> > DNSMaintenance
> > */3 * * * * /usr/bin/php -q /var/scalr/app/cron/cron.php --
> > DNSZoneListUpdate
> > ---------
> > while manually execution of the script the exit status yields "0". But
> > doen't updates the named.conf
>
> > +=+=+=+=+=+=+
>
> > And the system Logs for Errors in admin CP, go to Logs ->
> > System log yields no results...
>
> > How ever the Log level "Information" gives the following details for
> > DNS zone
> > --------------
> > 546316          INFO    2009-07-29 16:04:38     Updating ns1.ourdomain.net 
> > DNS
> > zone
> > 546317  DEBUG   2009-07-29 16:04:38     Add lock for 'ns1.ourdomain.net'
> > zone.
> > 546318  INFO    2009-07-29 16:04:38     Open stream to: ssh2.sftp://
> > CONNECTION/etc/bind/named.conf
> > 546319  INFO    2009-07-29 16:04:38     Reading: /etc/bind/named.conf
> > 546320  INFO    2009-07-29 16:04:38     Execute rndc reload
> > 546321  DEBUG   2009-07-29 16:04:38     Unlocking zone 12
> > --------------
> > But this doesn't updates the named.conf.
>
> > ********* could u please note there the "Open stream to: ssh2.sftp://
> > CONNECTION/etc/bind/named.conf".*******
> > is that term "CONNECTION" makes failure to update the named.conf?
> > if so please tell me that how to change the 
> > sftp://CONNECTION/etc/bind/named.conf
> > to sftp://<myip>/etc/bind/named.conf
>
> > On Jul 30, 12:54 pm, Nickolas Toursky <[email protected]> wrote:
> >> Hi Kiran,
>
> >> Make sure you have scheduled DNSZoneListUpdate cron job execution, as
> >> described in installation manual.
>
> >> After its execution, expect System log (in admin CP, go to Logs ->
> >> System log) for errors.
>
> >> Nick
>
> >> 2009/7/29 kiran <[email protected]>:
>
> >> > Hi
> >> >  While creating the new application scalr creates the new zone file
> >> > with Elastic IP.but the named.conf file is not updating. so the
> >> > application is not resolving internaly/externaly.
>
> >> > Bind configuration:
> >> > "The default user is bind. the owner ship of all bind related files is
> >> > given to bind and the user bind has got ssh access with a valid
> >> > shell". I have given the details in settings --> Nameserver
> >> > configuration of scalr too
>
> >> > After creating the application, the DNS Zone status in scalr for this
> >> > respective application shows as "Pending Create".
>
> >> > To achieve the goal of running instance in scalr is only pending due
> >> > to this DNS update.
> >> > any help or hint will be greatly thankful :-)
>
> >> > //Kiran

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to