Description of problem: On a Fedora 32 system having freshly been upgraded from f31, journalctl reports this: .... Apr 30 16:45:03 troy systemd[1514]: pam_unix(systemd-user:session): session opened for user troy by (uid=0) Apr 30 16:45:03 troy systemd[1514]: yp_bind_client_create_v3: RPC: Remote system error - Cannot allocate memory Apr 30 16:45:03 troy systemd[1514]: systemd: clnt_dg_create: out of memory Apr 30 16:45:03 troy systemd[1514]: yp_bind_client_create_v3: RPC: Remote system error - Cannot allocate memory Apr 30 16:45:03 troy systemd[1514]: systemd: clnt_dg_create: out of memory Apr 30 16:45:03 troy systemd[1514]: yp_bind_client_create_v3: RPC: Remote system error - Cannot allocate memory Apr 30 16:45:03 troy systemd[1514]: systemd: clnt_dg_create: out of memory Apr 30 16:45:03 troy systemd[1514]: yp_bind_client_create_v3: RPC: Remote system error - Cannot allocate memory Apr 30 16:45:03 troy systemd[1514]: systemd: clnt_dg_create: out of memory ... Version-Release number of selected component (if applicable): systemd-245.4-1.fc32.x86_64 rpcbind-1.2.5-5.rc1.fc32.1.x86_64 ypbind-2.6.1-2.fc32.x86_64 How reproducible: I am not sure. I am observing this issue on several machines. Also, so far I have only seen this happen shortly after booting up and/or upon the first remote ssh-login attempt. Steps to Reproduce: 1. boot up system 2. try to ssh into the system from remote Actual results: - Journalctl reports above - The ssh-login takes quite a long time (30secs - 1 min). Expected results: - No errors - Fast log ins Additional info: - I am using nis/yp and autofs mounted nfs homes. - This is regression to fc31. f31 did not exhibit these issues.
Thanks for Your report. from my point of view it's same issue like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1705641 Please try to apply the proposed fix and test, if your issue persists or not. If fix helps please move this bug to libtirpc component.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.