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.
Description of problem:
Due to various issues with systemd user instances, the admin may want to mask the user@.service unit to stop spawning systemd user instances.
When doing so, every time a user logs in, the following Error message is printed:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Failed to start user service, ignoring: Unit user@<UID>.service is masked.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
This is confusing to the admin and create false alarms.
This BZ is a request to backport Upstream's code, which basically hides the message when user@.service is masked:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
340 static void user_start_service(User *u) {
:
352 r = manager_start_unit(u->manager, u->service, &error, &u->service_job);
353 if (r < 0)
354 log_full_errno(sd_bus_error_has_name(&error, BUS_ERROR_UNIT_MASKED) ? LOG_DEBUG : LOG_WARNING, r,
355 "Failed to start user service '%s', ignoring: %s", u->service, bus_error_message(&e rror, r));
356 }
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Version-Release number of selected component (if applicable):
systemd-239
How reproducible:
Always
Steps to Reproduce:
1. Mask user@.service
# systemctl mask user@.service
2. Log in as a new user
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 (Moderate: systemd security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:1611
Description of problem: Due to various issues with systemd user instances, the admin may want to mask the user@.service unit to stop spawning systemd user instances. When doing so, every time a user logs in, the following Error message is printed: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Failed to start user service, ignoring: Unit user@<UID>.service is masked. -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- This is confusing to the admin and create false alarms. This BZ is a request to backport Upstream's code, which basically hides the message when user@.service is masked: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 340 static void user_start_service(User *u) { : 352 r = manager_start_unit(u->manager, u->service, &error, &u->service_job); 353 if (r < 0) 354 log_full_errno(sd_bus_error_has_name(&error, BUS_ERROR_UNIT_MASKED) ? LOG_DEBUG : LOG_WARNING, r, 355 "Failed to start user service '%s', ignoring: %s", u->service, bus_error_message(&e rror, r)); 356 } -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Version-Release number of selected component (if applicable): systemd-239 How reproducible: Always Steps to Reproduce: 1. Mask user@.service # systemctl mask user@.service 2. Log in as a new user