Security Center:Troubleshoot issues that cause vulnerability fixing failures

Error code

Error message

Cause

Solution

116

download file fails

The required patch fails to be downloaded.

The patch that is required to fix a Windows system vulnerability fails to be downloaded. Fix the vulnerability later in the Security Center console. If the issue persists, submit a ticket to contact technical support.

124

windows modules installer service disable

The Windows Modules Installer service is not enabled.

You must enable the Windows Modules Installer service in Windows Services Manager.

1. Press Win+R to open the Run dialog box.

2. In the Run dialog box, enter services.msc and click OK.

3. Find the Windows Modules Installer service in the service list.

4. Right-click the Windows Modules Installer service and click Start to enable the service.

windows update service disable

The Windows Update service is not enabled.

You must enable the Windows Update service in Windows Services Manager.

1. Press Win+R to open the Run dialog box.

2. In the Run dialog box, enter services.msc, and click OK.

3. Find the Windows Update service in the service list.

4. Right-click the Windows Update service and click Start to enable the service.

125

exit code:0x00000005

The fixing process is blocked by security software or infected by viruses.

The fixing process is blocked by security software or infected by viruses, or the files that are required for the fix cannot be opened. Check whether security software is running on your server. Suspend the security software and fix the vulnerability again.

127

exit code:0x00000070, (OK)

The disk space is insufficient.

If an ERROR_DISK_FULL error is reported when you install a Windows patch, the patch failed to be installed because the disk space is insufficient. In this case, you must release the disk space before you can continue to install the patch. The following list describes the methods that you can use to release the disk space:

• Delete unnecessary files and programs. You can search for and delete the files and programs that you no longer require on your computer. You can also use the Disk Cleanup tool that is provided by Windows or a third-party tool to delete unnecessary files, such as temporary files, junk files, and cached files.

• Move files to an external hard disk or cloud storage. You can move large files, such as videos, audio files, and photos, to an external hard disk or cloud storage to release disk space.

• Compress files. In some cases, you can compress files to release disk space.

• Archive files. You can archive the files that you no longer require to an external storage device so that you can restore the files later.

If the disk space is sufficient after you perform the preceding operations, you can continue to install the patch.

130

exit code:0x00000008

The memory is insufficient.

Check the memory usage and CPU utilization of your server. Make sure that your server has sufficient memory and CPU resources. Then, fix the vulnerability again.

132

exit code:0x80240017

• A patch is being installed on the server.

• A patch is installed on the server. The patch requires you to restart the server after the patch is installed.

Check whether a patch is being installed on your server. If a patch is being installed, wait until the patch is installed and fix the vulnerability again. If no patch is being installed on your server, make sure that your business is not affected when you restart the server. Then, restart the server and fix the vulnerability again.

133

xxx.exe is running

The installation of a patch is blocked by security software.

The installation of a patch is blocked by security software. Check the security software that runs on your server based on the error message and suspend the software. Then, fix the vulnerability again.

134

exit code:0x00000476, (OK)

ERROR_TOO_MANY_LINKS

Excessive symbolic links exist in the file system.

In most cases, the error is reported when excessive symbolic links or hard links exist in your file system. The error may affect the running of the file system. In addition, new Windows patches may fail to be installed. You can use the following methods to resolve the issue:

• Clear the disk space: You can delete unnecessary files and programs to clear the disk space.

• Cancel symbolic links: Check the symbolic links and hard links in the file system, and cancel the excessive symbolic links and hard links.

• Check the disk status: You can check the status of the disk and repair the disk to ensure that the file system runs as expected.

• Disable the Windows Defender service: The Windows Defender service may interfere with the installation of Windows patches. You can disable the Windows Defender service and install the patches again.

202

timeout

The installation of the required patch times out.

The installation of the patch that is required to fix a Windows system vulnerability times out. Fix the vulnerability again. If the issue persists, submit a ticket to contact technical support.

256

failure: repodata/repomd.xml from docker-ce-stable: [Errno 256] No more mirrors to try.

https://download.docker.com/linux/centos/2.1903/x86_64/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

The download source is invalid.

The error message indicates that the download source download.docker.com is invalid. Perform the following steps:

1. Use a CLI to go to the /etc/yum.repos.d/ directory and run the following command to find the invalid download source file.

   Note

   You must replace download.docker.com in the command with the source name in the error message.

   grep -r "download.docker.com"

2. Modify the source file and set enabled to 0 to disable the source file.

3. Fix the vulnerability again.

failure: repodata/repomd.xml from HDP-3.0-repo-1: [Errno 256] No more mirrors to try.

