1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

problems with named, Plesk 7.5.4

Discussion in 'Plesk for Linux - 8.x and Older' started by zname, Aug 26, 2005.

  1. zname

    zname Guest

    0
     
    I have a serious problems with Plesk 7.5.4 on Fedore Core 3. Plesk was installed on a clean FC3 server with auto install script.

    Please advice with the following problems:

    1. During installation Plesk couldn't start named
    2. From web interface shows the following error:

    ERROR
    Unable to make action: Unable to manage service by dnsmng: dnsmng: Service named failed to start
    0: /usr/local/psa/admin/htdocs/server/restart_services.php:28 psaerror(string "Unable to make action: Unable to manage service by dnsmng: dnsmng: Service named failed to start")

    From /var/log/messages:

    Aug 26 15:27:16 localhost named[9630]: starting BIND 9.2.5 -u named -c /etc/named.conf -u named -t /var/named/run-root
    Aug 26 15:27:16 localhost named[9630]: using 1 CPU
    Aug 26 15:27:16 localhost named[9630]: loading configuration from '/etc/named.conf'
    Aug 26 15:27:16 localhost named[9630]: listening on IPv4 interface lo, 127.0.0.1#53
    Aug 26 15:27:16 localhost named[9630]: listening on IPv4 interface eth0, 192.168.1.33#53
    Aug 26 15:27:16 localhost named[9630]: command channel listening on 127.0.0.1#953
    Aug 26 15:27:16 localhost kernel: audit(1125084436.100:0): avc: denied { read } for pid=9631 exe=/usr/sbin/named name=random dev=dm-0 ino=1504912 scontext=root:system_r:named_t tcontext=root:eek:bject_r:named_zone_t tclass=chr_file
    Aug 26 15:27:16 localhost named[9630]: could not open entropy source /dev/random: permission denied
    Aug 26 15:27:16 localhost named[9630]: couldn't open pid file '/var/run/named/named.pid': Permission denied
    Aug 26 15:27:16 localhost named[9630]: exiting (due to early fatal error)
    Aug 26 15:27:16 localhost named: named startup failed
     
  2. jamesyeeoc

    jamesyeeoc Guest

    0
     
    Have you checked to see if the named.pid is actually in /var/run/named/ ?

    I would think it would be at:

    /var/named/run-root/var/run/named/named.pid

    Since the log shows it trying to start with these parameters:
    which is the path Plesk has used for quite some time.

    Also check the ownership uid/gid, should be named/named on all those dirs & files

    The error about no entropy source is no big deal.
     
  3. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    I had the exact same thing on a box last night. My problem was in the network settings in /etc/sysconfig/network-scripts/ifcfg-eth0. The upgrade did some wierd things to that file. Once I fixed them, and restarted named all was well.
     
  4. Daracne

    Daracne Guest

    0
     
    I had the same problem happen to me the other night. Fixed the problem by reinstalling the bind packages. Works like a charm now.
     
  5. jackercrack

    jackercrack Guest

    0
     
    Hi all,
    I'm having the exact same issue as above and wonder if someone could walk me through fixing it.

    I did an up2date -u followed by an autoupdate pf plask from 7.5.3 to 7.5.4

    I didn't realize that named wasn't starting until hours later so I don't know what broke it...but this is what I get in my log.

    Feb 16 08:02:46 www named[1281]: starting BIND 9.2.4 -u named -c /etc/named.conf -u named -t /var/named/run-root
    Feb 16 08:02:46 www named[1281]: using 1 CPU
    Feb 16 08:02:46 www named[1281]: loading configuration from '/etc/named.conf'
    Feb 16 08:02:46 www named[1281]: no IPv6 interfaces found
    Feb 16 08:02:46 www named[1281]: listening on IPv4 interface lo, 127.0.0.1#53
    Feb 16 08:02:46 www named[1281]: listening on IPv4 interface eth0, XXX.XXX.XXX.XXX#53
    Feb 16 08:02:46 www named[1281]: listening on IPv4 interface eth0:1, XXX.XXX.XXX.XXX#53
    Feb 16 08:02:46 www named[1281]: listening on IPv4 interface eth0:2, XXX.XXX.XXX.XXX#53
    Feb 16 08:02:46 www named[1281]: listening on IPv4 interface eth0:3, XXX.XXX.XXX.XXX#53
    Feb 16 08:02:46 www named[1281]: command channel listening on 127.0.0.1#953
    Feb 16 08:02:46 www named[1281]: couldn't open pid file '/var/run/named.pid': Permission denied
    Feb 16 08:02:46 www named[1281]: exiting (due to early fatal error)
    Feb 16 08:02:46 www named: named startup failed

    I've been working on this for about 30 hours so at some point I think I've tried everything. I'm pretty sure that premissions and symlinks are all good.

    I've tried removing the bind-libs with rpm -e and then using up2date to reinstall them.

    This didn't help.

    I also checked out my ifcfg-eth0 script and it looks ok.

    Any ideas?

    Was reinstalling bind through up2date the right thing to do? Or does plesk of it's own bind packages...if so where to I get them and how to I go about installing them. sorry if this isn't the right info you need...just let me know...I've been at this for 30 hours...so i'm a bit dinghy...:0

    Thanks in advance for any help.
     
  6. jwilf

    jwilf Guest

    0
     
    I found a solution

    I had this problem after upgrading from 7.5.1 to 7.5.2. As the log message suggests it turned out to be file permissions. This fixed it:

    chown -R named:named /var/named/run-root/var

    James
     
Loading...