| Summary: | ypbind stops functioning after: mock init | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rex Dieter <rdieter> |
| Component: | ypbind | Assignee: | Honza Horak <hhorak> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | hhorak, jesusr, kklic |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-07 09:18:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Rex Dieter
2011-08-18 18:50:49 UTC
Can you see some differences in dmesg output, if you boot with verbose systemd (log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg)? Or any other messages that can be related to this failure if it happens? Thanks for the hints, mind you though this is still a systemd-free f14 system in question here. I'll try to dig deeper when/if it happens again (I'll be building more stuff in mock today likely). (In reply to comment #2) > Thanks for the hints, mind you though this is still a systemd-free f14 system > in question here. Version changed to F14. I just experienced this exact bug with F16. ypbind is running then once I do the mock init, it's gone. and my system can't find my user until I restart ypbind (In reply to comment #4) > I just experienced this exact bug with F16. ypbind is running then once I do > the mock init, it's gone. and my system can't find my user until I restart > ypbind Anything suspicious in syslog? For example restarting some other services or some DNS-related stuff? Ping, has it happened again recently? If so, I'd really need more information, at least some suspicious syslog messages. |