(yum) was not able to locate the glibc package

[zurca]

I got a question, I am trying to add a module to apache through the webhosting manager apache update, but when I try to build apache, this gives me an apache build error message:

Building Apache Config.....Done
Downloading and compiling apache+modules....


Fetching http://layer1.cpanel.net/buildapache.sea (0)[email protected]%...3%...4%...6%...7%...9%...11%...12%...14%...15%...17%...19%...20%...22%...23%...25%...27%...28%...30%...31%...33%...35%...36%...38%...39%...41%...42%...44%...46%...47%...49%...50%...52%...54%...55%...57%...58%...60%...62%...63%...65%...66%...68%...70%...71%...73%...74%...76%...78%...79%...81%...82%...84%...85%...87%...89%...90%...92%...93%...95%...97%...98%...100%......Done
Verifying archive integrity... All good.
Uncompressing buildapache...................................................................................................................................................................................................................................
Checking Update System........Your operating system's rpm update method (yum) was not able to locate the glibc package. This is an indication of an improper setup. You must correct this error before you can proceed.
Please correct the conflicts and try again!

I ssh to my server and tried rpm -q glibc from the command shell and it displays that the following glibc version is already installed:

glibc-2.3.2-95.30

Why is yum not able to locate this package since its already installed?

Any suggestions will be appreaciated and if it is in plain english walk through even better since I am still little green on linix commands. I am running CentOS 3.4 i686
Thanks

 

[fwwebs]

I believe you get that fail when yum isn't installed. If this is a new installation it's probably the case.

 

[cool38]

check ur /etc/yum.conf
see if your settings actually skip anything for updating.

 

[zurca]

I believe you get that fail when yum isn't installed. If this is a new installation it's probably the case.

No, this is not a fresh install, the server has been working for the past 3 years, and last time I did a apache build through whm worked fine about 3 to 4 months ago.

 

[zurca]

check ur /etc/yum.conf
see if your settings actually skip anything for updating.

Is there anything I need to look for in particular in the /etc/yum.conf

Thanks

 

[hamper]

I just tried to run an update and got the same thing.

Building Apache Config.....Done
Downloading and compiling apache+modules....


Testing connection speed...(this could take a while)............Done
Ping:30.335 Testing connection speed to 198.66.78.11 using wget...(416220 bytes/s)...Done
Ping:30.540 Testing connection speed to 198.66.78.12 using wget...(417650 bytes/s)...Done
Ping:30.650 Testing connection speed to 69.90.250.35 using wget...(311620 bytes/s)...Done
Ping:30.814 Testing connection speed to 69.90.250.36 using wget...(310870 bytes/s)...Done
Ping:31.163 Testing connection speed to 69.90.250.34 using wget...(402480 bytes/s)...Done
5 usable mirrors located
Fetching http://layer1.cpanel.net/buildapache.sea (0)[email protected]%...3%...4%...6%...7%...9%...11%...12%...14%...15%...17%...19%...20%...22%...23%...25%...27%...28%...30%...31%...33%...35%...36%...38%...39%...41%...42%...44%...46%...47%...49%...50%...52%...54%...55%...57%...58%...60%...62%...63%...65%...66%...68%...70%...71%...73%...74%...76%...78%...79%...81%...82%...84%...85%...87%...89%...90%...92%...93%...95%...97%...98%...100%......Done
Verifying archive integrity... All good.
Uncompressing buildapache...................................................................................................................................................................................................................................
Checking Update System........Your operating system's rpm update method (yum) was not able to locate the glibc package. This is an indication of an improper setup. You must correct this error before you can proceed.
Please correct the conflicts and try again!
Attempting to restart httpd
Waiting for httpd to restart....

finished.

httpd status
root 6713 0.7 0.7 14532 7192 ? Ss 22:35 0:00 /usr/local/apache/bin/httpd -DSSL



httpd started ok
Build Complete

 

[Danny_T]

Still no sollutions?

I getting this too since a while. Now i need to add a module but error still exists.

Building Apache Config.....Done
[...CUT...]
Checking Update System........Your operating system's rpm update method (yum) was not able to locate the glibc package. This is an indication of an improper setup. You must correct this error before you can proceed.
Please correct the conflicts and try again!

Box: FC3
Enabled dries/dag/legacy/updates/core/base.
Nothing much updated from yum because FC3 is in legacy state and almost EOL.

If someone knows a sollution.. its not anything to do with YUM! I think its the package/script that was downloaded from cpanel.net.

Be quick please.. i realy need to enable a module!

Greetz Danny.

 

[crwilliams]

I had the exact same problem a few months ago, but with up2date rather than yum. I don't know if this will help you, but my problem was fixed when I ran:

/scripts/updatenow

and then

/scripts/upcp --force

