Resolved Named won't start

[SlimIT]

Hello,

All my client websites are down because named won't start, here is the error i'm getting:

[root@plesk1 slimit]# service named start
Redirecting to /bin/systemctl start named.service
Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.

[root@plesk1 slimit]# systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-09-19 16:48:51 CET; 11s ago
Process: 12380 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=127)
Process: 12377 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)

Sep 19 16:48:51 plesk1.nebras-hosting.com bash[12377]: zone 115.255.51.in-addr.arpa/IN: loaded serial 1505828963
Sep 19 16:48:51 plesk1.nebras-hosting.com bash[12377]: zone advice-aster.com/IN: loaded serial 2017041501
Sep 19 16:48:51 plesk1.nebras-hosting.com bash[12377]: zone webuzz.tn/IN: loaded serial 2017070102
Sep 19 16:48:51 plesk1.nebras-hosting.com bash[12377]: zone yossdesign.com/IN: loaded serial 2016102609
Sep 19 16:48:51 plesk1.nebras-hosting.com bash[12377]: zone zidane.tn/IN: loaded serial 2017040601
Sep 19 16:48:51 plesk1.nebras-hosting.com named[12380]: /usr/sbin/named: symbol lookup error: /usr/sbin/named: undefined symbol: dns_dyndb_arguments_create
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: named.service: control process exited, code=exited status=127
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: Unit named.service entered failed state.
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: named.service failed.

Can you please help ?

Thanks.

 

[SlimIT]

Also I think that the main problem is that yum couldn't make upgrade properly.

