After an aborted yum update recently I began to notice ldconfig complaining about a truncated file
Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
Verifying : 1:qt-x11-4.8.4-19.fc19.i686
I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers
Help ?
Thanks
On 06/02/2013 01:12 PM, Frank McCormick wrote:
After an aborted yum update recently I began to notice ldconfig complaining about a truncated file
Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
Verifying : 1:qt-x11-4.8.4-19.fc19.i686
I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers
Further to this I found out the rpm file containing that library is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end .
How to fix ..anyone ?
On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote:
On 06/02/2013 01:12 PM, Frank McCormick wrote:
After an aborted yum update recently I began to notice ldconfig complaining about a truncated file
Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
Verifying : 1:qt-x11-4.8.4-19.fc19.i686
I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers
Further to this I found out the rpm file containing that library is:qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end .
How to fix ..anyone ?
rm /lib/libQtOpenGL.so.4.8.4;51a94e8f
yum reinstall qt-x11
On 06/02/2013 02:06 PM, Sérgio Basto wrote:
On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote:
On 06/02/2013 01:12 PM, Frank McCormick wrote:
After an aborted yum update recently I began to notice ldconfig complaining about a truncated file
Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
Verifying : 1:qt-x11-4.8.4-19.fc19.i686
I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers
Further to this I found out the rpm file containing that library is:qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end .
How to fix ..anyone ?
rm /lib/libQtOpenGL.so.4.8.4;51a94e8f
yum reinstall qt-x11
I'll try removing it first.
On 06/02/2013 06:50 PM, Frank McCormick wrote:
On 06/02/2013 02:06 PM, Sérgio Basto wrote:
On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote:
On 06/02/2013 01:12 PM, Frank McCormick wrote:
After an aborted yum update recently I began to notice ldconfig complaining about a truncated file
Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
Verifying : 1:qt-x11-4.8.4-19.fc19.i686
I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers
Further to this I found out the rpm file containing thatlibrary is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end .
How to fix ..anyone ?
rm /lib/libQtOpenGL.so.4.8.4;51a94e8f
yum reinstall qt-x11
I'll try removing it first.
Doesn't work. Erased the offending files and re installed but ldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ?
On Sun, 2013-06-02 at 19:14 -0400, Frank McCormick wrote:
Doesn't work. Erased the offending files and re installed butldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ?
Have you run out of disk space?
On 06/03/2013 01:09 AM, Adam Williamson wrote:
On Sun, 2013-06-02 at 19:14 -0400, Frank McCormick wrote:
Doesn't work. Erased the offending files and re installed butldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ?
Have you run out of disk space?
No 40% used.
[frank@localhost ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 13831448 5178960 7943220 40% / devtmpfs 501352 0 501352 0% /dev tmpfs 505224 0 505224 0% /dev/shm tmpfs 505224 852 504372 1% /run tmpfs 505224 0 505224 0% /sys/fs/cgroup tmpfs 505224 4 505220 1% /tmp /dev/sda5 222666372 9267220 202081700 5% /media/sda5 /dev/sda7 113656464 5472556 107028088 5% /media/sda7 /dev/sda2 13979216 5701136 7561300 43% /media/sda2
I have since re installed glibc (for ldconfig) and no change. I have Googled the problem but came up with almost nothing - maybe I am using the wrong terms.
On 06/03/2013 02:43 PM, Frank McCormick wrote:
On 06/03/2013 01:09 AM, Adam Williamson wrote:
On Sun, 2013-06-02 at 19:14 -0400, Frank McCormick wrote:
Doesn't work. Erased the offending files and re installed butldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ?
Have you run out of disk space?
No 40% used.
Wild guess: You might have run out of memory due to /tmp on /tmpfs.
I have occasionally hit such issues during yum runs on low RAM machines.
Ralf
On 06/03/2013 09:36 AM, Ralf Corsepius wrote:
On 06/03/2013 02:43 PM, Frank McCormick wrote:
On 06/03/2013 01:09 AM, Adam Williamson wrote:
On Sun, 2013-06-02 at 19:14 -0400, Frank McCormick wrote:
Doesn't work. Erased the offending files and re installed butldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ?
Have you run out of disk space?
No 40% used.Wild guess: You might have run out of memory due to /tmp on /tmpfs.
I have occasionally hit such issues during yum runs on low RAM machines.
Ralf
It's possible I guess...this machine only has one gig and even with barebones windows managers will usually utilize the swap. But that still begs the question how do I fix this truncated file ?
On Sun, Jun 02, 2013 at 07:14:15PM -0400, Frank McCormick wrote:
And what is the ;51a94e8f on the end of the file ?
This is one of temporary suffixes used to create temporary targets when unpacking an update rpm. If you are seeing something of that sort that means that something got screwy and a rename to a "final" form did not happen. I have seen something of that sort on occasions when a package update tried to replace directly a file with a symlink or vice-versa (or another mixup of that sort). What is really messed up in your case it is not really possible to tell from what you are saying but something definitely is.
Michal
On 06/03/2013 04:40 PM, Michal Jaegermann wrote:
On Sun, Jun 02, 2013 at 07:14:15PM -0400, Frank McCormick wrote:
And what is the ;51a94e8f on the end of the file ?
This is one of temporary suffixes used to create temporary targets when unpacking an update rpm. If you are seeing something of that sort that means that something got screwy and a rename to a "final" form did not happen. I have seen something of that sort on occasions when a package update tried to replace directly a file with a symlink or vice-versa (or another mixup of that sort). What is really messed up in your case it is not really possible to tell from what you are saying but something definitely is.
Deleting the file..then removing the rpm and re installing it doesn't change anything. Neither does deleting ldconfig's cache, or re installing GLIBC . It's a resistant error if nothing else.
The good new is it doesn't **seem** to affect any of the software I use on a daily basis. If and when it does, I have 3 other partitions of usable Linux distros :)
On Dom, 2013-06-02 at 19:14 -0400, Frank McCormick wrote:
On 06/02/2013 06:50 PM, Frank McCormick wrote:
On 06/02/2013 02:06 PM, Sérgio Basto wrote:
On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote:
On 06/02/2013 01:12 PM, Frank McCormick wrote:
After an aborted yum update recently I began to notice ldconfig complaining about a truncated file
Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
Verifying : 1:qt-x11-4.8.4-19.fc19.i686
I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers
Further to this I found out the rpm file containing thatlibrary is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end .
How to fix ..anyone ?
rm /lib/libQtOpenGL.so.4.8.4;51a94e8f
yum reinstall qt-x11
I'll try removing it first.
Doesn't work. Erased the offending files and re installed butldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ?
if /lib/libQtOpenGL.so.4.8.4;51a94e8f doesn't exit , and qt-x11 is correctly installed
rpm -V qt-x11 what says ?
ldconfig -i don't fix it ?
-- --Cheers--
On 06/03/2013 11:40 PM, Sérgio Basto wrote:
On Dom, 2013-06-02 at 19:14 -0400, Frank McCormick wrote:
On 06/02/2013 06:50 PM, Frank McCormick wrote:
On 06/02/2013 02:06 PM, Sérgio Basto wrote:
On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote:
On 06/02/2013 01:12 PM, Frank McCormick wrote:
After an aborted yum update recently I began to notice ldconfig complaining about a truncated file
Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
Verifying : 1:qt-x11-4.8.4-19.fc19.i686I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers
Further to this I found out the rpm file containing thatlibrary is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end .
How to fix ..anyone ?
rm /lib/libQtOpenGL.so.4.8.4;51a94e8f
yum reinstall qt-x11
I'll try removing it first.
Doesn't work. Erased the offending files and re installed butldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ?
if /lib/libQtOpenGL.so.4.8.4;51a94e8f doesn't exit , and qt-x11 is correctly installed
rpm -V qt-x11 what says ?
Nothing at all.
/lib/libQtOpenGL.so.4.8.4;51a94e8f does not actually exist, at least not in /lib The file that is there is libQtOpenGL.so.4.8.4 along with two symbolic links pointing to it. Erasing all three, then erasing and re installing qt-x11xxxxxxx does nothing. As was pointed out here already, the file name with those extra characters on the end is a temp file created as part of the install procedure. If it actually exists on the disk , I can't find it.
ldconfig -i don't fix it ?
No it doesn't.
On Tue, Jun 04, 2013 at 12:14:29AM -0400, Frank McCormick wrote:
On 06/03/2013 11:40 PM, Sérgio Basto wrote:
rpm -V qt-x11 what says ?
Nothing at all.
If there is nothing to report then it remains silent.
/lib/libQtOpenGL.so.4.8.4;51a94e8f does not actually exist, atleast not in /lib
So it means that an update completed just fine even if something raised fuss in the process. I really cannot tell why.
The file that is there is libQtOpenGL.so.4.8.4 along with twosymbolic links pointing to it.
So ldconfig did its job. It appears that there is nothing wrong with your installation.
If you are not sure to which packages belongs a specific file you can run a verification step like that:
rpm -Vf /lib/libQtOpenGL.so.4.8.4
where a file you are referencing has to exist.
Michal
On 06/04/2013 01:07 AM, Michal Jaegermann wrote:
The file that is there is libQtOpenGL.so.4.8.4 along with twosymbolic links pointing to it. So ldconfig did its job. It appears that there is nothing wrong with your installation.
There must be something wrong as ldconfig keeps reporting this truncated file which doesn't exist :)
If you are not sure to which packages belongs a specific file you can run a verification step like that:
rpm -Vf /lib/libQtOpenGL.so.4.8.4where a file you are referencing has to exist.
That also reports nothing, so it appears rpm isn't aware of the file/package even though it has been erased and re installed a few times now.
Is there a way to re build the info that rpm has ?
On Tue, 04 Jun 2013 09:42:19 -0400, Frank McCormick wrote:
There must be something wrong as ldconfig keeps reporting thistruncated file which doesn't exist :)
Do you run ldconfig as root? What files /etc/ld.so.cache* do you have? What does "ldconfig -v" show about that library?
If you are not sure to which packages belongs a specific file you can run a verification step like that:
rpm -Vf /lib/libQtOpenGL.so.4.8.4where a file you are referencing has to exist.
That also reports nothing, so it appears rpm isn't aware of thefile/package even though it has been erased and re installed a few times now.
It's _good_ that nothing is reported, because -Vf means "verify the package this file belongs into".
The query to show a package a file belongs into is this: rpm -qf /lib/libQtOpenGL.so.4.8.4
On 06/04/2013 09:57 AM, Michael Schwendt wrote:
On Tue, 04 Jun 2013 09:42:19 -0400, Frank McCormick wrote:
There must be something wrong as ldconfig keeps reporting thistruncated file which doesn't exist :)
Do you run ldconfig as root?
Yes
What files /etc/ld.so.cache* do you have?
[frank@franksfedora19 ~]$ ls /etc/ld.so.cache* /etc/ld.so.cache [frank@franksfedora19 ~]$
What does "ldconfig -v" show about that library?
This comes first ldconfig: Path `/usr/lib' given more than once ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
then the list of the libraries it knows about.
It's _good_ that nothing is reported, because -Vf means "verify the package this file belongs into".
The query to show a package a file belongs into is this: rpm -qf /lib/libQtOpenGL.so.4.8.4
[frank@franksfedora19 ~]$ rpm -qf /lib/libQtOpenGL.so.4.8.4 qt-x11-4.8.4-19.fc19.i686 [frank@franksfedora19 ~]
On Tue, 04 Jun 2013 10:58:59 -0400, Frank McCormick wrote:
Do you run ldconfig as root?
YesWhat files /etc/ld.so.cache* do you have?
[frank@franksfedora19 ~]$ ls /etc/ld.so.cache* /etc/ld.so.cache [frank@franksfedora19 ~]$
What does "ldconfig -v" show about that library?
This comes firstldconfig: Path `/usr/lib' given more than once ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
then the list of the libraries it knows about.
That means the file does exist. How have you searched for the file? Is /lib a link to /usr/lib?
Remove /etc/ld.so.cache* and the file, then run ldconfig again. As root. Be careful that you really let it recreate the cache file.
ldconfig doesn't make up any file names. It processes what it finds. Btw, it understands option -n to process a specific directory only, (ldconfig -n /usr/lib -v).
It's _good_ that nothing is reported, because -Vf means "verify the package this file belongs into".
The query to show a package a file belongs into is this: rpm -qf /lib/libQtOpenGL.so.4.8.4
[frank@franksfedora19 ~]$ rpm -qf /lib/libQtOpenGL.so.4.8.4qt-x11-4.8.4-19.fc19.i686
Expected. That's the lib, which is tracked by the RPM package. The temporary file will never belong into any package (in case you try to run a query for its path).
On 06/04/2013 12:40 PM, Michael Schwendt wrote:
On Tue, 04 Jun 2013 10:58:59 -0400, Frank McCormick wrote:
Do you run ldconfig as root?
YesWhat files /etc/ld.so.cache* do you have?
[frank@franksfedora19 ~]$ ls /etc/ld.so.cache* /etc/ld.so.cache [frank@franksfedora19 ~]$
What does "ldconfig -v" show about that library?
This comes firstldconfig: Path `/usr/lib' given more than once ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated
then the list of the libraries it knows about.
That means the file does exist. How have you searched for the file?
Found it !!! I had been looking adjacent to the original....but it was at the very bottom of the list in the file manager I use (midnight commander) - When you insisted the file did exist, I did another search. It doesn't exist now...and ldconfig is happy:
[frank@franksfedora19 lib]$ sudo ldconfig -v ldconfig: Path `/usr/lib' given more than once /usr/lib/iscsi: libiscsi.so.1 -> libiscsi.so.1.0.10700 /usr/lib/llvm: libLLVM-3.3.so -> libLLVM-3.3.so libprofile_rt.so -> libprofile_rt.so libLTO.so -> libLTO.so etc etc
The temporary file will never belong into any package (in case you try to run a query for its path).
I did and found nothing.
Thanks for all your help.
On Tue, 2013-06-04 at 09:42 -0400, Frank McCormick wrote:
On 06/04/2013 01:07 AM, Michal Jaegermann wrote:
The file that is there is libQtOpenGL.so.4.8.4 along with twosymbolic links pointing to it. So ldconfig did its job. It appears that there is nothing wrong with your installation.
There must be something wrong as ldconfig keeps reporting thistruncated file which doesn't exist :)
If you are not sure to which packages belongs a specific file you can run a verification step like that:
rpm -Vf /lib/libQtOpenGL.so.4.8.4where a file you are referencing has to exist.
That also reports nothing, so it appears rpm isn't aware of thefile/package even though it has been erased and re installed a few times now.
I think some people are missing that the file does not actually exist once the package install process is complete. To me, it sounds like an ldconfig is somehow being run from the package's scriptlets before extraction of the files from the RPM is actually complete.
On 06/04/2013 11:48 AM, Adam Williamson wrote:
On Tue, 2013-06-04 at 09:42 -0400, Frank McCormick wrote:
On 06/04/2013 01:07 AM, Michal Jaegermann wrote:
The file that is there is libQtOpenGL.so.4.8.4 along with twosymbolic links pointing to it. So ldconfig did its job. It appears that there is nothing wrong with your installation.
There must be something wrong as ldconfig keeps reporting thistruncated file which doesn't exist :)
If you are not sure to which packages belongs a specific file you can run a verification step like that:
rpm -Vf /lib/libQtOpenGL.so.4.8.4where a file you are referencing has to exist.
That also reports nothing, so it appears rpm isn't aware of thefile/package even though it has been erased and re installed a few times now.
I think some people are missing that the file does not actually exist once the package install process is complete. To me, it sounds like an ldconfig is somehow being run from the package's scriptlets before extraction of the files from the RPM is actually complete.
This all came about after an update was aborted by a hardware failure. Unfortunately I don't recall what I did after the aborted update...as it was several weeks ago. I **assume** I redid the update and after the next package was handled, ldconfig was run for it.....but the extraction/handling of files from qt-x11 had not been completed. The question now is how I get rid of that "/usr/lib/xxxxxxxx is truncated" warning. Reinstalls and re-running ldconfig after cache deletion doesn't work.
-
Adam Williamson -
Frank McCormick -
Michael Schwendt -
Michal Jaegermann -
Ralf Corsepius -
Sérgio Basto