wesupport

Need help?

Our experts have had an average response time of 13.14 minutes in February 2024 to fix urgent issues.

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

cPanel reported error number 1 when it ended – How to fix it

by | May 5, 2021

Stuck with the cPanel reported error number 1 when it ended? We can help you.

This error can occur in different scenarios. Let us discuss it in detail here.

As part of our Server Management Services, we assist our customers with several cPanel queries.

Today, let us the methods to fix this error.

 

cPanel reported error number 1 when it ended

Scenario 1:

Recently one of our customers came across the cPanel & WHM update failure notification:

The cPanel & WHM update process failed for the following reason:

Maintenance ended; however, it did not exit cleanly (256). The following events were logged: /scripts/check_unreliable_resolvers. Review the update logs to determine why the update failed.

Scenario 2:

In addition, we can find this error when we perform /scripts/rpmup.

Maintenance ended; however, it did not exit cleanly (256). The following events were logged: “scripts/rpmup”. Review the update logs to determine why the update failed.
Update log preview:
…
…
[2021-04-29 06:05:38 -0400] E [/usr/local/cpanel/scripts/rpmup] The “/usr/local/cpanel/scripts/rpmup” command (process 31027) reported error number 1 when it ended.
…
[2021-04-29 06:05:38 -0400] The Administrator will be notified to review this output when this script completes
[2021-04-29 06:05:38 -0400] – Finished command `/usr/local/cpanel/scripts/rpmup` in 14.180 seconds
[2021-04-29 06:05:38 -0400] 30% complete
[2021-04-29 06:05:38 -0400] – Finished in 14.180 seconds
[2021-04-29 06:05:38 -0400] – Finished in 0.036 seconds
[2021-04-29 06:05:38 -0400] Processing:
[2021-04-29 06:05:38 -0400] Maintenance complete. [state=pre]

Scenario 3:

We have also had customer face the following error while using ”Copy an Account From Another Server With an Account Password”

Starting “TRANSFER” for “Account” “Username”.
Attempting to copy “Username” from “Source IP”.
Trying to fetch cpmove file via cPanel API!
Fetching current backups from remote server …cPanel Login Failed: 403 Forbidden Access denied
Failed to fetch cpmove file via cPanel API.
Failed: Error while executing “/usr/local/cpanel/scripts/getremotecpmove”. The “/usr/local/cpanel/scripts/getremotecpmove SourceIP Username” command (process 2364424) reported error number 1 when it ended.

Cause

The major causes of this error include:

  1. When the script /scripts/check_unreliable_resolvers finds some, or all, of the DNS servers, are not reachable from the server.
  2. If the system’s /etc directory is assigned the immutable attribute.
  3. And, if the destination server is not able to login into the source server to fetch files.

 

Solution

Moving ahead, our Support Techs suggest three methods for the resolution.

  • Find which DNS server is unreachable

To do so, we run the following script:

/scripts/check_unreliable_resolvers​

For example,

# /scripts/check_unreliable_resolvers
cPanel reported error number 1 when it ended Partial DNS resolver failure

Resolver
State
192.168.0.1
Failed
8.8.4.4
Normal
8.8.8.8
Normal

Once we find the DNS servers that are unreachable, we can temporarily disable them. To do so, we add a ‘#’ to the front of each unreachable DNS server line in /etc/resolv.conf.

For instance,

nameserver 8.8.8.8
nameserver 8.8.4.4
#nameserver 192.168.0.1

Optionally, we can use WHM >> Resolver Configuration to remove the unreachable DNS servers.

However, in case all DNS servers are failing, we can temporarily use Google’s public DNS servers 8.8.8.8 and 8.8.4.4.

  • Change the immutable attribute

In order to change the immutable attribute, we use the below command:

chattr -i /etc
  • Recheck the username, password, and IP address.

Ensure the username and password are correct. In addition, login into the WHM of the source server. Then we go to “ConfigServer Security & Firewall”. Here, we allow the IP address in csf.

[Need help with the resolution? We’d be happy to help]

 

Conclusion

In short, today we saw how our Support Techs 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.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

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

Categories

Tags