s
Error: Package: alt-php71-tidy-7.1.9-2.el7.x86_64 (cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
Error: Package: alt-php56-tidy-5.6.31-2.el7.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
Error: Package: alt-php53-tidy-5.3.29-53.el7.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
Error: Package: alt-php52-tidy-5.2.17-103.el7.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
Error: Package: alt-php70-tidy-7.0.23-2.el7.x86_64 (cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
Error: Package: alt-php51-tidy-5.1.6-77.el7.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
Error: Package: alt-php54-tidy-5.4.45-37.el7.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
Error: Package: 1:alt-php55-tidy-5.5.38-19.el7.x86_64 (@cloudlinux-x86_64-server-7)
Requires: libtidy-0.99.so.0()(64bit)
Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
libtidy-0.99.so.0()(64bit)
Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
Not found
You could try using --skip-broken to work around the problem
** Found 334 pre-existing rpmdb problem(s), 'yum check' output follows:
1:NetworkManager-1.8.0-9.el7.x86_64 is a duplicate with 1:NetworkManager-1.4.0-20.el7_3.x86_64
1:NetworkManager-libnm-1.8.0-9.el7.x86_64 is a duplicate with 1:NetworkManager-libnm-1.4.0-20.el7_3.x86_64
abrt-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-2.1.11-45.el7.cloudlinux.x86_64
abrt-addon-ccpp-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-addon-ccpp-2.1.11-45.el7.cloudlinux.x86_64
abrt-addon-kerneloops-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-addon-kerneloops-2.1.11-45.el7.cloudlinux.x86_64
abrt-addon-pstoreoops-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-addon-pstoreoops-2.1.11-45.el7.cloudlinux.x86_64
abrt-addon-python-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-addon-python-2.1.11-45.el7.cloudlinux.x86_64
abrt-addon-vmcore-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-addon-vmcore-2.1.11-45.el7.cloudlinux.x86_64
abrt-addon-xorg-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-addon-xorg-2.1.11-45.el7.cloudlinux.x86_64
abrt-cli-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-cli-2.1.11-45.el7.cloudlinux.x86_64
abrt-console-notification-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-console-notification-2.1.11-45.el7.cloudlinux.x86_64
abrt-dbus-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-dbus-2.1.11-45.el7.cloudlinux.x86_64
abrt-libs-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-libs-2.1.11-45.el7.cloudlinux.x86_64
abrt-python-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-python-2.1.11-45.el7.cloudlinux.x86_64
abrt-tui-2.1.11-48.el7.cloudlinux.1.x86_64 is a duplicate with abrt-tui-2.1.11-45.el7.cloudlinux.x86_64
alt-php44-mysql-meta-1-13.el7.x86_64 is a duplicate with alt-php44-mysql-meta-1-12.4.el7.x86_64
alt-php51-mysql-meta-1-13.el7.x86_64 is a duplicate with alt-php51-mysql-meta-1-12.4.el7.x86_64
alt-php52-mysql-meta-1-22.el7.x86_64 is a duplicate with alt-php52-mysql-meta-1-21.4.el7.x86_64
alt-php53-mysql-meta-1-21.el7.x86_64 is a duplicate with alt-php53-mysql-meta-1-20.4.el7.x86_64
alt-php54-mysql-meta-1-25.el7.x86_64 is a duplicate with alt-php54-mysql-meta-1-24.4.el7.x86_64
1:alt-php54-pear-1.10.5-1.el7.noarch is a duplicate with 1:alt-php54-pear-1.9.5-1.el7.noarch
alt-php54-pear-ext-1-6.el7.noarch is a duplicate with alt-php54-pear-ext-1-4.el7.noarch
alt-php55-mysql-meta-1-22.el7.x86_64 is a duplicate with alt-php55-mysql-meta-1-21.4.el7.x86_64
1:alt-php55-pear-1.9.5-3.el7.noarch is a duplicate with 1:alt-php55-pear-1.9.5-1.el7.noarch
alt-php55-pear-ext-1-5.el7.noarch is a duplicate with alt-php55-pear-ext-1-4.el7.noarch
alt-php56-mysql-meta-1-16.el7.x86_64 is a duplicate with alt-php56-mysql-meta-1-15.4.el7.x86_64
1:alt-php56-pear-1.9.5-3.el7.noarch is a duplicate with 1:alt-php56-pear-1.9.5-1.el7.noarch
alt-php56-pear-ext-1-4.el7.noarch is a duplicate with alt-php56-pear-ext-1-1.el7.noarch
alt-php70-7.0.23-2.el7.x86_64 is a duplicate with alt-php70-7.0.21-2.el7.x86_64
alt-php70-cli-7.0.23-2.el7.x86_64 is a duplicate with alt-php70-cli-7.0.21-2.el7.x86_64
alt-php70-common-7.0.23-2.el7.x86_64 is a duplicate with alt-php70-common-7.0.21-2.el7.x86_64
alt-php70-devel-7.0.23-2.el7.x86_64 is a duplicate with alt-php70-devel-7.0.21-2.el7.x86_64
alt-php70-gd-7.0.23-2.el7.x86_64 is a duplicate with alt-php70-gd-7.0.21-2.el7.x86_64
alt-php70-ioncube-loader-10.0.1-1.el7.cloudlinux.x86_64 is a duplicate with alt-php70-ioncube-loader-6.1.0-1.el7.cloudlinux.x86_64
alt-php70-mariadb10-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-mariadb10-7.0.21-1.el7.x86_64
alt-php70-mariadb101-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-mariadb101-7.0.21-1.el7.x86_64
alt-php70-mysql5.0-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-mysql5.0-7.0.21-1.el7.x86_64
alt-php70-mysql5.1-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-mysql5.1-7.0.21-1.el7.x86_64
alt-php70-mysql5.5-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-mysql5.5-7.0.21-1.el7.x86_64
alt-php70-mysql5.6-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-mysql5.6-7.0.21-1.el7.x86_64
alt-php70-mysql5.7-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-mysql5.7-7.0.21-1.el7.x86_64
alt-php70-pdo-7.0.23-2.el7.x86_64 is a duplicate with alt-php70-pdo-7.0.21-2.el7.x86_64
alt-php70-pecl-ext-1-21.el7.x86_64 is a duplicate with alt-php70-pecl-ext-1-20.el7.x86_64
alt-php70-percona5.5-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-percona5.5-7.0.21-1.el7.x86_64
alt-php70-percona5.6-7.0.23-1.el7.x86_64 is a duplicate with alt-php70-percona5.6-7.0.21-1.el7.x86_64
alt-php71-7.1.9-2.el7.x86_64 is a duplicate with alt-php71-7.1.7-2.el7.x86_64
alt-php71-cli-7.1.9-2.el7.x86_64 is a duplicate with alt-php71-cli-7.1.7-2.el7.x86_64
alt-php71-common-7.1.9-2.el7.x86_64 is a duplicate with alt-php71-common-7.1.7-2.el7.x86_64
alt-php71-devel-7.1.9-2.el7.x86_64 is a duplicate with alt-php71-devel-7.1.7-2.el7.x86_64
alt-php71-gd-7.1.9-2.el7.x86_64 is a duplicate with alt-php71-gd-7.1.7-2.el7.x86_64
alt-php71-mbstring-7.1.9-2.el7.x86_64 is a duplicate with alt-php71-mbstring-7.1.7-2.el7.x86_64
alt-php71-pdo-7.1.9-2.el7.x86_64 is a duplicate with alt-php71-pdo-7.1.7-2.el7.x86_64
alt-php71-pecl-ext-1-7.el7.x86_64 is a duplicate with alt-php71-pecl-ext-1-6.el7.x86_64
alt-python27-cllib-1.2-51.el7.cloudlinux.x86_64 has installed conflicts lve-utils < ('0', '1.5', '48'): lve-utils-1.5-47.6.el7.cloudlinux.x86_64
alt-python27-cllib-1.2-51.el7.cloudlinux.x86_64 has installed conflicts lvemanager < ('0', '2.0', '17'): lvemanager-2.0-16.15.el7.cloudlinux.noarch
alt-python27-cllib-1.2-51.el7.cloudlinux.x86_64 is a duplicate with alt-python27-cllib-1.2-42.5.el7.cloudlinux.x86_64
atk-2.22.0-3.el7.x86_64 is a duplicate with atk-2.14.0-1.el7.x86_64
audit-libs-2.7.6-3.el7.x86_64 is a duplicate with audit-libs-2.6.5-3.el7_3.1.x86_64
bash-4.2.46-29.el7_4.x86_64 is a duplicate with bash-4.2.46-21.el7_3.x86_64
32:bind-libs-9.9.4-51.el7.x86_64 is a duplicate with 32:bind-libs-9.9.4-50.el7_3.1.x86_64
32:bind-libs-lite-9.9.4-51.el7.x86_64 is a duplicate with 32:bind-libs-lite-9.9.4-50.el7_3.1.x86_64
32:bind-license-9.9.4-51.el7.noarch is a duplicate with 32:bind-license-9.9.4-50.el7_3.1.noarch
binutils-2.25.1-32.base.el7_4.1.x86_64 is a duplicate with binutils-2.25.1-22.base.el7.x86_64
blas-3.4.2-8.el7.x86_64 is a duplicate with blas-3.4.2-5.el7.x86_64
boost-system-1.53.0-27.el7.x86_64 is a duplicate with boost-system-1.53.0-26.el7.x86_64
.................

...............

​

Any idea ?

 

[SlimIT]

The plesk auto repair tool :

I tried to use the Plesk Auto Repair utility:

[root@plesk1 slimit]# /usr/local/psa/bootstrapper/pp17.5.3-bootstrapper/bootstrapper.sh repair
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
===> Cumulative APS controller upgrade and repair (final stage) has been started.
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /usr/local/psa/bootstrapper/pp17.5.3-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Job for named-chroot.service failed because the control process exited with error code. See "systemctl status named-chroot.service" and "journalctl -xe" for details.

**** Product repair started.

===> Checking for previous installation ... found.
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

Trying to start service mariadb... active
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 017005003
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.17.5.3-17.5.3.20170919-165048.dump.gz
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
Checking for the group 'lock-manager'...
Trying to add supplementary group 'lock-manager' for user 'psaadm'... already there
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
Upgrade or repair for 'apsc' (stage 'prep') is not required
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.apsc.17.5.3-17.5.3.20170919-165102.dump.gz
===> Cumulative upgrade and repair of APS controller database has been completed.
Connection to APSC DB is possible
===> Cumulative APS controller upgrade and repair (final stage) has been started.
Upgrade or repair for 'apsc' (stage 'post') is not required
===> Cumulative upgrade and repair of APS controller (final stage) has been completed.
Trying to reset database user password for 'pma_sAk5WUah1JDG@'... done
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
Upgrade or repair for 'core' (stage 'prep') is not required
===> Preparing Plesk database upgrade (revertable stage).
Trying to resolve hostname 'plesk1.nebras-hosting.com' and validate its IP address... done

Trying to set psa database version to 017005003... done
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
===> Plesk database scheme upgrade has been completed.
done
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
Trying to upgrade and repair SpamAssassin service configuration... Upgrade or repair for 'spamassassin' (stage 'files') is not required
done
Trying to upgrade and repair Roundcube webmail configuration... Upgrade or repair for 'roundcube' (stage 'files') is not required
done
Upgrade of Roundcube Web Based mail client configs and DB is not required - no previous version
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-prep stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-prep') is not required
done
Trying to upgrade and repair Fail2Ban configuration (bootstrapper-post stage)... Upgrade or repair for 'fail2ban' (stage 'bootstrapper-post') is not required
done
Trying to upgrade and repair Firewall service configuration... Upgrade or repair for 'firewall' (stage 'post') is not required
done
Trying to stop service named-chroot... failed
done
Trying to register service named-chroot... done
Trying to start service named-chroot... failed
Sep 19 16:51:07 plesk1.nebras-hosting.com systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
Sep 19 16:51:07 plesk1.nebras-hosting.com named-checkconf[15324]: /etc/named.conf:10: change directory to '/var/named/chroot/var' failed: file not found
Sep 19 16:51:07 plesk1.nebras-hosting.com named-checkconf[15324]: /etc/named.conf:10: parsing failed
Sep 19 16:51:07 plesk1.nebras-hosting.com systemd[1]: named-chroot.service: control process exited, code=exited status=1
Sep 19 16:51:07 plesk1.nebras-hosting.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Sep 19 16:51:07 plesk1.nebras-hosting.com systemd[1]: Unit named-chroot.service entered failed state.
Sep 19 16:51:07 plesk1.nebras-hosting.com systemd[1]: named-chroot.service failed.

WARNING!
Some problems are found during start service named-chroot(see log file: /var/log/plesk/install/plesk_17.5.3_repair.log)

 

[UFHH01]

Hi SlimIT,

am I correct, when I assume, that you tried to upgrade to CentOS 7.4 ? If this assumption is correct, pls. see:

=> Question - Plesk Onyx & CentOS 7.4 compatible?​

If my assumption is incorrect, pls. consider to provide MORE informations about your statement:

Also I think that the main problem is that yum couldn't make upgrade properly

Pls. include not only a step-to-step information, WHAT you previously did, but pls. provide as well the current used operating system and your current used Plesk version ( incl. #MU ).

 

[SlimIT]

OS ‪CloudLinux 7.4 (Georgy Grechko)‬

Product Plesk Onyx

Version 17.5.3 Update #21, last updated on Sept 6, 2017 10:54 PM

 

[SlimIT]

Sorry for the long posting much responses.

I noticed that Plesk had many system updates to make but he couldn't do it.

I did the update with yum and I noticed that he has some dependencies problems.

Today I'm having problems with dns so I restarted the named service and now the DNS is not working anymore.

 

[UFHH01]

Hi SlimIT,

My OS is: CloudLinux release 7.4 (Georgy Grechko).

Did you see my answer?

If this assumption is correct, pls. see:

=> Question - Plesk Onyx & CentOS 7.4 compatible?

Actually, CentOS 7.4 is currently not yet supported, as you may read within the above mentioned thread.

 

[SlimIT]

Dear UFHH01,

I haven't updated my CloudLinux system and all is working well from a long time, could the autoupdate or the KernelCare plugin be responsible of that ?

Can you advice something to do just to let named working as it was working before ?

Now 'yum update' is looping through the dependencies until he reach limits by showing " Error Depsolving loop limit reached."

 

[UFHH01]

Hi SlimIT,

did you see the Plesk KB - article:

=> Unable to upgrade Plesk: Exception: Failed to solve dependencies: alt-php*​

... in the first place, to solve your "alt-php" issues/errors/problems ?


Afterwards, you should consider to investigate ( possible ) further issues/errors/problems, but always one at a time.

 

[SlimIT]

Yes I have done it as a first attempt.

 

[UFHH01]

Hi SlimIT,

well... you should provide ACTUAL issues/errors/problems then ( from logs or from your command line ), so that people willing to help you are up-to-date and might provide further suggestions.
As I stated before, Plesk itself doesn't offer ( yet ) support for CentOS 7.4, but you might still get help from the Plesk Community, but this requires, that you provide the essential informations to investigate a possible issue/error/problem, as there is no "works-for-all-kind-of-issues" - command, I'm afraid.

 

[UFHH01]

Pls. consider to read and follow as well:

=> Unable to start named-chroot.service: /etc/named.conf:10: change directory to '/var/named/chroot/var' failed: file not found​

 

[SlimIT]

I understand Mr. UFHH01 and I thank you for you great help.

Currently I have tried to fix yum duplicates problem with 'package-cleanup --cleandupes' and now the system have problems with many packages as shown in the attachment file 'yum_update'.

I also attached my yum repolist because when I enable CloudLinux 7 - Base yum enters a dependency resolv loop.

My main errors are:
- The 'named' service cannot start with message below and all my hosted websites dns could not be resolved:

Sep 19 16:48:51 plesk1.nebras-hosting.com named[12380]: /usr/sbin/named: symbol lookup error: /usr/sbin/named: undefined symbol: dns_dyndb_arguments_create
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: named.service: control process exited, code=exited status=127
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: Unit named.service entered failed state.
Sep 19 16:48:51 plesk1.nebras-hosting.com systemd[1]: named.service failed.

- The 'plesk' panel is working ultimely slow so I cannot change pages.

What else can I share ?

 

[SlimIT]

Another Plesk support page suggested that I change

directory "/var";

to

directory "/var/named/chroot/var";

and now I have reverted it as suggested in the thread => Unable to start named-chroot.service: /etc/named.conf:10: change directory to '/var/named/chroot/var' failed: file not found.

 

[UFHH01]

Hi SlimIT,

and ( as you read the above mentione KB - article ) did you consider to FOLLOW the provided resolutions? As I can see within your "yum update" - command, the "alt-php" - issues are still present.

Error: Package: alt-php56-tidy-5.6.31-2.el7.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
Error: Package: alt-php70-mysql5.7-7.0.22-1.el7.x86_64 (imunify360-alt-php)
           Requires: alt-php70-pdo = 7.0.22
           Installed: alt-php70-pdo-7.0.23-2.el7.x86_64 (installed)
               alt-php70-pdo = 7.0.23-2.el7
           Available: alt-php70-pdo-7.0.22-1.el7.x86_64 (imunify360-alt-php)
               alt-php70-pdo = 7.0.22-1.el7
Error: Package: alt-php53-tidy-5.3.29-53.el7.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
Error: Package: alt-php52-tidy-5.2.17-103.el7.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
Error: Package: alt-php51-tidy-5.1.6-77.el7.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
Error: Package: alt-php71-tidy-7.1.8-1.el7.x86_64 (imunify360-alt-php)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
Error: Package: alt-php71-7.1.8-1.el7.x86_64 (imunify360-alt-php)
           Requires: alt-php71-cli = 7.1.8-1.el7
           Installed: alt-php71-cli-7.1.9-2.el7.x86_64 (installed)
               alt-php71-cli = 7.1.9-2.el7
           Available: alt-php71-cli-7.1.8-1.el7.x86_64 (imunify360-alt-php)
               alt-php71-cli = 7.1.8-1.el7
Error: Package: alt-php70-tidy-7.0.22-1.el7.x86_64 (imunify360-alt-php)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
Error: Package: alt-php54-tidy-5.4.45-37.el7.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
Error: Package: alt-php70-mysql5.0-7.0.22-1.el7.x86_64 (imunify360-alt-php)
           Requires: alt-php70-pdo = 7.0.22
           Installed: alt-php70-pdo-7.0.23-2.el7.x86_64 (installed)
               alt-php70-pdo = 7.0.23-2.el7
           Available: alt-php70-pdo-7.0.22-1.el7.x86_64 (imunify360-alt-php)
               alt-php70-pdo = 7.0.22-1.el7
Error: Package: alt-php70-mysql5.1-7.0.22-1.el7.x86_64 (imunify360-alt-php)
           Requires: alt-php70-pdo = 7.0.22
           Installed: alt-php70-pdo-7.0.23-2.el7.x86_64 (installed)
               alt-php70-pdo = 7.0.23-2.el7
           Available: alt-php70-pdo-7.0.22-1.el7.x86_64 (imunify360-alt-php)
               alt-php70-pdo = 7.0.22-1.el7
Error: Package: alt-php70-mysql5.6-7.0.22-1.el7.x86_64 (imunify360-alt-php)
           Requires: alt-php70-pdo = 7.0.22
           Installed: alt-php70-pdo-7.0.23-2.el7.x86_64 (installed)
               alt-php70-pdo = 7.0.23-2.el7
           Available: alt-php70-pdo-7.0.22-1.el7.x86_64 (imunify360-alt-php)
               alt-php70-pdo = 7.0.22-1.el7
Error: Package: 1:alt-php55-tidy-5.5.38-19.el7.x86_64 (@cloudlinux-x86_64-server-7)
           Requires: libtidy-0.99.so.0()(64bit)
           Removing: libtidy-0.99.0-31.20091203.el7.x86_64 (@cloudlinux-x86_64-server-7)
               libtidy-0.99.so.0()(64bit)
           Updated By: libtidy-5.4.0-1.el7.x86_64 (PLESK_17_PHP54)
               Not found
 You could try using --skip-broken to work around the problem

 

[SlimIT]

Attached to this message are the error when trying to start 'named' and 'named-chroot' services.

 

[SlimIT]

Plesk is very slow to do such task. It takes a minute to open a page since website (having correct dns perharps from cache) are working good now.

Will this operation not delete my php packages and cause me another problem because I don't find which version is not affected by ? And my CloudLinux/imunify360 php-hardened will not be corrupted ?

The main question is why are these packages alt-php-* not resolvable ?

 

[UFHH01]

Hi SlimIT,

pls. do ONE step after the other. Currently you experience issues with "yum", which leaves your package - management with issues/errors/problems. This can result in dependent issues/errors/problems, as packages might have to be updated/upgraded first, before you are able to continue.

Will this operation not delete my php packages

As your custom installed "alt-php" - packages cause issues, it is recommended to solve such issues. The resolutions from the KB - article provide the exact steps, what you should do to solve the issues.

and cause me another problem because I don't find which version is not affected by

You might certainly re-install custom php - versions AFTERWARDS again... but in the first case, you should desire to solve the current issues, in order to be able to update/upgrade further packages on your server.

 

[SlimIT]

Ok I understand.

I have trying so but the package seems to not exist:

[root@plesk1 chroot]# rpm -e --nodeps alt-php70-mysql5.6-7.0.22-1.el7.x86_64
error: package alt-php70-mysql5.6-7.0.22-1.el7.x86_64 is not installed

 

[SlimIT]

And the biggest problem is that after the "package-cleanup --cleandupes" many core commands are not working like "sudo":

[slimit@plesk1 ~]$ sudo ls
sudo: error while loading shared libraries: libsudo_util.so.0: cannot open shared object file: No such file or directory

But I still have a root shell to perform package reinstallation process.