dns server error

Discussion in 'General' started by Hellbound, Jul 31, 2007.

  1. Hellbound

    Hellbound New Member

    hi guys,
    this dns server is killing me,
    almost everyday it does down and I have to initiate the service start thing to bring it back online manually.


    Code:
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named restart
    Stopping named:                                            [FAILED]
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [FAILED]
    [root@host2 ~]# service named start
    Starting named:                                            [  OK  ]
    [root@host2 ~]# http://www.networkworld.com/
    
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Any errors in the logfiles under /var/log/ ?
     
  3. Hellbound

    Hellbound New Member

    Thanks for a very fast reply.

    Code:
     23231  Jul 31 21:23:40 host2 named[1832]: shutting down: flushing changes
     23232  Jul 31 21:23:40 host2 named[1832]: stopping command channel on 127.0.0.1#953
     23233  Jul 31 21:23:40 host2 named[1832]: stopping command channel on ::1#953
     23234  Jul 31 21:23:40 host2 named[1832]: no longer listening on 127.0.0.1#53
     23235  Jul 31 21:23:40 host2 named[1832]: no longer listening on 10.1.1.7#53
     23236  Jul 31 21:23:40 host2 named[1832]: exiting
     23237  Jul 31 21:23:41 host2 named[1972]: starting BIND 9.3.1 -u named -D -t /var/named/chroot
     23238  Jul 31 21:23:41 host2 named[1972]: found 2 CPUs, using 2 worker threads
     23239  Jul 31 21:23:41 host2 named[1972]: loading configuration from '/etc/named.conf'
     23240  Jul 31 21:23:41 host2 named[1972]: listening on IPv4 interface lo, 127.0.0.1#53
     23241  Jul 31 21:23:41 host2 named[1972]: listening on IPv4 interface eth0, 10.1.1.7#53
     23242  Jul 31 21:23:41 host2 named[1972]: command channel listening on 127.0.0.1#953
     23243  Jul 31 21:23:41 host2 named[1972]: command channel listening on ::1#953
     23244  Jul 31 21:23:41 host2 named[1972]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
     23245  Jul 31 21:23:41 host2 named[1972]: zone 138.52.60.in-addr.arpa/IN: loaded serial 2007073102
     23246  Jul 31 21:23:41 host2 named[1972]: zone erfani111.com/IN: loaded serial 2006112102
     23247  Jul 31 21:23:41 host2 named[1972]: zone filtercard.com/IN: loaded serial 2007062702
     23248  Jul 31 21:23:41 host2 named[1972]: zone ir-sr.com/IN: loaded serial 2007022202
     23249  Jul 31 21:23:41 host2 named[1972]: zone negahnet.com/IN: loaded serial 2007062202
     23250  Jul 31 21:23:41 host2 named[1972]: zone neguin.com/IN: loaded serial 2007062104
     23251  Jul 31 21:23:41 host2 named[1972]: zone persiansubtitle.com/IN: loaded serial 2007031702
     23252  Jul 31 21:23:41 host2 named[1972]: zone shahbazpaper.com/IN: loaded serial 2007052602
     23253  Jul 31 21:23:41 host2 named[1972]: zone zirnevis.com/IN: loaded serial 2007060303
     23254  Jul 31 21:23:41 host2 named[1972]: zone ir-sr.com.my/IN: loaded serial 2007022210
     23255  Jul 31 21:23:42 host2 named[1996]: starting BIND 9.3.1 -u named -D -t /var/named/chroot
     23256  Jul 31 21:23:42 host2 named[1996]: found 2 CPUs, using 2 worker threads
     23257  Jul 31 21:23:42 host2 named[1996]: loading configuration from '/etc/named.conf'
     23258  Jul 31 21:23:42 host2 named[1996]: listening on IPv4 interface lo, 127.0.0.1#53
     23259  Jul 31 21:23:42 host2 named[1996]: listening on IPv4 interface eth0, 10.1.1.7#53
     23260  Jul 31 21:23:42 host2 named[1996]: command channel listening on 127.0.0.1#953
     23261  Jul 31 21:23:42 host2 named[1996]: command channel listening on ::1#953
     23262  Jul 31 21:23:42 host2 named[1996]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
     23263  Jul 31 21:23:42 host2 named[1996]: zone 138.52.60.in-addr.arpa/IN: loaded serial 2007073102
     23264  Jul 31 21:23:42 host2 named[1996]: zone erfani111.com/IN: loaded serial 2006112102
     23265  Jul 31 21:23:42 host2 named[1996]: zone filtercard.com/IN: loaded serial 2007062702
     23266  Jul 31 21:23:42 host2 named[1996]: zone ir-sr.com/IN: loaded serial 2007022202
     23267  Jul 31 21:23:42 host2 named[1996]: zone negahnet.com/IN: loaded serial 2007062202
     23268  Jul 31 21:23:42 host2 named[1996]: zone neguin.com/IN: loaded serial 2007062104
     23269  Jul 31 21:23:42 host2 named[1996]: zone persiansubtitle.com/IN: loaded serial 2007031702
     23270  Jul 31 21:23:42 host2 named[1996]: zone shahbazpaper.com/IN: loaded serial 2007052602
     23271  Jul 31 21:23:42 host2 named[1996]: zone zirnevis.com/IN: loaded serial 2007060303
     23272  Jul 31 21:23:42 host2 named[1996]: zone ir-sr.com.my/IN: loaded serial 2007022210
     23273  Jul 31 21:23:43 host2 named[2022]: starting BIND 9.3.1 -u named -D -t /var/named/chroot
     23274  Jul 31 21:23:43 host2 named[2022]: found 2 CPUs, using 2 worker threads
     23275  Jul 31 21:23:43 host2 named[2022]: loading configuration from '/etc/named.conf'
     23276  Jul 31 21:23:43 host2 named[2022]: listening on IPv4 interface lo, 127.0.0.1#53
     23277  Jul 31 21:23:43 host2 named[2022]: listening on IPv4 interface eth0, 10.1.1.7#53
     23278  Jul 31 21:23:43 host2 named[2022]: command channel listening on 127.0.0.1#953
     23279  Jul 31 21:23:43 host2 named[2022]: command channel listening on ::1#953
     23280  Jul 31 21:23:43 host2 named[2022]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
     23281  Jul 31 21:23:43 host2 named[2022]: zone 138.52.60.in-addr.arpa/IN: loaded serial 2007073102
     23282  Jul 31 21:23:43 host2 named[2022]: zone erfani111.com/IN: loaded serial 2006112102
     23283  Jul 31 21:23:43 host2 named[2022]: zone filtercard.com/IN: loaded serial 2007062702
     23284  Jul 31 21:23:43 host2 named[2022]: zone ir-sr.com/IN: loaded serial 2007022202
     23285  Jul 31 21:23:43 host2 named[2022]: zone negahnet.com/IN: loaded serial 2007062202
     23286  Jul 31 21:23:43 host2 named[2022]: zone neguin.com/IN: loaded serial 2007062104
     23287  Jul 31 21:23:43 host2 named[2022]: zone persiansubtitle.com/IN: loaded serial 2007031702
     23288  Jul 31 21:23:43 host2 named[2022]: zone shahbazpaper.com/IN: loaded serial 2007052602
     23289  Jul 31 21:23:43 host2 named[2022]: zone zirnevis.com/IN: loaded serial 2007060303
     23290  Jul 31 21:23:43 host2 named[2022]: zone ir-sr.com.my/IN: loaded serial 2007022210
     23291  Jul 31 21:23:43 host2 named[2022]: D-BUS dhcdbd subscription disabled.
     23292  Jul 31 21:23:43 host2 named[2022]: D-BUS service enabled.
     23293  Jul 31 21:23:43 host2 named[2022]: running
    
    
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Strange, it just stopped loading the zones without any error message. Please post the output of:

    df -h
     
  5. Hellbound

    Hellbound New Member

    Thanks again,

    Code:
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          288G   14G  259G   6% /
    /dev/sda1              99M   23M   71M  25% /boot
    /dev/shm              244M     0  244M   0% /dev/shm
    /var/run/dbus         288G   14G  259G   6% /var/named/chroot/var/run/dbus
    [root@host2 ~]#
    
     
  6. falko

    falko Super Moderator Howtoforge Staff

    Looks ok. Are there any errors in your other logs?
    Do you use SELinux?
     
  7. Hellbound

    Hellbound New Member

    no, its disabled! how to check it again?
    Code:
    # This file controls the state of SELinux on the system.
    # SELINUX= can take one of these three values:
    #       enforcing - SELinux security policy is enforced.
    #       permissive - SELinux prints warnings instead of enforcing.
    #       disabled - SELinux is fully disabled.
    SELINUX=disabled
    # SELINUXTYPE= type of policy in use. Possible values are:
    #       targeted - Only targeted network daemons are protected.
    #       strict - Full SELinux protection.
    SELINUXTYPE=targeted
    
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Thats fine too. Currently I have no futher Ideas :confused:
     

Share This Page