After those finished, I went back and ran the apache build, and it went through without a problem. Good luck!

 

[Danny_T]

[email protected] [/scripts]# ./updatenow
updatenow should only be run from upcp at ./updatenow line 10.
[email protected] [/scripts]#

Not working :S

and ./upcp --force ran, then apache update.. still the glibc error

Has it something todo with this when upcp is running? :

Doing a manual update...
Cpanel updates are coming from layer2.cpanel.net
findutils passes checksum
net-tools fails checksum !!!
Notification => [email protected] via EMAIL [level => 3]
Fetching http://updates.cpanel.net/pub/hackcheck/fedora/3/net-tools-1.60-37.FC3.1.i386.rpm (0)[email protected]%...2%...3%...5%...6%...7%...8%...10%...11%...12%...14%...15%...16%...17%...19%...20%...21%...22%...24%...25%...26%...28%...29%...30%...31%...33%...34%...35%...36%...38%...39%...40%...42%...43%...44%...45%...47%...48%...49%...50%...52%...53%...54%...56%...57%...58%...59%...61%...62%...63%...64%...66%...67%...68%...70%...71%...72%...73%...75%...76%...77%...79%...80%...81%...82%...84%...85%...86%...87%...89%...90%...91%...93%...94%...95%...96%...98%...99%...100%......Done
Error fetching http://updates.cpanel.net/pub/hackcheck/fedora/3/net-tools-1.60-37.FC3.1.i386.rpm at /scripts/cPScript/RpmUtils.pm line 81.


*rpm database has net-tools-1.60-37.FC3.1.i386

 

[Danny_T]

Error fetching http://updates.cpanel.net/pub/hackcheck/fedora/3/net-tools-1.60-37.FC3.1.i386.rpm at /scripts/cPScript/RpmUtils.pm line 81.

Not the problem. I just downloaded it manual (and file exists tho) and manual installed it.
That problem is now solved.

The glibc error still exists

 

[zurca]

Not the problem. I just downloaded it manual (and file exists tho) and manual installed it.
That problem is now solved.

The glibc error still exists

Any luck yet Danny?

I still can not figure this out yet, why would (yum) was not able to locate the glibc package

even tho I have glibc-2.3.2-95.30 already installed.

My yum.conf file out put is as follows:

#/etc/yum.conf Jan/2/2005 [email protected]

[main]

exclude=mod_ssl* httpd* perl mysql* php* spamassassin* kernel* exim* courier* apache*

cachedir=/var/cache/yum

debuglevel=2

logfile=/var/log/yum.log

pkgpolicy=newest

distroverpkg=redhat-release

installonlypkgs=kernel kernel-smp kernel-hugemem kernel-enterprise kernel-debug

kernel-unsupported kernel-smp-unsupported kernel-hugemem-unsupported

tolerant=1

exactarch=1


[base]
name=CentOS-$releasever - Base
baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1

#released updates
[update]
name=CentOS-$releasever - Updates
[update]
name=CentOS-$releasever - Updates
baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1

#packages used/produced in the build but not released
[addons]
name=CentOS-$releasever - Addons
baseurl=http://mirror.centos.org/centos/$releasever/addons/$basearch/
gpgcheck=1

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1

#additional packages that extend functionality of existing packages
#[centosplus]
#name=CentOS-$releasever - Plus
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
#gpgcheck=1
#packages in testing
#[testing]
#name=CentOS-$releasever - Testing
#baseurl=http://mirror.centos.org/centos/$releasever/testing/$basearch/
#gpgcheck=1

 

[BenThomas]

The check that is failing is the result of the command 'yum info glibc'. Does this command return any info for glibc and if so what?

 

[Danny_T]

yum info glibc (FC3):

Name : glibc
Arch : i686
Version: 2.3.6
Release: 0.fc3.1
Size : 12 M
Repo : installed
Summary: The GNU libc libraries.



Available Packages
Name : glibc
Arch : i386
Version: 2.3.6
Release: 0.fc3.1
Size : 4.2 M
Repo : legacy-updates
Summary: The GNU libc libraries.

Disabled legacy repo's:

Installed Packages
Name : glibc
Arch : i686
Version: 2.3.6
Release: 0.fc3.1
Size : 12 M
Repo : installed
Summary: The GNU libc libraries.



Available Packages
Name : glibc
Arch : i386
Version: 2.3.6
Release: 0.fc3.1
Size : 4.2 M
Repo : updates
Summary: The GNU libc libraries.

 

[rikgarner]

Could this be a problem with the Yum repo or the yum cache? Centos recently re-worked their repo structure to ensure that you always get the nearest mirror of the repo.

http://www.centos.org/modules/news/article.php?storyid=118
is worth a read.

Also, it may be worth giving clearing the yum cache a go:


