• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Is it safe to run up2date on RHEL3 and Plesk 8

C

carliebentley

Guest
Before I do this I want to know it's not going to wipe out a bunch of stuff or break a bunch of my sites.

I'm runnin RHEL3, and Plesk 8, that has has all the autoinstaller Plesk updates.

There are several things I want to Update, including:
1. Perl to 5.8.0
- perl-CGI to 2.89
- perl-CPAN to 1.61
- perl-DBD-MySQL to 2.1021
- perl-DB_File to 1.806
- perl-XML-Parser to 2.31
2. Wget to 1.10.2
3. php to 4.3.2
- php-imap to 4.3.2
- php-ldap to 4.3.2
- php-mysql to 4.3.2
- php-pgsql to 4.3.2
4. mysql-devel to 3.23.58
5. httpd to 2.0.46
6. python to 2.2.3
- python-devel to 2.2.3
7. spamassassin to 2.55

I plan on running up2date for each package individually. I'm nervous about doing a bulk update.

Is there anything in that list that will break Plesk's back? Or any of the 200 php based sites?

Thanks.
 
You can just use up2date to keep your system up to date. I'd even recommend it, not running up2date leaves you with a lot of vulnerable packages/services after a while...
 
Well, everything except BIND/NAMED!!!!!!!!!!!!!!

up2date worked well on everything except Bind.

Which it completely destroyed.

I'm struggling with the following:

Here's the message Log:

--
starting BIND 9.2.4
Sep 25 22:39:28 server named[15331]: using 1 CPU
Sep 25 22:39:28 server named[15331]: loading configuration from '/etc/named.conf'
Sep 25 22:39:28 server named[15331]: no IPv6 interfaces found
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface lo, 127.0.0.1#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0, 67.15.14.68#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:1, 67.15.15.210#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:2, 67.15.15.211#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:3, 67.15.15.212#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:4, 67.15.15.213#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:5, 67.15.15.214#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:6, 67.15.15.215#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:7, 67.15.15.216#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:29 server named[15331]: command channel listening on 127.0.0.1#953
Sep 25 22:39:29 server named[15331]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Sep 25 22:39:29 server named[15331]: exiting (due to early fatal error)
--


Here's the opening portion of named.conf

options {
allow-recursion {
localnets;
};
directory "/var";
auth-nxdomain no;
pid-file "/var/run/named/named.pid";
};

//Use with the following in named.conf, adjusting the allow list as needed:

key "rndc-key" {
algorithm hmac-md5;
secret "XXXXXXXXXXXXXXXXXXXXXXI know this is rightXXXXXXXXX";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};


Then it starts detailing the zones.
--

Here's the rndc.conf

options {
default-server localhost;
default-key "rndc-key";
};

server localhost {
key "rndc-key";
};

key "rndc-key" {
algorithm hmac-md5;
secret "XXXXXXXXXXXXXXXXXXXXXXI know this is rightXXXXXXXXX";
};

--

And just to make certain here's the rndc.key

key "rndc-key" {
algorithm hmac-md5;
secret "XXXXXXXXXXXXXXXXXXXXXXI know this is rightXXXXXXXXX";
};

--

And Yet I still get the following error when I try to launch named.

Sep 25 22:39:29 server named[15331]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Sep 25 22:39:29 server named[15331]: exiting (due to early fatal error)


If I ever get this fixed, I may not open an ssh terminal again. It's really very frustrating.
 
I've heard of a problem where bind-chroot was installed. If you have the bind-chroot package on your box do the following:

Code:
# rpm -e bind-chroot
# ln -s /var/named/run-root/etc/named.conf /etc/named.conf
# service named start
 
I finally got this figured out.

The named.conf file was really broken because of a simple }; out of place.

No more up2dates on this, unless I go with ARTs.
 
Back
Top