HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: "Could not set secret key for ..." message
Operating System - HP-UX
1836458
Members
2669
Online
110101
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2002 12:54 AM
07-01-2002 12:54 AM
"Could not set secret key for ..." message
HP server is configured as a NIS+ client. The server for the NIS+ domain is a Sun machine. Every two or three days, when logging into the HP, get the message "Could not set secret key for unix.824@devenv1.bt.co.uk. The key server may be down." The login then hangs, after running the .profile. Typing Control C twice then allows the login to complete. Rebooting the HP clears the problem until the next time.
Any ideas?
Any ideas?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2002 01:02 AM
07-01-2002 01:02 AM
Re: "Could not set secret key for ..." message
Norman
A couple of things to look at
Where are you resolving ? locally on the client or on the NIS machine ?
entry in /etc/nsswitch.conf will tell you
hosts: files [NOTFOUND=continue] nis
On your client, what is you variable MAX_NISCHECKS set to in /etc/rc.config.d/namesvrs file ?
Steve
A couple of things to look at
Where are you resolving ? locally on the client or on the NIS machine ?
entry in /etc/nsswitch.conf will tell you
hosts: files [NOTFOUND=continue] nis
On your client, what is you variable MAX_NISCHECKS set to in /etc/rc.config.d/namesvrs file ?
Steve
take your time and think things through
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2002 01:11 AM
07-01-2002 01:11 AM
Re: "Could not set secret key for ..." message
in nsswitch.conf:
hosts: files dns nisplus [NOTFOUND=return]
MAX_NISCHECKS is set to 2
hosts: files dns nisplus [NOTFOUND=return]
MAX_NISCHECKS is set to 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2002 04:42 AM
07-02-2002 04:42 AM
Re: "Could not set secret key for ..." message
Norman,
The obvious question that I had is, "Is keyserv running at the time of the failure"? If not, did you try restarting it?
If it is running, then you've probably encountered a more detailed NIS+ problem that might require more extensive debugging. ITRC document NETUXKBRC00006829 helps you to understand if the user does get properly authenticated. Beyond that, a network packet trace might
be helpful. Use snoop on the Sun server and/or nettl + netfmt on the HPUX system.
Regards,
-> Brian Hackley
The obvious question that I had is, "Is keyserv running at the time of the failure"? If not, did you try restarting it?
If it is running, then you've probably encountered a more detailed NIS+ problem that might require more extensive debugging. ITRC document NETUXKBRC00006829 helps you to understand if the user does get properly authenticated. Beyond that, a network packet trace might
be helpful. Use snoop on the Sun server and/or nettl + netfmt on the HPUX system.
Regards,
-> Brian Hackley
Ask me about telecommuting!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP