Bobcares

wesupport

CLIENT AREACall Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193
Bobcares

wesupport

Call Us 1-800-383-5193

Need help?

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

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

Failed to update analyze_config_VERSION

by | Nov 2, 2021

Failed to update analyze_config_VERSION? We can help you.

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

Today, let us see how we can fix this error.

 

Failed to update analyze_config_VERSION

Though we can log in to the server through the command line, an attempt to connect and scan the remote server in the WHM interface Transfer Tool may return the following error:

The system failed to update the file "analyze_config_VERSION" on the remote server because of an error: The remote server "X.X.X.X" unexpectedly terminated the connection. The port may be incorrect, or the remote server may not allow connections from this server: lost connection

This tool establishes an SSH connection and generates a script to populate the remote server’s information in the interface.

Most often, this error occurs due to network communication issues between the source and destination servers.

On the other hand, suppose we can establish an SSH login manually outside of the Transfer Tool. Then, it indicates a problem with the additional tasks the transfer tool performs.

Once we establish the initial SSH connection, to generate the analyze_config script the Transfer Tool performs an SCP command on the source server.

If this fails, a failure in the SCP command on the source server is the cause. We cannot alter or modify SCP binaries.

In order to check any alteration in the binary, our Support Techs recommend the following command:

rpmverify openssh-clients | grep -i scp

If there is any modification, we need to restore it from the package or revert it to the correct values.

By default, this binary should have a group and owner of the root user and have access permissions of 755.

In case, there has been any modification we can correct it with the following commands:

chown root. /usr/bin/scp

chmod 755 /usr/bin/scp

[Need further assistance? We are here for you]

 

Conclusion

In short, we saw how our Support Techs fix the WHM error for our customers.

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

0 Comments

Submit a Comment

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

Reviews