Find the answer to your Linux question:
Page 3 of 5 FirstFirst 1 2 3 4 5 LastLast
Results 21 to 30 of 42
i got this: root@tux2:/etc# rndc flush rndc: connect failed: connection refused...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #21
    Just Joined!
    Join Date
    Apr 2005
    Posts
    16

    i got this:

    root@tux2:/etc# rndc flush
    rndc: connect failed: connection refused

  2. #22
    Just Joined!
    Join Date
    Apr 2005
    Posts
    16
    i did this right now:

    root@tux2:/etc# /etc/rc.d/rc.bind restart
    named: no process killed
    Starting BIND: /usr/sbin/named

    jsut wanted to let u know..incase that would matter

  3. #23
    Just Joined!
    Join Date
    Apr 2005
    Posts
    16
    i am going home right now..wil check the forum againa fter an hour...
    Thanks a lot for the help!!!

  4. #24
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230
    The reason is 1 of 2 things. Either BIND shut itself down after starting it (probably due to permissions problems now that we're using the 'named' user), or rndc is trying to connect to the wrong IP or port. So show me the results to the following commands:

    grep 'named' /var/log/messages | tail -n 20
    ps -Af | grep 'named'
    netstat -an | grep ':53'

    If ya haven't noticed, I'm a real grep fan. Now that we're running as the 'named' user, there may be some pain involved in setting some file permissions, but the pain is worth it. Never run BIND as root.

  5. #25
    Just Joined!
    Join Date
    Apr 2005
    Posts
    16
    strange but the site is working ..i think it took the changes..but i would still love to set the persmissions so next time i dont fall in this..i will try those commands in 10 minutres and let u know wht the output is...thanks a lot!!!

    wait for me

  6. #26
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230
    Yeah, the reason the site is working is cause we forcefully terminated the previous instances of BIND, and then you started it using that "rc.bind" script which runs BIND as root. BIND is humming along happily with the exception that you shouldn't run as root.

    The full restart effectively flushed your cache.

  7. #27
    Just Joined!
    Join Date
    May 2005
    Posts
    5

    Bind / Named Problem...

    Hi there. I've got the same similar problem with bind / named. I followed your steps and this is what I get:

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

    What should the permissions be? Can I just chmod the permissions? Sorry, I'm e REAL newbie to RH9 as I always work on Windows... Any help would be really appreciated.

  8. #28
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230
    That is very strange that you're missing a random device. Show me the results for the following command:

    ls -l /dev/random

    Let's also make sure you've got a pid file directory.

    ls -la /var/run/named

    And if the pid file directory did exist...

    chown -R named:named /var/run/named
    chmod -R 755 /var/run/named

  9. #29
    Just Joined!
    Join Date
    May 2005
    Posts
    5
    [root@kinetix]# ls -l /dev/random
    crw-r--r-- 1 root root 1, 8 Jan 30 2003 /dev/random

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

    There's nothing in /var/run/named - it's totally empty! Oh gr8!!!

    Okay, I did the chown -R named:named /var/run/named and chmod -R 755 /var/run/named commands anyway... juuuuust in case...

    thanx for the help SilentRage dewd - you don't know how much I appreciate your help!!!

  10. #30
    Linux Newbie
    Join Date
    Mar 2005
    Posts
    230
    The directory is supposed to be empty. I just needed it to exist. Now that you've changed the owner, let's see the results of this command again:

    ls -la /var/run/named

    And it looks like the random device exists and has the proper modes. We'll just pretend we fixed the random problem for now. I want to see if BIND is already running:

    ps -Af | grep 'named'

    If all you see is 'grep named' in the response, then I want you to start BIND like this (assuming you're using redhat):

    service named start

    Then show me that handy grep/tail of your system logs again.

Page 3 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
  •