http://www.centos.org/docs/4/html/yum/sn-yum-maintenance.html

Rich

 

[BenThomas]

Please run the following from the command line several times and let me know how often it fails:

perl -I/scripts -McPScript::RpmUtils -e '($status,$message) = cPScript::RpmUtils::checkupdatesystem(); print $message;'

It should say "Rpm Sanity Check PASSED!" in green.

Also do the same for 'yum info glibc'.

I'd seen this fail during early testing, but it was a yum hiccup (I assume) because it immediately starting working again.

 

[Danny_T]

# yum clean all
Cleaning up Everything
111 headers removed
100 packages removed
20 metadata files removed
10 cache files removed

Ok lets try...


Checking Update System........Your operating system's rpm update method (yum) was not able to locate the glibc package. This is an indication of an improper setup. You must correct this error before you can proceed.
Please correct the conflicts and try again!
initfpsuexec: using apache 1.x support
User demo
Group demo
User demo
Group demo
User reseller
Group reseller
User develop
Group develop
(cut of a lot such messages.....)

Euh what is this all about lol That did not showed up yesterday!? cPanel scripts did changed something again? lol
Still the yum glibc error.

 

[BenThomas]

Please read my previous post.

 

[Danny_T]

Did ran it 15 times.

Same message:

# perl -I/scripts -McPScript::RpmUtils -e '($status,$message) = cPScript::RpmUtils::checkupdatesystem(); print $message;'

Your operating system's rpm update method (yum) was not able to locate the glibc package. This is an indication of an improper setup. You must correct this error before you can proceed.

And now yum info glibc or yum update etc etc gives:

Traceback (most recent call last):
File "/usr/bin/yum", line 7, in ?
yummain.main(sys.argv[1:])
File "/usr/share/yum-cli/yummain.py", line 68, in main
result, resultmsgs = base.doCommands()
File "/usr/share/yum-cli/cli.py", line 413, in doCommands
return self.updatePkgs()
File "/usr/share/yum-cli/cli.py", line 932, in updatePkgs
self.doRepoSetup()
File "/usr/share/yum-cli/cli.py", line 89, in doRepoSetup
self.doSackSetup()
File "/usr/lib/python2.3/site-packages/yum/__init__.py", line 143, in doSackSetup
self.repos.populateSack()
File "/usr/lib/python2.3/site-packages/yum/repos.py", line 243, in populateSack
dobj = repo.cacheHandler.getPrimary(xml, csum)
File "/usr/lib/python2.3/site-packages/yum/mdcache.py", line 103, in getPrimary
return self._getGeneric('metadata', location, checksum)
File "/usr/lib/python2.3/site-packages/yum/mdcache.py", line 90, in _getGeneric
databank = self._unpickle(piklfile)
File "/usr/lib/python2.3/site-packages/yum/mdcache.py", line 62, in _unpickle
obj = cPickle.load(infh)
EOFError

Danny

 

[BenThomas]

Thanks for the follow up. In this case it looks like the "checkupdatesystem" verification is working as intended. You'll need to resolve the issue with yum before continuing. I recommend verifying the yum rpm and reinstalling it if necessary. Once you get to the point where 'yum info glibc' returns valid results then the cPanel software will work as expected.

 

[MMarko]

Please run the following from the command line several times and let me know how often it fails:

perl -I/scripts -McPScript::RpmUtils -e '($status,$message) = cPScript::RpmUtils::checkupdatesystem(); print $message;'

It should say "Rpm Sanity Check PASSED!" in green.

Also do the same for 'yum info glibc'.

I'd seen this fail during early testing, but it was a yum hiccup (I assume) because it immediately starting working again.

I got "Rpm Sanity Check PASSED!" and 'yum info glibc' shows:

Name : glibc
Arch : i686
Version: 2.3.2
Release: 95.39
Size : 11.79 MB
Group : System Environment/Libraries
Repo : Locally Installed
Summary: The GNU libc libraries.



I'm still getting

"Fetching http://layer1.cpanel.net/buildapache.sea (0)[email protected]%...3%...4%...6%...7%...9%...11%...12%...14%...15%...17%...19%...20%...22%...23%...25%...26%...28%...30%...31%...33%...34%...36%...38%...39%...41%...42%...44%...46%...47%...49%...50%...52%...53%...55%...57%...58%...60%...61%...63%...65%...66%...68%...69%...71%...72%...74%...76%...77%...79%...80%...82%...84%...85%...87%...88%...90%...92%...93%...95%...96%...98%...99%...100%......Done
Verifying archive integrity... All good.
Uncompressing buildapache....................................................................................................................................................................................................................................
Checking Update System........Your operating system's rpm update method (yum) was not able to locate the glibc package. This is an indication of an improper setup. You must correct this error before you can proceed.
Please correct the conflicts and try again!"