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!
(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?
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
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.