- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- FAILED daemon at startup
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
Discussions
Forums
Discussions
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
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
07-16-2001 06:10 AM
07-16-2001 06:10 AM
At system startup I get two procedures that fail to complete (FAILED status)
1-tombstones
Copy processor logs to /var/tombstones
Output from "/sbin/rc1.d/S430pdcinfo start":
----------------------------
pdcinfo: pdc_system_info(return info) call failed, status = -2
pdcinfo: pdcinfo_main.c:911
ERROR: pdcinfo returned error status=255
"/sbin/rc1.d/S430pdcinfo start" FAILED
2-name server daemon
Copy processor logs to /var/tombstones
Output from "/sbin/rc1.d/S430pdcinfo start":
----------------------------
pdcinfo: pdc_system_info(return info) call failed, status = -2
pdcinfo: pdcinfo_main.c:911
ERROR: pdcinfo returned error status=255
"/sbin/rc1.d/S430pdcinfo start" FAILED
What can I do to correct these problems? Are they related?
I'm new so any help will get points and is much appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2001 06:29 AM
07-16-2001 06:29 AM
Re: FAILED daemon at startup
This is not supported on the system you have, and you should disable it by editing /etc/rc.config.d/pdcinfo and turning the variable from PDCINFO=1 to PDCINFO=0
and at the next reboot you should not get this error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2001 06:42 AM
07-16-2001 06:42 AM
Re: FAILED daemon at startup
'pdcinfo' is part of the Online Diagnostics software. I'm not sure that it runs on other than series-800 machines.
You can disable it by changing PDCINFO=1 to PDCINFO=0 in /etc/rc.config.d/pdcinfo.
For the failure in sbin/rc2.d/S370named, check /var/adm/syslog/syslog.log as the failure suggests.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2001 06:54 AM
07-16-2001 06:54 AM
Re: FAILED daemon at startup
Start name server daemon
Output from "/sbin/rc2.d/S370named start":
----------------------------
EXIT CODE: 1
Error in starting named. Recommend checking the
syslog file (usually /var/adm/syslog/syslog.log)
for possible reasons.
"/sbin/rc2.d/S370named start" FAILED
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2001 07:12 AM
07-16-2001 07:12 AM
SolutionFollow the recommendation of the message and look in /var/adm/syslog/syslog.log for pertinent failures.
You appear to have NAMED=1 in /etc/rc.config.d/namesvrs. This setting means that your server is operating as a DNS server. I suspect this is not what you intended. If not, change the variable setting to NAMED=0.
...JRF...