Kbase P89173: AppServer not starting when defined for a NIS+ user
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1D
Solaris SPARC 2.8 64-bit
SYMPTOM(s):
AppServer not starting when defined for a NIS+ user
Adminserver started as root
Within ubroker.properties, userName, uuid and groupName are defined for the AppServer Broker
PID missing in second message of admserv.log file, after error 8171
[<date> <time>] [3] [AdminServer] SvcControlCmd.connectToService() failure: Unable to connect to the service process at rmi://<host>:<port>/<AppServer>(after 2 retries) (8171)
[<date> <time>] [3] [AdminServer] Started broker. Broker: <AppServer>, PID:
no entry in <AppServer>.broker.log
NIS+ user fails to authenticate with the AdminServer using Progress Explorer.
The command "nismatch <user> passwd.org_dir" returns
<user>:*NP*:<uuid>:<gid>::<home_dir>:<shell>:*NP*
The command "ypmatch <user> passwd" returns
Can't match key batch in map passwd.byname. Reason: can't communicate with ypbind.
CAUSE:
"*NP*" returned by "nismatch" stands for "No Permissions", which means that root doesn't have permissions to look at other user's encrypted password.
FIX:
Set up the NIS table in such a way that root can read it.
There are a couple of links on the Internet that explains how to do this, for example:
http:/
ewfdawg.com/SecBook-5.4.1.htm