Skip to main content

The service “nameserver” appears to be down.

Comments

7 comments

  • cPRex Jurassic Moderator
    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?
    0
  • Willianix
    The command /scripts/upcp --force ran normally. The other two did not. Here are the returns. [root@panel ~]# 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 [root@panel ~]# [root@panel ~]# [root@panel ~]# 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 [root@panel ~]# ------------------------------------------------ [root@panel ~]# 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 [root@panel ~]# /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 [root@panel ~]#
    0
  • cPRex Jurassic Moderator
    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 [root@host /]# ls -ld /var/lib drwxr-xr-x. 41 root root 4096 Apr 26 16:18 /var/lib [root@host /]# ls -ld /var/lib/rpm drwxr-xr-x. 2 root root 4096 May 17 13:23 /var/lib/rpm
    0
  • Willianix
    Aqui est"o os retornos. [root@panel ~]# ls -ld /var drwxr-xr-x. 24 raiz raiz 4096 Dez 26 2019 /var [root@panel ~] # [root@panel ~]# ls -ld /var/lib drwxr-xr-x. 41 raiz raiz 4096 Mai 17 03:46 /var/lib [root@panel ~] # [root@panel ~]# ls -ld /var/lib/rpm drwxr-xr-x. 2 raiz raiz 4096 Ago 9 2021 /var/lib/rpm [root@panel ~] #
    0
  • cPRex Jurassic Moderator
    That all looks normal to me. Can you try running the WHM >> Rebuild RPM Database tool to see if that works well?
    0
  • 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: Disable HTML notifications:
    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:
    0
  • cPRex Jurassic Moderator
    That's good news! Let me know if you run into any other problems.
    0

Please sign in to leave a comment.