Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

A fatal error or timeout occurred while processing this directive

by | May 7, 2021

Wondering how to resolve ‘ A fatal error or timeout occurred while processing this directive’ error? We will help you.

As a part of our Server Management Services, our Support Engineers helps to fix similar  errors regularly.

Today, let us discuss the causes and fixes for this error.

Cause and solutions for “A fatal error or timeout occurred while processing this directive” error

 

At times, WHM/cPanel interface can give timeout errors occasionally, if there are outdated packages.

[A fatal error or timeout occurred while processing this directive.]
OR
[A warning occurred while processing this directive.]

1. Cause: This is due to the error with rpm database.

Firstly, from cPanel log in the server /usr/local/cpanel/logs/error_log

STDERR: error: rpmdb: BDB0113 Thread/process 14329/139871898372160 failed: BDB1507 Thread died in Berkeley DB library
error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db5 – (-30973)
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: BDB0113 Thread/process 14329/139871898372160 failed: BDB1507 Thread died in Berkeley DB library
error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages database in /var/lib/rpm

 

Solution

1. Firstly, we update the RPM packages using “yum update” command.

2. Then, remove all db files from rpm directory and rebuild the database:

# rm -f /var/lib/rpm/__db*
# db_verify /var/lib/rpm/Packages
# rpm –rebuilddb
# yum clean all

2. Cause:

  • Corrupt cPanel installation or template.

From cPanel log in the server /usr/local/cpanel/logs/error_log

[2021-05-03 09:57:24 +0000] die [Internal Death while parsing ./frontend/paper_lantern/ssl/install.html.tt 15562] Template::Exception:
[TYPE]=[undef]
[INFO]=[SSL::installed_hosts() failed: Unrecognized vhost: “second-addon-domain.com.customer-main-domain.com” at /usr/local/cpanel/Cpanel/Config/WebVhosts.pm line 292.

]
[TEXT]=[]
at cpanel.pl line 1267.
cpanel::cpanel::cptt_exectag(“/usr/local/cpanel/base/frontend/paper_lantern/ssl/install.htm”…, 1) called at cpanel.pl line 5226
cpanel::cpanel::run_standard_mode() called at cpanel.pl line 874
cpanel::cpanel::script(“cpanel::cpanel”, “./frontend/paper_lantern/ssl/install.html.tt”) called at cpanel.pl line 304
  • Customer added an addon domain addon-domain.com. For some reason, apache virtual host for this site is missing. This domain was not listed in cPanel to remove it using cPanel.

 

Solution

1. If we run just cPanel, do cpanel force update:

# /scripts/upcp –force
# /scripts/checkperlmodules

If we run cPanel with CloudLinux, do LVE Manager update:

# yum update lvemanager

2. Then, we need to manually remove all entry for this domain from following locations:

/var/cpanel/users/$username
/var/cpanel/userdata/$username/

Example:

[email protected] [/var/cpanel/users]# grep addon-domain /var/cpanel/users/*
/var/cpanel/users/bob:XDNS1=addon-domain.com
/var/cpanel/users/bob:XDNS2=addon-domain.customer-main-domain.com
[email protected] [/var/cpanel/users]#

Removed the two entries from the file /var/cpanel/users/bob

Now in users data folder, check for the domain.

[email protected] [/var/cpanel/users]# cd /var/cpanel/userdata/bob/
[email protected] [/var/cpanel/userdata/bob]# ls -l | grep addon-domain.com
-rw-r–r– 1 root root 719 May 03 06:27 addon-domain.com.customer-main-domain.com_SSL
-rw-r–r– 1 root root 764 May 03 06:27 addon-domain.com.customer-main-domain.com_SSL.cache
[email protected] [/var/cpanel/userdata/bob]# rm -f addon-domain.com.customer-main-domain.com_SSL
[email protected] [/var/cpanel/userdata/bob]# rm -f addon-domain.com.customer-main-domain.com_SSL.cache

 

3. Cause: When we create a cPanel account from root WHM account we are getting this error.

[wpfmb type=’error’ theme=2]Fatal error or timeout occurred while processing this directive] [an error occurred while processing this directive[/wpfmb]

It is due to permission issues.

Solution

Execute following commands in /home.

# chown username.username username -R
# chown username.mail username/etc -R
# chown username.nobody username/public_html
# rm -rf username/.cpanel

Then log out and log in back into cPanel. This will regenerate the .cpanel directory.

4. Cause: The file /var/cpanel/whm/nvdata/root.yaml seems to have been corrupted.

From cPanel log:

Magic number checking on storable file failed at /usr/lib/perl5/site_perl/5.6.2/x86_64-linux/Storable.pm line 414, at /usr/local/cpanel/Cpanel/SafeStorable.pm line 69
Carp::croak(‘Magic number checking on storable file failed at /usr/lib/perl5/…’) called at /usr/lib/perl5/site_perl/5.6.2/x86_64-linux/Storable.pm line 38
Storable::__ANON__(‘Magic number checking on storable file failed at /usr/lib/perl5/…’) called at /usr/lib/perl5/site_perl/5.6.2/x86_64-linux/Storable.pm line 415
Storable::fd_retrieve(‘GLOB(0x1d4a980)’, 0) called at /usr/local/cpanel/Cpanel/SafeStorable.pm line 69
Cpanel::SafeStorable::fd_retrieve(‘GLOB(0x1d4a980)’) called at /usr/local/cpanel/Cpanel/CachedDataStore.pm line 120
eval {…} called at /usr/local/cpanel/Cpanel/CachedDataStore.pm line 120
Cpanel::CachedDataStore::loaddatastore(‘/var/cpanel/whm/nvdata/root.yaml’, 0, ‘HASH(0x1d3e340)’, undef) called at /usr/local/cpanel/Cpanel/CachedDataStore.pm line 39
Cpanel::CachedDataStore::load_ref(‘/var/cpanel/whm/nvdata/root.yaml’, ‘HASH(0x1d3e340)’) called at /usr/local/cpanel/Cpanel/CachedDataStore.pm line 29
Cpanel::CachedDataStore::fetch_ref(‘/var/cpanel/whm/nvdata/root.yaml’) called at /usr/local/cpanel/Whostmgr/NVData.pm line 41
Whostmgr::NVData::get_ref() called at whostmgr/bin/whostmgr10 line 402
main::themecommand_tmpl(‘main’) called at whostmgr/bin/whostmgr10 line 252

Solution

Move the file /var/cpanel/whm/nvdata/root.yaml to /var/cpanel/whm/nvdata/root.yaml.bk.

[Need help with the procedures? We are here for you]

Conclusion

In short, WHM/cPanel interface can give timeout errors occasionally, if the packages are outdated. Today, we saw how our Support Engineers fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF