yum/rpm failing with pre or post script errors + sshd
David Timms
dtimms at iinet.net.au
Thu Apr 10 00:02:30 UTC 2008
seth vidal wrote:
> On Wed, 2008-04-09 at 19:07 +1000, David Timms wrote:
>> Rex Dieter wrote:
>>> David Timms wrote:
>>>
>>>> I'm having trouble on only one of two test machines.
>>>>
>>>> when I yum update, I see a lot of:
>>>> Updating : at-spi
>>>> error: %post(at-spi...) scriptlet failed, exit status 255.
>>> Bugzilla please (against at-spi). pkg scriplet's should never fail.
>> Actually every package generates these same errors. I don't think we
>> really want 500 bugzilla items. I don't really want to update at the
>> moment because it just causes more failed rpm transactions.
>>
>> Any ideas for what the underlying cause might be ?
>>
>> Actually, attempting to start sshd on that machine also fails:
>> # service sshd start
>> Starting sshd: /usr/sbin/sshd: error while loading shared libraries:
>> libwrap.so.0: cannot open shared object file: No such file or directory
>> [FAILED]
>>
>> # sshd
>> sshd re-exec requires execution with an absolute path
>>
>> Think it is related ?
>
> just for fun, put selinux in permissive mode, then retry it.
>
> I wonder if something is unhappy in one of your protections.
setenforce 0
Aha. now package-cleanup --cleandupes runs to completion; I'm back on track.
To get it back happy: touch /forcefsck and touch /.autorelabel
Boots OK, and package updates are completing normally now. I'm thinking
it may have been a hang over from the upgrade that didn't go to
completion - however, updates had been working OK for the first few days.
Thanks, DaveT.
More information about the fedora-test-list
mailing list