Failed or Missing Dependency of glibc-common Error失败或失踪的依赖， glibc的常见错误

The following error message or problem may appear when you’re using or running “/scripts/upcp” script (manual or schedule), “/scripts/rhlupdate” script from WebHost Manager (WHM) cPanel, “yum update” command, or “yum check-update” command in CentOS and Linux such as RedHat or Fedora:下列错误讯息或可能出现的问题，当您使用或运行“ /脚本/ upcp ”脚本（手动或附表） ， “ /脚本/ rhlupdate ”脚本从网页主机服务经理（的WHM ）的cPanel ， “荫更新”命令，或“百胜检查更新”命令，在centos和Linux如RedHat作业或Fedora的：

Error: Missing Dependency: glibc-common = 2.3.4-2 is needed by package libc-dummy-centos-4错误：失踪的依赖： glibc的常见= 2.3.4-2是所需要的一揽子LIBC的模拟- centos - 4

Note that the version number for glibc-common can be different from the above.请注意，版本号码为glibc的常见的可与上述不同。

If the command ran has been successfully executed in the system before, but then suddenly give such a missing dependencies error message, the RPM database may have been corrupted.如果该命令然已成功执行了在该系统之前，但随后突然作出这样的失踪相依的错误讯息， RPM的数据库可能已损坏。 You can try to rebuild RPM database.您可以尝试重建RPM的数据库。 If you’re using cPanel, you can easily rebuild RPM database by clicking on “Rebuild RPM Database” link in Software section which executes “/scripts/dialog?dialog=rebuildrpmdb” script.如果您使用的cPanel ，您可以轻松地重建RPM的数据库，按一下“重建RPM的数据库”链接，软件组执行“ /脚本/对话？对话框= rebuildrpmdb ”脚本。

In above resolution doesn’t work, in order to solve the problem or error, first thing to do is to check whether the RPM package has been installed or not.在上述决议不工作，为了解决问题或错误，要做的第一件事是检查是否有RPM的软件包已经被安装或没有。 The following command can be used to check for the existence of installed glibc-common package:下面的命令可以用于检查存在安装的glibc -共同一揽子方案：

sudo rpm -qa | grep glibc-common sudo的每分钟转速基地| grep glibc的常见
Expected result: glibc-common-2.3.4-2预期结果： glibc的常见- 2.3.4 - 2
or或

rpm -q glibc-common每分钟转速-Q报告g libc的常见
Expected result: glibc-common-2.3.4-2预期结果： glibc的常见- 2.3.4 - 2

or或

yum list glibc-common百胜名单的glibc -共同

Expected result:预期结果：
Installed Packages已安装的软件包
glibc-common.i386 2.3.4-2 installed glibc的- common.i386 2.3.4-2安装
Available Packages可用的软件包
glibc-common.i386 2.3.4-2.9 base glibc的- common.i386 2.3.4-2.9基地

If the glibc-common RPM package is not installed, you can install it with the following command as root user:如果glibc的-共同rpm的包没有安装，您可以安装它与下面的命令作为root用户：

yum install glibc-common百胜安装的glibc -共同

The last command of “yum list glibc-common” is also needed to verify and ensure that the system architecture is matched with the version of glibc and glibc-common installed.最后的命令“荫名单的glibc常见的”还需要验证，并确保该系统的体系结构，是符合版本的glibc和glibc的常见的安装。 Yum is set to respect architecture values, so if you have i386 version for 32-bit x86 system installed, both glibc and glibc-common should be of i386.百胜是设定为尊重建筑的价值观，因此，如果您的I386版本的32位x86系统的安装，无论是glibc的和glibc的常见的应该是的I386 。 It’s the same if you have i586 or i686 for x64 machine architecture.它的同时，如果您有i586或i686 x64的机器架构。 Beside, if you have i686 installed but only i386 version is available in the repository, or if you’re using the x86_64 distribution but with the i386 repository, both situation may cause a failure problem too.旁边，如果您有i686安装，但只的I386版本，可在仓库，或如果您使用x86_64分布，但与上I386存放，双方的情况可能会导致失败的问题。

To display what architecture a distribution of glibc and glibc-common is meant for, type the following command:要显示什么架构分布的glibc和glibc的常见的就是，键入以下命令：