http://public-repo-1.hortonworks.com/HDP/centos7/3.x/updates/3.0.0.0/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden

The download source cannot be accessed.

The error message indicates that the download source public-repo-1.hortonworks.com cannot be accessed. Perform the following steps:

1. Use the CLI to go to the /etc/yum.repos.d/ directory and run the following command to find the source file of the download source that cannot be accessed.

   Note

   You must replace public-repo-1.hortonworks.com in the command with the source name in the error message.

   grep -r "public-repo-1.hortonworks.com" 

2. Modify the source file and set enabled to 0 to disable the source file.

3. Fix the vulnerability again.

There are unfinished transactions remaining

The historical installation commands failed to complete and the installation stopped.

The error may be caused by issues that occur when you use Yellowdog Updater, Modified (YUM) to install software. Run the following command on the server to resolve the remaining issues. Then, fix the vulnerability again.

yum-complete-transaction --cleanup-only

Error:rpmdb open failed

The RPM database is corrupted.

The RPM database is opened by a process other than the installation process, or the files of the RPM database are corrupted. You can run the following commands in sequence to rebuild the RPM database. Then, fix the vulnerability again.

cd /var/lib/rpm  // Go to the directory of the RPM database.
rm -f __db.*  // Delete the existing files of the RPM database.
rpm --rebuilddb // Rebuild the RPM database.
yum clean all // Clear all YUM caches.

Transaction Check Error

A software package conflict occurs.

1. View the execution information about YUM in the error message and find the software package that causes the conflict based on the following keyword: conflicts with file.

2. Make sure that your business is not affected if the software package is deleted. Then, run the following command to delete the software package.

   yum remove [package_name]

3. Fix the vulnerability again.

CRITICAL:yum.cli:Config error: Error accessing file for config file:///etc/yum.conf

The YUM configuration file is missing.

The error may occur because the YUM configuration file /etc/yum.conf does not exist. You can copy the configuration file from another server that runs the same type of operating system as your server. Then, fix the vulnerability again.

300

rtap running error

The execution of the script for the Security Center agent fails.

The Security Center agent fails to run the fixing program because the program may be blocked by third-party security software. Fix the vulnerability again in the Security Center console. If the issue persists, submit a ticket to contact technical support.

309

execute rtap task fail

8005

/bin/rpm permit error

The tool or script used to fix a vulnerability does not have the required permissions to run the /bin/rpm command.

If excessively high permissions are required to run the /bin/rpm command, privilege escalation risks may rise. In most cases, you can set the permissions on the /bin/rpm file to 755 or 750. This ensures that only authorized users can perform related operations.

8008

not support this system xxx

The current system does not support vulnerability fixing.

The error may occur because you have changed the type of the operating system of your server after the vulnerability is detected on the server. As a result, the current operating system of your server is different from the operating system when the vulnerability was detected. You can ignore the vulnerability in the Security Center console or wait for the vulnerability to expire. For more information, see View and handle vulnerabilities.

8009

update process is running

An existing fixing process is running.

A vulnerability fixing process is running. Try again later.

8010

Insufficient space in download directory /var/cache/yum/x86_64/7/aegisbase

The disk space is insufficient.

YUM failed to be updated because of insufficient disk space. Clear the disk space based on the path in the error message. Then, fix the vulnerability again.

8012

dpkg was interrupted

Related data is damaged because dpkg (Debian Packager) is interrupted.

Related data is damaged because dpkg is interrupted. The previous fixing process is forcefully stopped and junk data is generated. Use the CLI to run the following command on your server to reconfigure the settings.

dpkg --configure -a	

For more information, see Fix dpkg interruptions.

8019

yum exception

An error occurs in running the yum command.

The Python environment in which the yum command is run does not support the syntax of the yum file. Check whether the content of the file in the /usr/bin/yum directory contains syntax errors and check whether the Python environment in which the yum command is run is correctly configured.

8027

A has missing requires of B

A required software package is missing.

1. Identify the software package that is required to fix the vulnerability based on the error message. Example:

   1. A in the error message is the software package that is used for the update.

   2. B in the error message is the software package that is required for the preceding software package.

2. Use the CLI on your server to run the following command to install the software.

   Note

   Before you run the following command, replace xxx with the name of the software package that you want to use.

   yum update xxx --disableexcludes=all --disablerepo="*" --enablerepo="aegisbase,aegisupdates,aegisextras" --obsoletes 

3. Fix the vulnerability again.

8032

run virtio fix process faild

The program that is used to fix an Elastic Compute Service (ECS) disk drive vulnerability fails to start.

