Not sure if it's ypbind or mock, but...
Seems ypbind sometimes(1) stops functioning properly on my box after I init a buildroot using mock. The sometimes seems to be approximately 50% of the time, depending on weather, phase of the moon, and such.
0. start with happy functioning box
1. mock -r fedora-15-i386 init
2. sudo ls /
sudo: unknown uid: XXXX
3. su -c "/sbin/service ypbind restart"
4. sudo ls /
... proper output ...
Testing here using:
$ rpm -q ypbind mock
Of course, now that I'm filing this, it's worked ok 5 times in a row.
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
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.