This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1953554 - ipa-otpd.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Resource temporarily unavailable
Summary: ipa-otpd.socket: Failed to queue service startup job (Maybe the service file ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: beta
: ---
Assignee: Michal Sekletar
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-26 11:32 UTC by Aleksandr Sharov
Modified: 2023-09-21 11:13 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 11:13:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5873 0 None Migrated None 2023-09-21 11:11:47 UTC

Description Aleksandr Sharov 2021-04-26 11:32:17 UTC 
Description of problem:
ipa-otpd is a service that is ran on-demand. Normally Dirserv breaks idle connection after some timeout, and ipa-optd fails, then starts again if needed.

It seems that it can't get it's socket to start in this installation:

Apr 17 12:57:49 ipa-ba1.ipa.orange.sk systemd[1]: ipa-otpd.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Resource temporarily unavailable
Apr 17 12:57:49 ipa-ba1.ipa.orange.sk systemd[1]: ipa-otpd.socket: Failed with result 'resources'.


[root@idm0 slapd-AGDSN-DE]# sd status ipa-otpd
● ipa-otpd - ipa-otpd service (PID 848960/UID 0)
   Loaded: loaded (/usr/lib/systemd/system/ipa-otpd@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2021-03-31 21:29:58 UTC; 1min 1s ago
  Process: 2322932 ExecStart=/usr/libexec/ipa/ipa-otpd $ldap_uri (code=exited, status=1/FAILURE)
 Main PID: 2322932 (code=exited, status=1/FAILURE)

Mar 31 21:28:58 myhost ipa-otpd[2322932]: LDAP: ldapi://%2fvar%2frun%2fslapd-AGDSN-DE.socket
Mar 31 21:28:58 myhost ipa-otpd[2322932]: lukasjuhrich: request received
Mar 31 21:28:58 myhost ipa-otpd[2322932]: lukasjuhrich: user query start
Mar 31 21:28:58 myhost ipa-otpd[2322932]: lukasjuhrich: user query end: uid=lukasjuhrich,cn=users,cn=accounts,dc=agdsn,dc=de
Mar 31 21:28:58 myhost ipa-otpd[2322932]: lukasjuhrich: bind start: uid=lukasjuhrich,cn=users,cn=accounts,dc=agdsn,dc=de
Mar 31 21:28:58 myhost ipa-otpd[2322932]: lukasjuhrich: bind end: success
Mar 31 21:28:58 myhost ipa-otpd[2322932]: lukasjuhrich: response sent: Access-Accept
Mar 31 21:29:58 myhost ipa-otpd[2322932]:     bind.c:088: Input/output error: IO error received on bind socket
Mar 31 21:29:58 myhost systemd[1]: ipa-otpd: Main process exited, code=exited, status=1/FAILURE
Mar 31 21:29:58 myhost systemd[1]: ipa-otpd: Failed with result 'exit-code'.

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

systemd-219-42.el7_4.10.x86_64
ipa-common-4.5.4-10.el7_5.1.noarch

How reproducible:
on clients side - always, could not reproduce in lab

Actual results:


Expected results:
ipa-otpd restarts succesfully

Additional info:
sosreport can be found in the attached case

As I consulted with IPA dev team, this needs to be investigated from systemd side. If it's IPA's bug - please revert it to IPA. Thank you!
Comment 1 David Tardon 2021-04-27 07:30:24 UTC 
(In reply to Aleksandr Sharov from comment #0)
> Version-Release number of selected component (if applicable):
> 
> systemd-219-42.el7_4.10.x86_64
> ipa-common-4.5.4-10.el7_5.1.noarch

So what RHEL version is this problem happening on: RHEL 8, as stated by the bug; or 7, as indicated by the package versions?
Comment 2 Aleksandr Sharov 2021-04-27 09:06:23 UTC 
Hi David,

thank you for looking into this. Well, that's a good question! As per sosreport:

[asharov@supportshell sosreport-ipa-ba1-2021-04-17-nlnlzrj]$ cat sos_commands/subscription_manager/subscription-manager_list_--installed 
+-------------------------------------------+
    Installed Product Status
+-------------------------------------------+
Product Name:   Red Hat Enterprise Linux for x86_64
Product ID:     479
Version:        8.3
Arch:           x86_64
Status:         Subscribed
Status Details: 
Starts:         11/20/19
Ends:           11/20/22

But the packages I provided are incorrect. Sorry about that, must have looked somewhere else. Actual packages are

ipa-server-4.8.7-16.module+el8.3.0+10289+b6566038.x86_64    Fri Apr 16 21:53:11 2021
systemd-239-41.el8_3.2.x86_64                               Fri Apr 16 21:52:53 2021

Best regards,
Aleksandr Sharov
Red Hat EMEA
Comment 17 Abhinay Reddy Peddireddy 2023-08-06 08:02:38 UTC 
However looking for further updates on this bugzilla in regards to other cases attached. 

May I know do we have any update on the progress of this bugzilla ? 

Marking needinfo again.
Comment 19 RHEL Program Management 2023-09-21 11:08:24 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 20 RHEL Program Management 2023-09-21 11:13:28 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.