If a program that is used to fix an ECS disk drive vulnerability fails to start, the program may be blocked by security software. Make sure that no security software blocks the program. Then, fix the vulnerability again.

8033

yum plugins protectbase enable

The ProtectBase plug-in blocked the update of YUM.

The ProtectBase plug-in of YUM blocked the update. Disable the ProtectBase plug-in on your server and fix the vulnerability again. Perform the following steps to disable the plug-in:

1. Open the configuration file /etc/yum/pluginconf.d/protectbase.conf of ProtectBase.

2. Change enabled = 1 to enabled = 0.

8037

[Errno 14] curl#6 - "Could not resolve host: mirrors.cloud.aliyuncs.com; Unknown error"

The mirrors.cloud.aliyuncs.com domain name cannot be accessed.

1. Check whether the network connection between your server and the mirrors.cloud.aliyuncs.com domain name is normal, and whether the traffic between your server and the domain name is blocked by a security group or a firewall.

2. If your server is connected to the Internet, replace mirrors.cloud.aliyuncs.com in the enabled source file with mirrors.aliyun.com in the /etc/yum.repos.d/ path.

3. Fix the vulnerability again.

8040

miss kernel grub file

The kernel boot file is missing.

Rebuild the kernel boot file. If your server runs CentOS 7, run the following command in the CLI on your server:

grub2-mkconfig -o /boot/grub2/grub.cfg

After the file is rebuilt, fix the vulnerability again.

8041

redhat not subscription

No Red Hat account is created.

No Red Hat account is created for your server. You must create a Red Hat account on the Red Hat official website and purchase a subscription service. Go to the Red Hat official website and create a Red Hat account.

8080

sh xxx killed

The yum process is terminated due to an out of memory (OOM) error.

The vulnerability failed to be fixed because the system memory is insufficient. You can release the memory space and fix the vulnerability again.

8081

blacklist process xxx is running

A blacklist process that locks the kernel configuration file is running.

If a blacklist process is running, it blocks the kernel configuration file. As a result, the kernel version may not be updated after a vulnerability is fixed. You can stop the process and fix the vulnerability again.

9002

timeout

The fixing operation times out.

The failure may be caused by network jitters or the server environment. Fix the vulnerability again in the Security Center console. If the issue persists, submit a ticket to contact technical support.

9003

xxx is already the newest version

The command is successfully run, and your system is updated to the latest version. However, the vulnerability is not fixed.

Your system is updated to the latest version, but the vulnerability is not fixed. If you changed the source, set the source to the Alibaba Cloud source mirrors.cloud.aliyuncs.com or mirrors.aliyun.com. Then, fix the vulnerability again. If the issue persists, submit a ticket to contact technical support.

Invalid configuration value: failovermethod =priority in /etc/yum.repos.d/CentOS-Linux-epel.repo

An error occurs in the configuration items of YUM.

Check the download source configurations of the current system. Move the source file /etc/yum.repos.d/CentOS-Linux-epel.repo that contains the configuration error to a different directory for backup. Then, fix the vulnerability again.

Finished Dependency Resolution

YUM exits immediately after the dependency analysis is complete. This may be caused by software package conflicts.

The operation logs of YUM in the error message show that YUM exits immediately after the dependency analysis is complete, and the installation command is not run.

If you are upgrading MariaDB, this error may occur because MySQL was installed on your server and port conflicts exist. You can perform the following steps to resolve the issue:

1. Run the following command in the CLI on your server to check whether port 3306 is occupied by MySQL:

   netstat -anltp

2. Make sure that your business is not affected if MySQL is disabled. Then, run the following command to disable MySQL:

   systemctl stop mysqld

3. Run the following command to view the installed MySQL package:

   yum list mysql*

4. Run the following command to remove the MySQL package:

   yum remove [package_name]

5. Run the following command to reinstall MariaDB:

   yum install -y mariadb-server

9007

ack timeout

The execution of the installation command times out.

The upgrade of the software package times out, which may be caused by network jitters or the environment of your server. Fix the vulnerability again in the Security Center console. If the issue persists, submit a ticket to contact technical support.

9008

rpm collect timeout

The collection of the data of a software package times out.

The collection of the data of a software package times out. This may be caused by network jitters or the environment of your server. Fix the vulnerability again in the Security Center console. If the issue persists, submit a ticket to contact technical support.

60001

start vulfix:[Error 2] The system cannot find the file specified

The fixing process is blocked by security software and fails to be started.

The fixing process is blocked by security software and fails to be started. Check whether security software is running and suspend the security software. Then, fix the vulnerability again.