Bug 700160 - ypbind service doesn't start correctly
Summary: ypbind service doesn't start correctly
Keywords:
Status: CLOSED DUPLICATE of bug 696629
Alias: None
Product: Fedora
Classification: Fedora
Component: ypbind
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Honza Horak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-27 15:58 UTC by Chris Plummer
Modified: 2011-04-29 13:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-29 13:42:20 UTC
Type: ---


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 696629 0 unspecified CLOSED NIS logins unavailable immediately after boot (ypbind service started) 2021-02-22 00:41:40 UTC

Internal Links: 696629

Description Chris Plummer 2011-04-27 15:58:01 UTC
Description of problem:

I did a fresh install from DVD of the F15 beta - after the installation of all the packages, the system rebooted to the configuration wizard.  While creating a local user, I clicked on the button to set up an NIS client to do additional authentication.  However, whenever I try to run any kind of 'yp' command, like ypcat {map}, I get the message: "No such map {map}.  Reason: Can't bind to server which serves this domain".  However, if I issue a 'service ypbind restart' command as root, the service starts up fine and ypbind now connects to the server and ypcat {map} works again.  I've checked my /etc/yp.conf file and /etc/sysconfig/network file, which have the correct servers and domain set up - I searched the /var/log/messages for 'ypbind' and found entries that say 'ypbind NIS domain: mydomain.com, NIS server: ', then once I restart the service, there is another entry with the server name filled in that says 'ypbind NIS domain: mydomain.com, NIS server: nis-server.mydomain.com'.  This seems like a bug in the startup configuration for ypbind.

Version-Release number of selected component (if applicable):

ypbind-1.32-8.fc15.x86_64

How reproducible:

Every time I reboot the computer.

Steps to Reproduce:
1. Reboot the computer.
2. Run ypcat {map} on a known map name.
3. Returns an error about not binding to the NIS server correctly.
  
Actual results:

Error message when running 'yp' commands.

Expected results:

Commands should not complain about not binding to the server correctly.

Additional info:

Comment 1 Honza Horak 2011-04-28 11:18:14 UTC
It is probably related to bug #696629, could you provide some more info, please?
Do you use NetworkManager or network service?
What is the output of following commands?
rpm -q systemd
rpm -q dbus
rpm -q NetworkManager
cat /etc/sysconfig/ypbind

Comment 2 Chris Plummer 2011-04-28 15:57:32 UTC
(In reply to comment #1)
> It is probably related to bug #696629, could you provide some more info,
> please?
> Do you use NetworkManager or network service?
> What is the output of following commands?
> rpm -q systemd
> rpm -q dbus
> rpm -q NetworkManager
> cat /etc/sysconfig/ypbind

Thanks for the response - I think NetworkManager, but I'm not sure of the difference between it and network service (I guess I thought that NetworkManager did everything network configuration related).

$ rpm -q systemd
systemd-25-1.fc15.x86_64
$ rpm -q dbus
dbus-1.4.6-3.fc15.x86_64
]$ rpm -q NetworkManager
NetworkManager-0.8.998-3.git20110419.fc15.x86_64
$ cat /etc/sysconfig/ypbind
cat: /etc/sysconfig/ypbind: No such file or directory

Comment 3 Honza Horak 2011-04-29 13:42:20 UTC
I think this is the same as bug #696629, you can try the new update 
https://admin.fedoraproject.org/updates/ypbind-1.32-8.fc15.1

*** This bug has been marked as a duplicate of bug 696629 ***


Note You need to log in before you can comment on or make changes to this bug.