Find the answer to your Linux question:
Page 4 of 5 FirstFirst 1 2 3 4 5 LastLast
Results 31 to 40 of 42
[root@kinetix]# ls -la /var/run/named total 8 drwxr-xr-x 2 named named 4096 Jan 26 2003 ./ drwxr-xr-x 11 root root 4096 May 9 21:12 ../ [root@kinetix]# ps -Af | grep 'named' ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #31
    Just Joined!
    Join Date
    May 2005
    Posts
    5

    [root@kinetix]# ls -la /var/run/named
    total 8
    drwxr-xr-x 2 named named 4096 Jan 26 2003 ./
    drwxr-xr-x 11 root root 4096 May 9 21:12 ../

    [root@kinetix]# ps -Af | grep 'named'
    ps: error: Conflicting format options.
    usage: ps -[Unix98 options]
    ps [BSD-style options]
    ps --[GNU-style long options]
    ps --help for a command summary

    oh crap, now ps has got problems too!? Juuuust my day today

    [root@kinetix]# service named start
    [root@kinetix]# [ OK ]

    Kewl - seems like it's fixed!!! Okie, maybe I should jump up and down just yet....

    [root@kinetix]# grep 'named' /var/log/messages | tail -n 20
    May 9 21:46:02 kinetix named[13105]: exiting (due to early fatal error)
    May 9 21:46:02 kinetix named: named startup succeeded
    May 9 22:06:57 kinetix named[20575]: starting BIND 9.2.1 -u named -c /etc/named.conf -u named -t /var/named/run-root
    May 9 22:06:57 kinetix named[20575]: using 1 CPU
    May 9 22:06:57 kinetix named[20577]: loading configuration from '/etc/named.conf'
    May 9 22:06:57 kinetix named[20577]: no IPv6 interfaces found
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface lo, 127.0.0.1#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0, 64.182.44.111#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0:1, 64.182.44.112#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0:2, 64.182.44.113#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0:3, 64.182.44.114#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0:4, 64.182.44.115#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0:5, 64.182.44.116#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0:6, 64.182.44.117#53
    May 9 22:06:57 kinetix named[20577]: listening on IPv4 interface eth0:7, 64.182.44.118#53
    May 9 22:06:57 kinetix named[20577]: command channel listening on 127.0.0.1#953
    May 9 22:06:57 kinetix named[20577]: could not open entropy source /dev/random: file not found
    May 9 22:06:57 kinetix named[20577]: couldn't open pid file '/var/run/named/named.pid': Permission denied
    May 9 22:06:57 kinetix named[20577]: exiting (due to early fatal error)
    May 9 22:06:57 kinetix named: named startup succeeded
    [root@kinetix]#

    Seems that it's okay, except for the named.pid file...

  2. #32
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230
    Looks like the init script is configured to use chroot. Do you want to use chroot or not?

  3. #33
    Just Joined!
    Join Date
    May 2005
    Posts
    5
    Okay, first of all, let me tell you about my setup:

    My server is RedHat 9, upgraded from RH7.2. Now, my business is a webhosting company, based in South Africa. I installed Plesk 7.1.7 as a control panel. With the installation, it installed chroot aswell, but I don't quite know how to check for it - all I can make out is: (if it'll help)

    [root@kinetix]# find / -name chroot -print
    /home/httpd/vhosts/chroot
    find: /proc/1104: No such file or directory
    find: /proc/1109/fd: No such file or directory
    /usr/sbin/chroot
    [root@kinetix]#

    Like I said, I'm new this scene and like to learn as much as I can. Do you thing chroot is a good or bad thing? If it's a good thing, I don't mind using it, otherwise I'll go without it. Then again, maybe Plesk do rely on chroot...

  4. #34
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230

    * SilentRage shrugs

    we'll work with it.

    First off, we'll make sure your chroot devices are properly setup. Some of the below commands might ***** about a file existing, but that's ok.

    mkdir /var/named/run-root/dev
    chgrp named /var/named/run-root/dev
    chmod 774 /var/named/run-root/dev
    mknod -m 644 /var/named/run-root/dev/null c 1 3
    mknod -m 644 /var/named/run-root/dev/zero c 1 5
    mknod -m 644 /var/named/run-root/dev/random c 1 8

    Now we'll fix the pid file problem.

    mkdir -p /var/named/run-root/var/run/named
    chgrp -R named /var/named/run-root/var/run
    chmod -R 770 /var/named/run-root/var/run
    chown named /var/named/run-root/var/run/named

    Now we'll make sure BIND is stopped, and restarted

    service named restart

    Show me the grep/tail of your logs again.

  5. #35
    Just Joined!
    Join Date
    May 2005
    Posts
    5
    [root@kinetix]# service named restart [ OK ]
    Stopping named:
    [root@kinetix src]# service named status [ OK ]
    number of zones: 7
    debug level: 0
    xfers running: 0
    xfers deferred: 0
    soa queries in progress: 0
    query logging is OFF
    server is up and running
    [root@kinetix]#

    Silent dewd - you're the man!!!!

    [root@kinetix]# grep 'named' /var/log/messages| tail -n 20
    May 9 23:14:56 kinetix named[12373]: loading configuration from '/etc/named.conf'
    May 9 23:14:56 kinetix named[12373]: no IPv6 interfaces found
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface lo, 127.0.0.1#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0, 64.182.44.111#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0:1, 64.182.44.112#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0:2, 64.182.44.113#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0:3, 64.182.44.114#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0:4, 64.182.44.115#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0:5, 64.182.44.116#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0:6, 64.182.44.117#53
    May 9 23:14:56 kinetix named[12373]: listening on IPv4 interface eth0:7, 64.182.44.118#53
    May 9 23:14:56 kinetix named[12373]: command channel listening on 127.0.0.1#953
    May 9 23:14:56 kinetix named[12373]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
    May 9 23:14:56 kinetix named[12373]: zone 44.182.64.in-addr.arpa/IN: loaded serial 1114796611
    May 9 23:14:56 kinetix named[12373]: zone beltingstructure.com/IN: loaded serial 1114846638
    May 9 23:14:56 kinetix named[12373]: zone dancenet.co.za/IN: loaded serial 1114851170
    May 9 23:14:56 kinetix named[12373]: zone kinetix.co.za/IN: loaded serial 1114796611
    May 9 23:14:56 kinetix named[12373]: running
    May 9 23:14:56 kinetix named[12373]: zone kinetix.co.za/IN: sending notifies (serial 1114796611)
    May 9 23:14:56 kinetix named: named startup succeeded
    [root@kinetix]#

    Hell yeah!!! Thank you, thank you, thank you!!!!! You're a REAL life saver!!! Many, many, many thanx!!!!

  6. #36
    Just Joined!
    Join Date
    May 2005
    Location
    Boston
    Posts
    3
    Figured I'd jump in here. Recent reader, first-time poster.

    I've been reading all of the various DNS problems here, but I think I have a new one. Here's unadulterated I/O:

    [root@tta root]# ps -ef | grep named
    [root@tta root]# /sbin/service named start
    [root@tta root]# ps -ef | grep named
    [root@tta root]# /etc/init.d/named start
    [root@tta root]# ps -ef | grep named
    [root@tta root]# /usr/sbin/named -u named
    [root@tta root]# ps -ef | grep named
    [root@tta root]# tail -200 /var/log/messages | grep named
    [root@tta root]#

    Essentially, named isn't running, I cannot seem to start it, I get no feedback when attempting to do so, and get nothing in the system log.

    A little background -- I'm a Linux novice, but not a newbie. I know enough to be dangerous, I suppose. *grin*

    Oh, and it's RedHat 9.0 running at a virtual dynamic server provider.

    Any help anyone could lend would be much appreciated (though I must admit that this is mostly a challenge for SilentRage). Thanks in advance!

  7. #37
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230
    You got your tail messages a little backwards. You should grep the entire file for the last 20 messages that relate with BIND. I like to use this command:

    grep 'named' /var/log/messages | tail -n 20

    But that's beside the point. If you checked out the last 200 messages right after attempting to start BIND, then it is pretty likely no messages was posted about BIND's attempt to start.

    First, we'll try an alternate method of seeing if the DNS server is running:
    netstat -an | grep ':53'

    Second, we'll start BIND in the foreground to see what's up:
    /usr/sbin/named -u named -g

    Show me the results for the above commands.

  8. #38
    Just Joined!
    Join Date
    May 2005
    Location
    Boston
    Posts
    3
    [root@tta root]# netstat -an | grep ':53'
    [root@tta root]# /usr/sbin/named -u named -g
    May 27 10:56:53.336 starting BIND 9.2.1 -u named -g
    May 27 10:56:53.337 using 1 CPU
    May 27 10:56:53.379 loading configuration from '/etc/named.conf'
    May 27 10:56:53.380 none:0: open: /etc/named.conf: file not found
    May 27 10:56:53.380 loading configuration: file not found
    May 27 10:56:53.380 exiting (due to fatal error)
    [root@tta root]#

    I am indeed missing /etc/named.conf. I checked the setup of another server I have access to, and Googled a bit, but I'm finding conflicting info on how to create this file. The other server I have access to includes a line about how it was auto-created by named-bootconf, but Googling brought up instructions on how to create it manually.

    Is there a recommended method?

  9. #39
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230
    yeah, you can grab a well-commented named.conf I wrote:
    http://www.dollardns.net/bind/named.conf

    Feel free to browse around in that bind directory for other example configs and files.

    We could also search for the presence of a named.conf with this command:
    find / -name named.conf

    P.S.: I corrected the grep/tail command in my previous post.

  10. #40
    Just Joined!
    Join Date
    May 2005
    Location
    Boston
    Posts
    3
    Wow. You do the community a great service.

    I built my files based on the examples you gave and named now starts just fine.

    Thanks a million!

Page 4 of 5 FirstFirst 1 2 3 4 5 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •