Bus error

jcci · 2007-09-22 02:58:59

Since the last update on Sept.21st lots of applications fail by a "bus error" which is pretty serious as it makes the systems almost unusable. I could confirm this problem for 4 Arch32 computer and 3 Arch64 computer, so I believe it will happen to any computer after the update.
My failure list so far:
gdm
sshd
wget
openoffice

The wget failure stops pacman, so you can not have any further updates as long as you don't outcomment the following line in the pacman.conf:
# XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

Last edited by jcci (2007-09-22 03:17:24)

fwojciec · 2007-09-22 03:32:06

jcci wrote:

Since the last update on Sept.21st lots of applications fail by a "bus error" which is pretty serious as it makes the systems almost unusable. I could confirm this problem for 4 Arch32 computer and 3 Arch64 computer, so I believe it will happen to any computer after the update.
My failure list so far:
gdm
sshd
wget
openoffice
The wget failure stops pacman, so you can not have any further updates as long as you don't outcomment the following line in the pacman.conf:
# XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u

All works fine on my computer and I have just rebooted to see if I could reproduce the problem. Try downgrading the packages that were upgraded today (look in /var/log/pacman.log). The older versions of packages can be found in /var/cache/pacman/pkg and can be installed by running pacman -U /path/to/package/file.

I hope this helps.

jcci · 2007-09-22 03:54:08

After replacing the following libs from a non-updated computer openssh works again:
libcrypto.so.0.9.8 libcrypto.so (hardlink)
When re-installing openssh and wget there is a warning message about the 2 libs being "truncated".
Openoffice recovered with re-install, but for all Arch32 computer just overwriting the above libs solved the problem. The machines are all different so I expect this to be a common issue. Beside pacman Syu nothing has been done.
wget still complaints as followed: /usr/bin/wget: symbol lookup error: /usr/lib/libssl.so.0.9.8: undefined symbol: __ASN1_dup

By the way: How to check to which package these libs belong?

Last edited by jcci (2007-09-22 03:58:21)

fwojciec · 2007-09-22 04:01:11

The libs you mentioned are owned by openssl. That package was updated yesterday on my computer:

[2007-09-20 09:19] upgraded openssl (0.9.8e-3 -> 0.9.8e-5)

Copying the libs from another computer is a pretty crude hack - even if it works - I'd try to downgrade the openssl package and see if that solves the issue. By the way, this upgrade seems to have had no negative effects on my systems (a desktop and a laptop).

Last edited by fwojciec (2007-09-22 04:02:44)

fwojciec · 2007-09-22 04:02:12

jcci wrote:

By the way: How to check to which package these libs belong?

like this:

pacman -Qo /usr/lib/libcrypto.so

jcci · 2007-09-22 04:09:06

Thanks for the quick reply!
The point is: I did try to downgrade openssh and has the old version in the cache. But it didn't help. I know the hack is crude, but it is reversible any time as well. I do have enough troublesome machines right now, sharing one pacman cache through nfs.

Last edited by jcci (2007-09-22 04:11:12)

fwojciec · 2007-09-22 04:09:53

jcci wrote:

Thanks for the quick reply!
The point is: I did try to downgrade openssh and has the old version in the cache. But it didn't help. I know the hack is crude, but it is reversible any time as well. I do have enough troble machines right now, sharing one pacman cache through nfs.

I think you need openssl - not openssh I'm just trying to come up with an idea of what is happening so I can suggest something useful to the guy in the other thread. So if you could check if that works as a solution I'd appreciate it since I can't reproduce the problem here.

Last edited by fwojciec (2007-09-22 04:11:27)

jcci · 2007-09-22 04:13:48

Yes, of course - sorry!
Unfortunately there is no old version of openssh in the cache. At least I didn't remove it.

Anyway, definitely a fix for openssh is required!

Last edited by jcci (2007-09-22 04:14:51)

jcci · 2007-09-22 04:21:09

By your nice pacman use instruction I found that all troublesome libs are owned by openssl.
Unfortunately there is just yesterdays version in the cache.
So, the fix should be for openssl, right?

fwojciec · 2007-09-22 04:23:11

I think the theory with openssl is a good one, and, who knows, maybe it will fix the problem with openssh and wget (or at least it should allow you to reinstall them without problems).

Try running something like this:

sudo pacman -U /var/cache/pacman/pkg/openssl-0.9.8e-3.pkg.tar.gz

I can't guarantee that the package file name will be the same on a 64bit machine (I'm on 32 bit here).

If that works you can add openssl to IgnorePkg in pacman.conf for now (which will prevent the downgraded package from being upgraded during pacman -Syu) and hopefully the devs will come up with a solution soon.

fwojciec · 2007-09-22 04:24:20

jcci wrote:

By your nice pacman use instruction I found that all troublesome libs are owned by openssl.

That's what I was trying to say above, but I guess we had a miscommunication of sorts - "openssl" and "openssh" are very similar names.

jcci · 2007-09-22 04:45:09

After further digging I found this concerning openssl (http://bbs.archlinux.org/viewtopic.php?id=37557):
"The broken package was only online for an hour before I realized it was broken, I am surprised how many users actually installed it in that short time. I was rather surprised when psi stopped working.

openssl has been rebuilt without changes to the PKGBUILD, but there is a bug that makes it break with gcc 4.2, which we haven't used to build it last time (a few months ago). I apologize for any inconvenience."

But the package wasn't renamed, so pacman didn't update anymore. All my computers got affected due to the shared cache. After manually deleting the openssh package from the cache and re-installing from a fresh download it works again. Hallelujah!
So to ejt122390 and anybody else who upgraded during "the magic hour": remove openssl 0.9.8e-5 from the pacman cache (rm /var/cache/pacman/pkg/openssl-0.9.8e-5-i686.pkg.tar.gz), pacman -S openssl and that's it. pacman Sy openssl may not work due to broken wget. After re-installing you can check wget simply by pacman -Sy.

Thanks to everybody for being a great community!

Last edited by jcci (2007-09-22 04:49:20)

fwojciec · 2007-09-22 04:57:10

I'm glad you were able to come up with the solution - hopefully ejt122390 will be able to solve it as well once he gets back online.

regomodo · 2008-02-10 23:06:19

um, sorry to necrobump but i'm getting a load of bus errors with openssh-4.7p1-6
i get 4 errors 6605-6608 and at the end of the line it mentions /usr/bin/ssh-keygen -t rsa1 or rsa or dsa and fot eh last $SSHD_ARGS

I've used ssh in arch a lot in the past and with fresh install on a different computer i am not only getting these ssh bus errors but also this "/usr/lib/libcrypto.so is truncated error" just like the OP.

Can anybody help?

Arch Linux

#1 2007-09-22 02:58:59

Bus error

#2 2007-09-22 03:32:06

Re: Bus error

#3 2007-09-22 03:54:08

Re: Bus error

#4 2007-09-22 04:01:11

Re: Bus error

#5 2007-09-22 04:02:12

Re: Bus error

#6 2007-09-22 04:09:06

Re: Bus error

#7 2007-09-22 04:09:53

Re: Bus error

#8 2007-09-22 04:13:48

Re: Bus error

#9 2007-09-22 04:21:09

Re: Bus error

#10 2007-09-22 04:23:11

Re: Bus error

#11 2007-09-22 04:24:20

Re: Bus error

#12 2007-09-22 04:45:09

Re: Bus error

#13 2007-09-22 04:57:10

Re: Bus error

#14 2008-02-10 23:06:19

Re: Bus error

Board footer