- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- "named" daemon needs to be stop & start after rebo...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
04-23-2001 01:12 AM
04-23-2001 01:12 AM
Our server SERVER99 (a PRI DNS & NIS Server) needs to have its "named" daemon stops & starts again after each reboot (though a "ps -ef" shows that it is running fine). Failure to do so will result in clients having problem --- "ypwhich" returns hex code and "nslookup" error of "Cannot find server name for address:
Note :
- Problem occurs only after installation of QPK1100, Quality Pack for HP-UX 11.0, on 18-Apr-2001.
- any suggestions that require reboot will not receive any immed feedback as our next reboot is scheduled on 2-May-2001.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2001 01:47 AM
04-23-2001 01:47 AM
Re: "named" daemon needs to be stop & start after reboot
edit /etc/rc/config.d/namesrvs
and change "NAMED=0" to
NAMED=1
and check if you have following files:
/sbin/rc1.d/K630named
/sbin/init.d/named
/sbin/rc2.d/S370named
good luck,
Thierry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2001 02:47 AM
04-23-2001 02:47 AM
SolutionDid you check for Special installation instructions for each patch you were going to install?
I'm afraid you should do it before, but if you didn't, do it now and check if you find something relating named.
I've checked some patches and I found this insteresting patch:
PHNE_20619 may give some errors with name resolutin
install superseding patch PHNE_23274 (HP recommended - does not require reboot).
good luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2001 08:56 AM
04-23-2001 08:56 AM
Re: "named" daemon needs to be stop & start after reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2001 08:11 PM
04-23-2001 08:11 PM
Re: "named" daemon needs to be stop & start after reboot
1) have verified the problem exists by rebooting the server 3 times on 23-Apr-01, issuing commds "nslookup" & "ypwhich" on clients before stop/start "named" on Server.
2) the "named" daemon was running fine on Server after each reboot. BEFORE stop/start "named" to resolve Clients' problem, issued "ypwhich" & "nslookup" on Server itself. Works fine on Server but NOT on clients.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2001 08:16 PM
04-23-2001 08:16 PM
Re: "named" daemon needs to be stop & start after reboot
3) everything works fine on clients after stop/start "named" on server.