• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

named errors when upgrading to Plesk 12.5.30

cmaxwell

Regular Pleskian
Hello,

We were testing the upgrade process from Plesk 11.5.30 to 12.5.30, and when running the upgrade the following errors were logged:

Code:
Trying to untar named run-root directory structure... mknod: `dev/random': File exists
mknod: `dev/urandom': File exists
done
Trying to set up default permissions... done
Trying to stop service named... named is stopped
done
Trying to start service named... named is stopped
Starting named:
Error in named configuration:
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
zone samstest.com/IN: NS 'ns.samstest.com' has no address records (A or AAAA)
zone samstest.com/IN: not loaded due to errors.
_default/samstest.com/IN: bad zone
zone samstest.co.uk/IN: NS 'ns.samstest.co.uk' has no address records (A or AAAA)
zone samstest.co.uk/IN: not loaded due to errors.
_default/samstest.co.uk/IN: bad zone
zone tomtester.com/IN: loaded serial 1454367889
zone bob.org/IN: loaded serial 1454368023
zone test.com/IN: loaded serial 1454368059
zone smith.uk.com/IN: loaded serial 1454517163
zone 56.168.192.in-addr.arpa/IN: loaded serial 1454517163
zone smith.co.uk/IN: loaded serial 1454517163
[FAILED]

WARNING!
Some problems are found during start service named(see log file: /var/log/plesk/install/plesk_12.5.30_installation.log)

After the upgrade the named service now fails to start.

The server is running CloudLinux Server 6.7.

Any ideas how we can fix this or is it a known issue?

Thanks,
Chris
 
Back
Top