How Does One Fix Or Otherwise Remove Prelinking Errors On CentOS 5
Nov 28, 2007
We regular see the following errors in our CentOS 5 64-bit and 32-bit (the 32-bit has less errors, but all the same - dealing with prelinking):
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/sbin/lsof: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/addr2line: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/ar: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/as: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/c++filt: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/gprof: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/ld: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/nm: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/objcopy: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/objdump: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/ranlib: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/readelf: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/size: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/strings: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/strip: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /sbin/chkconfig: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/sbin/alternatives: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/basename: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/cat: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/chgrp: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/chmod: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/chown: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/cp: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/cut: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/date: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/dd: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/df: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/echo: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/env: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/false: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/link: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/ln: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/ls: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/mkdir: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/mknod: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/mv: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/nice: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/pwd: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/rm: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/rmdir: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/sleep: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/sort: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/stty: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/sync: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/touch: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/true: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/uname: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /bin/unlink: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /sbin/runuser: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/[: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/base64: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/chcon: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/cksum: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/comm: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/csplit: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/dir: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/dircolors: at least one of file's dependencies has changed since prelinking
prelink: /lib64/libc-2.5.so has a dependency cycle
prelink: /usr/bin/dirname: at least one of file's dependencies has changed since prelinking
How can we fix these errors or otherwise remove them?
I am sorry. We are not able to resolve the File Does Not Exist errors for you. You have to do it own.
The unique errors that you have today for Apache are as follows:
client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): /w00tw00t.at.ISC.SANS.DFind File does not exist: /usr/local/apache/htdocs File does not exist: /usr/local/apache/htdocs/501.shtml File does not exist: /usr/local/apache/htdocs/images, referer: [url] File does not exist: /usr/local/apache/htdocs/jailbreak-iphone-3-0-1-with-redsn0w File does not exist: /usr/local/apache/htdocs/robots.txt Invalid method in request x16x03x01 Invalid method in request x80bx01x03x01 # Invalid URI in request alt="Follow%20via%20FreiendFFeed"%20title="Follow%20via%20FriendFeed"%20border="0"%20height="16"%20width="16"%20/>Home Top%20StuffiPhoneWindows%207FirefoxVistaTipsWordpressSubscribeSitemapAdvertise xc2xa0xc2xa0xc2xa0Vertical1240899%20=%20false;ShowAdHereBanner1240899%20=%20true;RepeatAll1240899%20=%20false;NoFollowAll1240899%20=%20false;Ban nerStyles1240899%20=%20new%20Array(%20%20%20%20"a{display:block;font-size:11px;color: HTTP/1.1 PHP Fatal error: Call to a member function get() on a non-object in /home/technob2/public_html/wp-includes/cache.php on line 93 PHP Fatal error: Call to a member function get() on a non-object in /home/technob2/public_html/wp-includes/cache.php on line 93, referer: [url] PHP Fatal error: Call to a member function get() on a non-object in /home/technob2/public_html/wp-includes/cache.php on line 93, referer: [url] PHP Fatal error: Call to a member function get() on a non-object in /home/technob2/public_html/wp-includes/cache.php on line 93, referer: [url] PHP Fatal error: Call to a member function get() on a non-object in /home/technob2/public_html/wp-includes/cache.php on line 93, referer: [url] request failed: error reading the headers
I would advise that you resolve as many of these errors as you are able.
As to what caused the load on your server, I can't say. There is nothing in your logs to indicate the source of the problem. During the 1PM period when your server overloaded last there were only 29 errors in Apache. The errors that occurred during this time would not cause excessive load.
I have installed a script to monitor your server. If this load issue occurs again within one week or before your next reboot, whichever comes first, we should be able to determine the source from the script's logs in /var/log/sys-snap.sh.
[xcache.coverager] xcache.coverager = Off xcache.coveragedump_directory = ""
If I open phpinfo I can see that xcache is loaded and can see the settings, I have also installed the xcache admin panel and I am able to access that without problem.
However if I enable xcache on in the PHP scripts (vbulletin) file I get multiples of the following errors:
Quote:
Warning: xcache_isset() [function.xcache-isset]: xcache.var_size is either 0 or too small to enable var data caching in [path]includesclass_datastore.php on line 557
Quote:
Warning: xcache_unset() [function.xcache-unset]: xcache.var_size is either 0 or too small to enable var data caching in [path]includesclass_datastore.php on line 596
Quote:
Warning: xcache_set() [function.xcache-set]: xcache.var_size is either 0 or too small to enable var data caching in [path]includesclass_datastore.php on line 597
Now unless I am being thick, var_size is currently set to 128M, it was originally 4M but as the error suggested "too small" I upped it a little with no affect.
The only thing I can think might be related to this is that I am using PHP 5.2.6 and I am using xCache 1.2.2 for PHP 5.2.5 as there is no 5.2.6 version
ive got a site which auto creates subdomains and installs a script automaticly and inserts details into a mysql db. i have had some issues recent so have loads (talking 100s) of folders that are empty which i need to remove, and to remove the details of said folder from db also. any ideas how i can do this, using plesk control panel so removing the subdomain via plesk cli may be the best way in that respect but the db is external to plesk so that would not be edited
I'm noticed I was getting bounced email errors from a company I was sending email through and I further investigated this by running a dnsreport on my domain.
Turns out that it fails at Acceptance of NULL <> sender, Acceptance of postmaster address, and Acceptance of abuse address. The domain that I ran a test on is using a new IP that I had recently added to my Direct Admin server. None of the other domains on my server are having issues like this.
Is is possible that I need to do something to enable these new IP addresses in exim? I mean, exim obviously responds to that IP address, but it seems to be having some issues with it.
I have setup a xen VPS some time back. I need to remove it permanently. I have used the commands virsh destroy <domainID> as well as xm destroy <domainID>. However they only performs a shutdown. I can restore it back!
I want to remove / wipe it permanently and memory consumed is given up then and reflected in the core server.
My /tmp on my cPanel hosting server is nearly full, and I was wondering if it is safe to remove all the contents in /tmp, if not, what can I delete to clear up the space?
My server has 2 drives,one is backup drive. The backup drive seem to be failing so i decide to remove it. However when i remove it,the system can not boot. ANyone got this issue?
The way Exim is setup on Cpanel/Centos is that it adds the origination IP and server IP address that the email is relayed through.
Because many RBL's flag Verizon and Comcast ISP IP's as spam sources; it causes my email relayed through my server to be rejected. Note: My server IP is not on any RBL for spam or abuse.
Is there a way to edit Exim to only use the server IP adddress that I relay through?
