• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Troubles after upgrade from 8.1.0

ToRum

New Pleskian
Hi all,

I tried to upgrade Plesk on my VE from 8.1.0 to 8.2.1. However, something went wrong. This is what the reports says:
===> Installing and configuring Named Server

Checking for the system groups and users necessary for named (bind)...
Checking for the group 'named'...
Group 'named' already exists

Checking for the user 'named'...
User 'named' already exists

Stop running named daemon

Now BIND server shutting down...

Trying to stop BIND server... done
Trying to untar named run-root directory structure... done
Trying to set up default permissions... done
mv: cannot move `/etc/sysconfig/named' to `/etc/sysconfig/named.saved_by_psa': No such file or directory

ERROR while trying to mv -f /etc/sysconfig/named /etc/sysconfig/named.saved_by_psa.01.15;11:18
Check the error reason(see log file: /tmp/psa_8.2.1_cos4.build82070918.10_upgrade.080115.11.18.log), fix and try again

Aborting...

error: %post(psa-8.2.1-cos4.build82070918.10.i586) scriptlet failed, exit status 1
Trying to install PAM module... done
Trying to establish test connection... connected
done
===> Checking database
===> Checking kernel support for iptables
Trying to establish test connection... connected
done
===> Setting up file owners
===> Installing database
===> Installing configuration files
===> Registering services
Trying to register service psa-firewall... using /sbin/chkconfig
done
===> Registering module
ERROR: An error occurred during installation of packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

In manually copied /etc/sysconfig/named to /etc/sysconfig/named.saved_by_psa.01.15. Afterwards, I was able to restart /etc/init.d/named again, but apparently it doesn't solve my problem, as all websites now redirects to /var/www/html/ (default Apache-page for CentOS) instead of the right vhost in /var/www/vhosts/xxxxx/httpdocs/.


When restarting named, I got:

[root]# /etc/init.d/named restart
Stopping named: [ OK ]
Starting named: /bin/chown: cannot access `/var/named/run-root/var/named': No such file or directory
[ OK ]
However, my /var/log/messages/ says:

Jan 15 13:18:27 myserver named[15889]: shutting down: flushing changes
Jan 15 13:18:27 myserver named[15889]: stopping command channel on 127.0.0.1#953
Jan 15 13:18:27 myserver named[15889]: no longer listening on 127.0.0.1#53
Jan 15 13:18:27 myserver named[15889]: no longer listening on xx.xx.xx.xx#53
Jan 15 13:18:27 myserver named[15889]: no longer listening on xx.xx.xx.xx#53
Jan 15 13:18:27 myserver named[15889]: no longer listening on xx.xx.xx.xx#53
Jan 15 13:18:27 myserver named[15889]: no longer listening on xx.xx.xx.xx#53
Jan 15 13:18:27 myserver named[15889]: no longer listening on xx.xx.xx.xx#53
Jan 15 13:18:27 myserver named[15889]: exiting
Jan 15 13:18:27 myserver named: succeeded
Jan 15 13:18:29 myserver named[28417]: starting BIND 9.2.4 -u named -c /etc/named.conf -u named -t /var/named/run-root
Jan 15 13:18:29 myserver named[28417]: using 1 CPU
Jan 15 13:18:29 myserver named[28417]: loading configuration from '/etc/named.conf'
Jan 15 13:18:29 myserver named[28417]: no IPv6 interfaces found
Jan 15 13:18:29 myserver named[28417]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 15 13:18:29 myserver named[28417]: listening on IPv4 interface venet0:0, xx.xx.xx.xx#53
Jan 15 13:18:29 myserver named[28417]: listening on IPv4 interface venet0:1, xx.xx.xx.xx#53
Jan 15 13:18:29 myserver named[28417]: listening on IPv4 interface venet0:2, xx.xx.xx.xx#53
Jan 15 13:18:29 myserver named[28417]: listening on IPv4 interface venet0:3, xx.xx.xx.xx#53
Jan 15 13:18:29 myserver named[28417]: listening on IPv4 interface venet0:4, xx.xx.xx.xx#53
Jan 15 13:18:29 myserver named[28417]: command channel listening on 127.0.0.1#953
Jan 15 13:18:29 myserver named[28417]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Jan 15 13:18:29 myserver named[28417]: zone xx.xx.xx.in-addr.arpa/IN: loaded serial 1199890867
Jan 15 13:18:29 myserver sshd(pam_unix)[28424]: session opened for user root by (uid=0)
Jan 15 13:18:29 myserver named[28417]: zone xx.xx.xx.in-addr.arpa/IN: loaded serial 1188457847
Jan 15 13:18:29 myserver named[28417]: zone xx.xx.xx.in-addr.arpa/IN: loaded serial 1188407468
Jan 15 13:18:29 myserver named[28417]: zone xxxxxx.be/IN: loaded serial 1199889870
...
Jan 15 13:18:30 myserver named[28417]: zone xxxxxx.be/IN: loaded serial 1192189326
Jan 15 13:18:30 myserver named: named startup succeeded
Jan 15 13:18:30 myserver named[28417]: running
Jan 15 13:18:30 myserver named[28417]: zone xxxxxxx.be/IN: sending notifies (serial 1188569277)
...
Jan 15 13:19:08 myserver named[28417]: zone xxxxxxx.be/IN: sending notifies (serial 1188569277)

which looks like a normal startup.

Can anyone help me?

Thanks a lot!
 
Hello,

In the meanwhile I was able to fix it temporary by replacing the file /etc/httpd/conf.d/zz010_psa_httpd.conf (which contained only 1 line after the failed upgrade) by a backup version of this file (I luckely had that backup!).

A Technical Support Engineer will now try to fix it definitive.
 
Back
Top