Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The httpd package installation script tried to create both the "apache" user and group in a single "useradd" command. Consequently, when the "apache" group had already been created on the system, the command failed, and the "apache" user was not created. To fix this bug, the "apache" group is now created by a separate command, and the "apache" user is correctly created during httpd installation even when the "apache" group exists.
Description of problem:
When installing httpd via yum and apache group already exists on the system (for example when it is defined in IDM), installation is not able to create apache user:
warning: user apache does not exist - using root
Problem is caused by way the new user is created:
/usr/sbin/useradd -c "Apache" -u 48 \
-s /sbin/nologin -r -d /usr/share/httpd apache 2> /dev/null || :
This causes httpd unable to start.
Version-Release number of selected component (if applicable):
RHEL 7.2
httpd 2.4
How reproducible:
By creating group apache and than trying to install httpd.
Steps to Reproduce:
1. groupadd apache --gid=48
2. yum install httpd
Actual results:
Error message: warning: user apache does not exist - using root
httpd unable to start
Expected results:
Smooth installation of httpd. httpd is able to start.
Additional info:
We found this issue thanks to enclosed support case. The problem here was, that customer had apache group defined in IDM.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-2534.html
Description of problem: When installing httpd via yum and apache group already exists on the system (for example when it is defined in IDM), installation is not able to create apache user: warning: user apache does not exist - using root Problem is caused by way the new user is created: /usr/sbin/useradd -c "Apache" -u 48 \ -s /sbin/nologin -r -d /usr/share/httpd apache 2> /dev/null || : This causes httpd unable to start. Version-Release number of selected component (if applicable): RHEL 7.2 httpd 2.4 How reproducible: By creating group apache and than trying to install httpd. Steps to Reproduce: 1. groupadd apache --gid=48 2. yum install httpd Actual results: Error message: warning: user apache does not exist - using root httpd unable to start Expected results: Smooth installation of httpd. httpd is able to start. Additional info: We found this issue thanks to enclosed support case. The problem here was, that customer had apache group defined in IDM.