Bug 172398 - preinstall script runs adduser which does not exit
preinstall script runs adduser which does not exit
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openssh (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-11-03 14:53 EST by drew.middlesworth
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-03 15:27:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description drew.middlesworth 2005-11-03 14:53:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 CentOS/1.7.12-1.4.1.centos4

Description of problem:
When upgrading to openssh-server-3.9p1-8.RHEL4.9 from an older version using yum, the preinstall script:
preinstall scriptlet (using /bin/sh):
/usr/sbin/useradd -c "Privilege-separated SSH" -u 74 \
        -s /sbin/nologin -r -d /var/empty/sshd sshd 2> /dev/null || :

runs useradd which sits in a tight loop using up CPU. This process also cannot be killed even with a kill -9. This only happens on x86_64, and not i386.

I have duplicated this 3 times on 3 different x86_64 installations

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Upgrade RHEL from 4.1 to 4.2 on x86_64

Actual Results:  useradd sits in a tight loop using cpu, and the yum upgrade will not continue.

Expected Results:  the package should have been upgraded normally

Additional info:
Comment 1 Tomas Mraz 2005-11-03 15:27:20 EST
1. Upgrading RHEL using yum is not supported.
2. This is definitely not a bug in openssh.
3. This is most probably some problem with kernel and upgrade of auditd.
4. Try to upgrade the kernel first.

Note You need to log in before you can comment on or make changes to this bug.