echo “%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}” >> ~/.rpmmacros回声“ ％ _query_all_fmt ％ ％ （名称}-%%{版本}-%%{释放}.%%{拱） ” > > 〜 / 。 rpmmacros

The command alters the way rpm command displays the output of “rpm -q” to a style which also include architecture value (such as rpm_name.arch).命令改变了方式， RPM的命令显示输出的“每分钟转速-Q报告”的风格，其中还包括建筑的价值（如r pm_name.arch） 。 So in above example, you see glibc-common-2.3.4-2, and now you will see libc-common-2.3.4-2.9.i386 instead with the command of “rpm -q glibc-common”.因此，在上面的例子中，你看到的glibc -共同2.3.4 - 2 ，现在你会看到LIBC的常见- 2.3.4 - 2.9.i386 ，而是与指挥“每分钟转速-Q报告g libc的常见” 。 Check out if both glibc and glibc-common is of i386 flavor.检查如果双方的glibc和glibc的常见的是对的I386的味道了。

If you’re on Virtuozzo or OpenVZ virtual server VPS with CentOS and cPanel platform, and getting the error that related to libc-dummy-centos-4 or libc-dummy-centos-3, you can remove the dummy file from SWSoft with the following command:如果您或openvz的Virtuozzo虚拟服务器的电子道路收费与centos和的cPanel平台，并收到错误有关的LIBC的模拟- centos - 4或LIBC的模拟- centos - 3 ，您可以删除虚拟文件从swsoft与以下命令：

yum erase glibc-dummy-centos-3百胜抹掉的glibc -道具- centos - 3

or或

yum erase glibc-dummy-centos-4百胜抹掉的glibc -道具- centos - 4

This will likely solve your problem as glibc-dummy-centos-3/4 no longer subjected to dependencies check and verification.这可能会解决您的问题，作为glibc的模拟- centos - 3 / 4不再受到相依性检查和核查。

IMPORTANT : This is a machine translated page which is provided "as is" without warranty. 重要说明 ：这是一个机器翻译网页是“按原样”提供的担保。 Machine translation may be difficult to understand.机器翻译可能很难理解。 Please refer to请参阅 original English article原来的英语文章 whenever possible.只要有可能。

Share and contribute or get technical support and help at分享和贡献，或取得技术的支持和帮助，在 My Digital Life Forums 我的数字生活论坛 . 。

Related Articles相关文章

• cPanel WHM Failed to Receive Status Information From Apache Error的cPanel的WHM没有收到状态信息从Apache的错误
• Starting Apache HTTPD Failed Due to Cannot Open or No Such mod_bwlimited, mod_log_bytes or mod_bandwidth Files开始的Apache的httpd失败，由于无法打开，或没有这样的mod_bwlimited ， mod_log_bytes或mod_bandwidth档案
• The Call to DllRegisterServer Failed with Error Code 0×80004005 on Windows Vista呼吁的DllRegisterServer失败，错误码0 × 80004005的Windows Vista
• PHP Parse Error: syntax error, unexpected $end PHP的解析错误：语法错误，意想不到的元月底
• Windows Update KB905474 and KB913446 Installation Failed with Error Code 0×80242006在Windows Update 905474和KB913446发布安装失败，错误码0 × 80242006
• PHP 5 Unable to Open HTTP Request Stream with fopen or fsockopen Functions PHP 5中无法打开HTTP请求流与fopen或fsockopen职能
• winnt_accept: Asynchronous AcceptEx failed Error in Apache Log winnt_accept ：异步acceptex失败错误在Apache日志
• BOOTMGR Is Missing During Vista Boot Error bootmgr是失踪期间， Vista的开机错误
• Fix Explorer.exe Unable to Locate Component Because Browseui.dll Was Not Found Error修复的Explorer.exe无法找到组件，因为browseui.dll ，未发现错误
• ESET NOD32 AntiVirus or Smart Security Kernel Virus Scanner and File Submission System Initialization Failed Error eset NOD32防毒或智能安全内核病毒扫描和文件提交系统初始化失败，错误

This entry was posted on Tuesday, February 6th, 2007 at 6:33 pm and is filed under 此项目被张贴于周二， 2007年2月6日在下午6时33分，并提交下 Operating Systems 操作系统 . 。 You can follow any responses to this entry through the 您可以按照任何的反应，此项目通过 RSS 2.0 2.0 feed. 喂养。 You can 您可以 leave a response 留下的回应 , or ，或 trackback Trackback跟踪 from your own site. 从你自己的网站。