The service “nameserver” appears to be down.

[Willianix]

Hello!

I am receiving the emails below every 10 to 5 minutes.

What can be done for resolution?

Server	panel.onetele.com.br
Primary IP Address	128.201.164.225
Service Name	nameserver
Service Status	failed
Notification	The service “nameserver” appears to be down.
Service Check Method	The system’s command to check or to restart this service failed.
Number of Restart Attempts	2,750
Service Check Raw Output	STDOUT: file /etc/redhat-release is not owned by any package STDERR: rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages database in /var/lib/rpm rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages database in /var/lib/rpm Cpanel::Exception::ProcessFailed::Error/(XID 7564na) “/bin/rpm” reported error code “1” when it ended: rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages database in /var/lib/rpm rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages database in /var/lib/rpm at /usr/local/cpanel/Cpanel/ChildErrorStringifier.pm line 150. Cpanel::ChildErrorStringifier::die_if_error(Cpanel::SafeRun::Object=HASH(0x2a7a950)) called at /usr/local/cpanel/Cpanel/SafeRun/Object.pm line 538 Cpanel::SafeRun::Object::new_or_die("Cpanel::SafeRun::Object", "program", "/bin/rpm", "args", ARRAY(0x2a21b10), "timeout", 15, "read_timeout", ...) called at /usr/local/cpanel/Cpanel/GenSysInfo.pm line 247 Cpanel::GenSysInfo::_run_with_timeout("/bin/rpm", "--query", "--nosignature", "--nodigest", "--queryformat", "%{NAME} %{VERSION}\\n", "--file", "/etc/redhat-release") called at /usr/local/cpanel/Cpanel/GenSysInfo.pm line 187 Cpanel::GenSysInfo::_get_rpm_distro_version_arch() called at /usr/local/cpanel/Cpanel/GenSysInfo.pm line 107 Cpanel::GenSysInfo::_get_new_conf(HASH(0x2a8a918)) called at /usr/local/cpanel/Cpanel/GenSysInfo.pm line 51 Cpanel::GenSysInfo::run() called at /usr/local/cpanel/Cpanel/GenSysInfo.pm line 71 Cpanel::GenSysInfo::get_rpm_distro_version() called at /usr/local/cpanel/Cpanel/ServiceManager/Services/Pdns.pm line 23 Cpanel::ServiceManager::Services::Pdns::__ANON__(Cpanel::ServiceManager::Services::Pdns=HASH(0x2a2b228)) called at (eval 8) line 22 Cpanel::ServiceManager::Services::Pdns::pidfile(Cpanel::ServiceManager::Services::Pdns=HASH(0x2a2b228)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 1139 Cpanel::ServiceManager::Base::get_status_string(Cpanel::ServiceManager::Services::Pdns=HASH(0x2a2b228)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 1156 Cpanel::ServiceManager::Base::status(Cpanel::ServiceManager::Services::Pdns=HASH(0x2a2b228)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 1106 Cpanel::ServiceManager::Base::check(Cpanel::ServiceManager::Services::Pdns=HASH(0x2a2b228)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 1094 Cpanel::ServiceManager::Base::check_with_message(Cpanel::ServiceManager::Services::Pdns=HASH(0x2a2b228)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 600 Cpanel::ServiceManager::Base::run_from_argv(Cpanel::ServiceManager::Services::Pdns=HASH(0x2a2b228), "--verbose", "--check", "--notconfigured-ok") called at bin/restartsrv_base.pl line 145 scripts::restartsrv_base::__ANON__() called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/Try/Tiny.pm line 97 eval {...} called at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/Try/Tiny.pm line 88 Try::Tiny::try(CODE(0x29e7e60), Try::Tiny::Catch=REF(0xc66f48)) called at bin/restartsrv_base.pl line 185 scripts::restartsrv_base::run("--check", "--notconfigured-ok") called at bin/restartsrv_base.pl line 80 The subprocess “/usr/local/cpanel/scripts/restartsrv_named” reported error number 255 when it ended.
Startup Log	No startup log
Memory Information	Used 772 MB Available 1.2 GB Installed 1.96 GB
Load Information	0.00 0.01 0.00
Uptime	281 days, 13 hours, 36 minutes, and 3 seconds
IOStat Information	avg-cpu: %user %nice %system %iowait %steal %idle 0.45 0.05 0.34 0.90 0.00 98.27 Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn sda 2.62 15.21 51.31 370075074 1248168140 dm-0 6.79 15.15 51.25 368478372 1246787968 dm-1 0.02 0.07 0.06 1589128 1376976
Top Processes	PID​ Owner​ CPU %​ Memory %​ Command​ 6070 root 0.45 0.52 cPhulkd - processor - http socket 6071 root 0.23 0.19 dovecot/auth -w 6054 dovecot 0.19 0.20 dovecot/auth 27740 mysql 0.04 6.79 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/log/mysqld.log --open-files-limit=10000 --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/lib/mysql/mysql.sock 2697 root 0.04 1.23 cpsrvd (SSL) - waiting for connections

 

[cPRex]

Hey there! The first thing I would try with that error is the following commands:

yum clean all
yum update
/scripts/upcp --force

since there are many Yum issues mentioned in that output. Can you try that and see if the server is able to update?

 

[Willianix]

The command /scripts/upcp --force ran normally. The other two did not. Here are the returns.

[[email protected] ~]# yum clean all
rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library
erro: erro db3 (-30974) de dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
erro: não foi possível abrir o índice Packages usando o db3 - (-30974)
erro: não foi possível abrir o banco de dados de pacotes em /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed
[[email protected] ~]#
[[email protected] ~]#
[[email protected] ~]# yum update
rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library
erro: erro db3 (-30974) de dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
erro: não foi possível abrir o índice Packages usando o db3 - (-30974)
erro: não foi possível abrir o banco de dados de pacotes em /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed
[[email protected] ~]#

------------------------------------------------
[[email protected] ~]# yum update
rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library
erro: erro db3 (-30974) de dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
erro: não foi possível abrir o índice Packages usando o db3 - (-30974)
erro: não foi possível abrir o banco de dados de pacotes em /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed
[[email protected] ~]# /scripts/upcp --force
[2022-05-17 16:07:49 -0300] Detected cron=0 (--force passed on command line)
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (8329) at Tue May 17 16:07:49 2022
[2022-05-17 16:07:49 -0300] Detected cron=0 (--force passed on command line)
[2022-05-17 16:07:49 -0300] 1% complete
[2022-05-17 16:07:49 -0300] 2% complete
[2022-05-17 16:07:49 -0300] mtime on upcp is 1576180127 (Thu Dec 12 16:48:47 2019)
----------------------------------------------------------------------------------------------------
=> Log opened from /usr/local/cpanel/scripts/updatenow (8330) at Tue May 17 16:07:49 2022
[2022-05-17 16:07:49 -0300] Running version '11.84.0.18' of updatenow.
[2022-05-17 16:07:49 -0300] Detected version '11.84.0.18' from version file.
[2022-05-17 16:07:49 -0300] --force passed on command line. Upgrade will disregard update config settings.
[2022-05-17 16:07:55 -0300] Target version set to '11.102.0.15'
[2022-05-17 16:07:55 -0300] First upgrading to 11.86.0.40 before upgrading to final version.
[2022-05-17 16:07:55 -0300] Switching to version 11.86.0.40 of updatenow to determine if we can reach that version without failure.
[2022-05-17 16:07:55 -0300] ***** FATAL: Failed to download updatenow.static from server: (XID ypnq9e) “/bin/rpm” reported error code “1” when it ended: rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library
[2022-05-17 16:07:55 -0300] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2022-05-17 16:07:55 -0300] error: cannot open Packages index using db3 - (-30974)
[2022-05-17 16:07:55 -0300] error: cannot open Packages database in /var/lib/rpm
[2022-05-17 16:07:55 -0300] rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library
[2022-05-17 16:07:55 -0300] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2022-05-17 16:07:55 -0300] error: cannot open Packages database in /var/lib/rpm
[2022-05-17 16:07:55 -0300] rpmdb: Thread/process 25373/47633502635168 failed: Thread died in Berkeley DB library
[2022-05-17 16:07:55 -0300] error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
[2022-05-17 16:07:55 -0300] error: cannot open Packages database in /var/lib/rpm
[2022-05-17 16:07:55 -0300] The Administrator will be notified to review this output when this script completes
=> Log closed Tue May 17 16:07:55 2022
[2022-05-17 16:07:55 -0300] 17% complete
=> Log closed Tue May 17 16:07:55 2022
----------------------------------------------------------------------------------------------------
=> Log opened from /usr/local/cpanel/scripts/maintenance (8341) at Tue May 17 16:07:55 2022
=> Log closed Tue May 17 16:07:55 2022
----------------------------------------------------------------------------------------------------
=> Log opened from cPanel Update (upcp) - Slave (8329) at Tue May 17 16:07:55 2022
[2022-05-17 16:07:55 -0300] E Pre Maintenance ended, however it did not exit cleanly (65280). Please check the logs for an indication of what happened
=> Log closed Tue May 17 16:07:56 2022
[2022-05-17 16:07:56 -0300] 95% complete
[2022-05-17 16:07:56 -0300] 100% complete
[2022-05-17 16:07:56 -0300]
[2022-05-17 16:07:56 -0300] cPanel update completed
[2022-05-17 16:07:56 -0300] A log of this update is available at /var/cpanel/updatelogs/update.1652814468.log
[2022-05-17 16:07:56 -0300] Removing upcp pidfile
[2022-05-17 16:07:56 -0300]
[2022-05-17 16:07:56 -0300] Completed all updates
=> Log closed Tue May 17 16:07:56 2022
[[email protected] ~]#

 

[cPRex]

Thanks for that output. Can you run the following commands and let me know what those say?

ls -ld /var
ls -ld /var/lib
ls -ld /var/lib/rpm

I'm expecting to find something similar to this output:

# ls -ld /var
drwxr-xr-x. 25 root root 4096 May 17 13:23 /var
[[email protected] /]# ls -ld /var/lib
drwxr-xr-x. 41 root root 4096 Apr 26 16:18 /var/lib
[[email protected] /]# ls -ld /var/lib/rpm
drwxr-xr-x. 2 root root 4096 May 17 13:23 /var/lib/rpm

 

[Willianix]

Aqui estão os retornos.

[[email protected] ~]# ls -ld /var
drwxr-xr-x. 24 raiz raiz 4096 Dez 26 2019 /var
[[email protected] ~] #
[[email protected] ~]# ls -ld /var/lib
drwxr-xr-x. 41 raiz raiz 4096 Mai 17 03:46 /var/lib
[[email protected] ~] #
[[email protected] ~]# ls -ld /var/lib/rpm
drwxr-xr-x. 2 raiz raiz 4096 Ago 9 2021 /var/lib/rpm
[[email protected] ~] #

 

[cPRex]

That all looks normal to me. Can you try running the WHM >> Rebuild RPM Database tool to see if that works well?

 

[Willianix]

Após conclusão às 16:58PM não recebi mais e-mail de falha.
Segue abaixo e-mail da conclusão.

The service “nameserver” is now operational.

Server panel.onetele.com.br Primary IP Address 128.201.164.225 Service Name nameserver Service Status recovered Notification The service “nameserver” is now operational. Service Check Raw Output The 'pdns' service passed the check: pdns (/usr/sbin/pdns_server --daemon --guardian=yes) is running as root with PID 11614 (pidfile+/proc check method). Startup Log No startup log Memory Information Used 775 MB Available 1.2 GB Installed 1.96 GB Load Information 0.01 0.05 0.01 Uptime 281 days, 15 hours, 55 minutes, and 50 seconds IOStat Information avg-cpu: %user %nice %system %iowait %steal %idle 0.45 0.05 0.34 0.90 0.00 98.27 Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn sda 2.62 15.21 51.31 370237066 1248701708 dm-0 6.79 15.15 51.25 368640276 1247321536 dm-1 0.02 0.07 0.06 1589216 1376976 Top Processes PID​ Owner​ CPU %​ Memory %​ Command​ 9724 root 0.22 0.52 cPhulkd - processor - http socket 9725 root 0.22 0.19 dovecot/auth -w 9712 dovecot 0.18 0.20 dovecot/auth 27740 mysql 0.04 6.79 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/log/mysqld.log --open-files-limit=10000 --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/lib/mysql/mysql.sock 2697 root 0.04 1.23 cpsrvd (SSL) - waiting for connections Configure Monitor Settings: https://panel.onetele.com.br:2087/scripts/srvmng#service-chkservd Configure chkservd: https://panel.onetele.com.br:2087/scripts2/tweaksettings?find=chkservd Disable HTML notifications: https://panel.onetele.com.br:2087/scripts2/tweaksettings?find=chkservd_plaintext_notify Disable recovery notifications: https://panel.onetele.com.br:2087/scripts2/tweaksettings?find=skip_chkservd_recovery_notify The system generated this notice on Tuesday, May 17, 2022 at 7:58:07 PM UTC. “Service failures (ChkServd)” notifications are currently configured to have an importance of “High”. You can change the importance or disable this type of notification in WHM’s Contact Manager at: https://panel.onetele.com.br:2087/scripts2/editcontact?event=chkservd Do not reply to this automated message.

 

[cPRex]

That's good news! Let me know if you run into any other problems.