We are doing RHEL patching using RHSM plugin present in BigFix Console but today we observed that all patches are getting failed.
Below is the log file, Please suggest what could be issue…
OSError: [Errno 28] No space left on device
28459 : 2020-08-15 18:54:09 : ERROR : yum command not continue, last command exit code is not 0
28680 : 2020-08-15 19:00:22 : INFO : Start Task ID: 3456
28680 : 2020-08-15 19:00:22 : INFO : RHEL-Patch-Client at version 2.0.1.0
28680 : 2020-08-15 19:00:22 : INFO : 01 setup and request repomd.xml
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28680 : 2020-08-15 19:00:22 : INFO : yum cache lock is not expired yet. Skip repomd.xml file requests.
28682 : 2020-08-15 19:00:22 : INFO : 03 lock repo data
28682 : 2020-08-15 19:00:22 : CRITICAL : Unexpected error!
28682 : 2020-08-15 19:00:22 : CRITICAL : Exception type: <class ‘OSError’>
28682 : 2020-08-15 19:00:22 : CRITICAL : [Errno 28] No space left on device
OSError: [Errno 28] No space left on device
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “”, line 47, in
File “”, line 41, in main
File “bfyum/cli/lock.py”, line 29, in do
File “bflinux/lock.py”, line 58, in set_lock
OSError: [Errno 28] No space left on device
28684 : 2020-08-15 19:00:23 : ERROR : Unarchive Metadata will not continue, last command exit code is not 0
28686 : 2020-08-15 19:00:23 : ERROR : Dependency resolution will not continue, last command exit code is not 0
28689 : 2020-08-15 19:00:27 : ERROR : yum command not continue, last command exit code is not 0
You will probably need to open a support ticket to help diagnose your system, but I think it’s likely you are out of space somewhere. That might be reflected in the output of df -k
@Manish, given the EDR log detail that you’ve provided, I would look at YUM to see if there’s an issue. In some cases, it becomes necessary to clean-up the YUM database, etc. on an endpoint for the RHSM/CentOS plugins to work properly. I’ve uploaded one analysis and two fixlets to my personal GitHub that are specific YUM check data collection and remediation.
We are patching RHEL 6 server by using BigFix but it got failed with the below error:
23987 : 2023-01-21 06:33:18 : ERROR : yum command not continue, last command exit code is not 0
24001 : 2023-01-21 06:33:26 : INFO : Start Task ID: 22564060
24001 : 2023-01-21 06:33:26 : INFO : RHEL-Patch-Client at version 2.0.1.0
24001 : 2023-01-21 06:33:26 : INFO : 01 setup and request repomd.xml
24001 : 2023-01-21 06:33:26 : WARNING : Repo list is empty for OS: els-6-x86_64
24003 : 2023-01-21 06:33:26 : INFO : 03 lock repo data
24005 : 2023-01-21 06:33:27 : INFO : 03.5 unarchive metadata
24005 : 2023-01-21 06:33:27 : WARNING : Repo list is empty for OS: els-6-x86_64
24007 : 2023-01-21 06:33:27 : INFO : 04 dependency resolution and request packages
24007 : 2023-01-21 06:33:27 : WARNING : Repo list is empty for OS: els-6-x86_64
24007 : 2023-01-21 06:33:27 : INFO : Download Plugin mode.
24007 : 2023-01-21 06:33:27 : INFO : Run cmd: env: {} cmd: yum --verbose --cacheonly -c /var/opt/BESClient/EDRDeployData//EDR_Yumconfig_22564060 --bf_dependency_resolution install --assumeyes kernel-firmware-2.6.32-754.48.1.el6.noarch kernel-2.6.32-754.48.1.el6.x86_64 kernel-headers-2.6.32-754.48.1.el6.x86_64 perf-2.6.32-754.48.1.el6.x86_64
24007 : 2023-01-21 06:33:27 : INFO : Set timout: 1785 seconds
24007 : 2023-01-21 06:33:28 : ERROR : Dependency resolution failed.
24007 : 2023-01-21 06:33:28 : ERROR : Exit Code: 1
Loading “yum-rhsmplugin” plugin
Config time: 0.007
Yum Version: 3.2.29
rpmdb time: 0.000
Setting up Install Process
Setting up Package Sacks
Checking for virtual provide or file-provide for kernel-firmware-2.6.32-754.48.1.el6.noarch
Setting up Package Sacks
No package kernel-firmware-2.6.32-754.48.1.el6.noarch available.
Setting up Package Sacks
Setting up Package Sacks
Checking for virtual provide or file-provide for kernel-2.6.32-754.48.1.el6.x86_64
Setting up Package Sacks
No package kernel-2.6.32-754.48.1.el6.x86_64 available.
Setting up Package Sacks
Setting up Package Sacks
Checking for virtual provide or file-provide for kernel-headers-2.6.32-754.48.1.el6.x86_64
Setting up Package Sacks
No package kernel-headers-2.6.32-754.48.1.el6.x86_64 available.
Setting up Package Sacks
Setting up Package Sacks
Checking for virtual provide or file-provide for perf-2.6.32-754.48.1.el6.x86_64
Setting up Package Sacks
No package perf-2.6.32-754.48.1.el6.x86_64 available.
Setting up Package Sacks
Error: Nothing to do
24011 : 2023-01-21 06:33:28 : ERROR : yum command not continue, last command exit code is not 0
If you are using the RHSM plugin method, please check if you are able to access the repositories of red hat by running the check-all repos.
In our environment the Dependency resolution failed error usually occurred due to the certificates issue. If the certificate configuration is changed then also you get this error.
If the certificates are ok and able to see the BigFix server is able to access the repositories then you will have to check if the /var/log volume is full or no if yes then clear and re-deploy the patch.