Description of problem: Recently, whenever I try and run up2date on one of my hosts - I get a segmentation violation.. I do not believe it is a connectivity issue because I am able to successfully re-register with RHN. Here is a cut-n-paste of up2date output.. [root@vq2xr001 rpm]# up2date -l Fetching Obsoletes list for channel: rhel-i386-as-3... Fetching rpm headers... Segmentation fault############ [root@vq2xr001 rpm] [root@vq2xr001 rpm]# up2date -u Fetching Obsoletes list for channel: rhel-i386-as-3... Fetching rpm headers... Segmentation fault############ [root@vq2xr001 rpm]# Version-Release number of selected component (if applicable): [root@vq2xr001 rpm]# rpm -qa | grep -i up2date up2date-gnome-4.4.67-3 up2date-4.4.67-3 [root@vq2xr001 rpm]# rpm -qa | grep -i rpm rpm-python-4.2.3-24_nonptl rpm-libs-4.2.3-24_nonptl rpm-build-4.2.3-24_nonptl rpm-4.2.3-24_nonptl redhat-java-rpm-scripts-1.0.2-2 rpmdb-redhat-3-0.20050921 rpm-devel-4.2.3-24_nonptl redhat-rpm-config-8.0.28-2 How reproducible: Every Time Steps to Reproduce: 1. run "up2date -l" 2. or run "up2date -u" 3. Actual results: Segmentation Violation Expected results: Expecting server to download latest updates from RHN and install them. Additional info: Server is RHEL 3.6
User bnackash's account has been closed
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.