Tag Info

Hot answers tagged

12

You can control address selection with /etc/gai.conf. The configuration file is well documented, and already contains the defaults, so you can just begin tweaking. The interesting defaults here are: label ::1/128 0 label ::/0 1 label 2002::/16 2 label ::/96 3 label ::ffff:0:0/96 4 precedence ::1/128 50 precedence ...


9

Make sure you have your development tools installed: yum groupinstall "Development Tools" Grab the src rpm: wget http://xmlsoft.org/sources/libxml2-2.7.8-1.src.rpm you won't be able to call rpmbuild directly, due to rpm version differnces, so lets short circuit that: rpm -ivh libxml2-2.7.8-1.src.rpm --nomd5 then: rpmbuild -ba ...


6

Glibc is one of the core libraries on a Linux system. It is a.ordinary reason why upgrading from CentOS 5 to 6 isnt recommended without a reinstall. In short mucking with those libraries has a high chance of rendering your system unbootable.


6

Hmm. glibc 2.5 is a dependency on pretty much everything in CentOS5. If you change it to glibc 2.7, your box will explode. Here's some discussion over in the CentOS forums: https://www.centos.org/modules/newbb/viewtopic.php?topic_id=28345&forum=41 https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=27133&forum=38


6

Your problem is described on http://udrepper.livejournal.com/20948.html, and is caused by a parallel lookup on both IPv4 and IPv6 which doesn't work together with some DNS servers and firewalls. It can be fixed by adding "single-request" to the options in /etc/resolv.conf as the link above mentions.


4

This message means that there is a bug either in httpd, one in of its loaded modules or in its execution environment (libraries, OS, hardware). The technical explanation of the bug is that part of the httpd process kept a pointer to a block of memory around even though the memory had already been freed for other use. In this instance, the error was caught, ...


4

Do what it told you to do. There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. The program yum-complete-transaction is found in the yum-utils package. Once that completes, run yum distro-sync to bring your system back in sync with the repositories. Now, you have duplicate entries in the ...


4

Yeah this is so not the end of the world. You'll want to boot using a rescue CD - which for CentOS means the installation media. At the boot prompt, enter linux rescue You will be presented with an option to mount your filesystem in read/write mode, mount it in read only mode, or skip mounting it. Select the option to mount in read/write mode. Your ...


4

The best thing to do in this case by far is to boot the server using a livecd, mount the applicable partitions, and create the symlink (be careful that the symlink points to exactly the right place when doing this, as if it points to a different absolute path than when you are running, it will not be helpful). I can't think of a program you can run which ...


3

OK, here's a completely different answer. Place the offending hosts with crappy IPv6 connectivity in /etc/hosts with their corresponding IPv4 address. For example: 199.7.53.74 whois.verisign-grs.com Remember to remove them when their (in this case) or your IPv6 connectivity improves.


3

CentOS 5.x is based around GLIBC version 2.5. The version of fpcalc that you have is compiled against GLIBC 2.7. You will need to compile fpcalc against the C library available for your system. The source code seems to be available here.


3

It is often possible to compile up a fresher libc, and have one piece of software use a different library to everyone else. The biggest painpoint between libc versions is thread local storage, IIRC. If you're passing this milestone, all bets are off. Having said all that - I would strongly recommend that you simply upgrade the distro to something modern. ...


3

In the subject, you say that the machine is running Debian 3.1 (Sarge). However, the glibc dependency and error messages you have posted indicate that you are trying to install packages from Debian 5.0 (Lenny). This probably means your /etc/apt/sources.list file references stable rather than sarge (i.e. you are taking packages from the latest stable release ...


3

Your system is missing the gzip library development files. Try yum install zlib-devel ... that should resolve your issue.


2

link statically(-static) use rpath. rpath overwrite the default search path(-rpath,/srv/myapp/lib)


2

Apparently, I found a command that will work [ex@uid377 ~]$ echo 'help!' >& .bashrc This overwrote the .bashrc and I was able to log back in. In retrospect doing export LD_LIBRARY_PATH='' would also fix this problem.


2

Your Apache or one of it's modules has crashed. This could be a hardware problem or it could be a bug in Apache or one of it's modules. Diagnosing it could be quite difficult. Update your Apache and it's modules to the latest version for your OS/Distro. Put it all on different hardware File a bug report with the Apache group.


2

glibc-2.12-1.80.el6_3.6 is the latest updated package for glibc in RHEL6. I am certain that a package like glibc will not be rebased to v3. If you are doing this on a production RHEL server, the simple rule is don't, don't do it. For testing purpose, feel free to add the fedora repo or rpmforge or whatever gives you the latest one. But, I am quite sure you ...


2

I guess it's libc's default/ fallback behaviour. Tried to reconstruct what you did. This stops, if you change your nsswitch.conf-entry to: hosts: files See also this hint: http://sourceware.org/ml/libc-alpha/2009-02/msg00028.html See 'man 5 resolv.conf': If this file doesn't exist the only name server to be queried will be on the local machine; ...


2

Stop the install command and rebuild your rpm database. You should be able to: rm /var/lib/rpm/__db* Then: rpm --rebuilddb Then attempt your installation again.


2

I have been experiencing exactly the same issue. I tried following the accepted answer above and found I couldn't remove very much because of preexisting dependencies. In the end, I installed yum-utils and ran the following: package-cleanup --dupes This sorted everything out straight away. I was then able to yum update to update Apache, which is what I ...


2

When in doubt, head over to the source code! So, let's see... gethostbyname() looks interesting; that describes exactly what we're seeing: try IPv6 first, then fall back to IPv4 if you don't get an answer you like. What's this RES_USE_INET6 flag? Tracing it back, it's coming from res_setoptions(). This is where resolv.conf is read in. And.... that's me ...


1

While I personally would have used the php-pear-* packages provided by EPEL (with the php-pear package coming from CentOS itself), I don't really see the problem. The installer script says the pear executable was installed - is it working as expected or not? If not, please post that error. I tend to disergard error messages about temporary files in /tmp - ...


1

The GLibC in EL should not be updated outside of what the distribution creator provides as it could cause issues with existing software; that software is not runnable on CentOS 5 without recompilation.


1

There is no libc6 package in Red Hat Enterprise Linux. The package name for the same files is glibc. It appears that someone installed a package on your server from a different Linux distribution, and overrode the errors they would have received upon attempting to do so (which are just about the same as those you saw here). This of course puts your RPM ...


1

The discussions you may have seen are correct... See here, here, here, and here. You can't change glibc versions on CentOS 5. You'll need an upgrade to a newer version of RHEL/CentOS. EL6 ships with glibc 2.12: Name : glibc Relocations: (not relocatable) Version : 2.12 Vendor: CentOS Of ...


1

It looks like: yum wants to update glibc-common-2.12-1.80.el6_3.3.x86_64 to glibc-comon-2.12-1.80.el6_3.5.x86_64 the glibc-common:i686 package needs to stay in lockstep with glibc-common:x86_64 the latest version of glibc-common:i686 available is glibc-common-2.12-1.80.el6_3.3.i686 hence, it cannot resolve the two So it appears that ...


1

You can refer to this compatibility table to determine binary-compatible versions. Usually it's not a problem to upgrade glibc to a newer version, but you should build it with the same configuration flags as used in your distribution (see spec file in the appropriate srpm package).


1

You built PhantomJS on a much newer system than the one you're trying to deploy it on. Rebuild it on a system matching the deployment system.


1

Can someone please help? Actually, no. glibc is a core part of the distro and cannot be upgraded casually. Rebuild OO from source.



Only top voted, non community-wiki answers of a minimum length are eligible