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. 從你自己的網站。