Bug 812501
| Summary: | ypbind not registered with rpcbind | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Highley <david.m.highley> | ||||||||
| Component: | ypbind | Assignee: | Honza Horak <hhorak> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | hhorak, kklic, michael.glass, tilmann | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | ypbind-1.35-2.fc16 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-04-26 20:06:13 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
David Highley
2012-04-14 03:53:29 UTC
Could you attach output of dmesg to see ordering of services and systemd events during boot? To do so, boot with "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg". Created attachment 577853 [details]
dmesg log from booting system that has ypbind-rpcbind problem
We were having the same bug:
--ypbind not registered with rpcbind at boot (although ypbind seems to be running)
--systemctl restart ypbind.service makes it work
--yum downgrade fixes the problem.
I followed the instructions to log systemd messages. This is the dmesg file that comes out.
The next file will be the /var/log/messages from the same boot.
Created attachment 577854 [details]
/var/log/messages file that corresponds to dmesg file
This is the /var/log/messages file that corresponds to the dmesg file just attached. It starts with the current boot. (The weird times--2000 seconds for rpcbind work---comes from the BIOS time being wrong, and fixed by ntpd.)
Created attachment 578349 [details]
use proper DBus message string
The problem is probably in communication with NetworkManager. A wrong constant is used for listening on DBus, so ypbind don't notice network is ready and waits for a connection forever.
ypbind-1.35-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/ypbind-1.35-2.fc16 ypbind-1.35-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ypbind-1.35-2.fc17 Package ypbind-1.35-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ypbind-1.35-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6135/ypbind-1.35-2.fc17 then log in and leave karma (feedback). I had the same issue and ypbind-1.35-2 fixed it for f16. Thanks! Seems to be fixed now, thanks. Seems fixed our our FC16 systems also. ypbind-1.35-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. ypbind-1.35-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |