- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Starting Control Daemon Fail
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
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
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
02-18-2012 12:10 AM
02-18-2012 12:10 AM
Starting Control Daemon Fail
Hi,
i reinstall the HP-UX (DC-OE 11.31) on my server rx2660 and i see the big message output "OK"
but when the server booting it's stopped for more 20 minutes on " Starting Control Daemon" then i see the below error message
Starting Control Daemon .....................................FAIL *
* - An error has occurred !
* - Refer to the file /etc/rc.log for more information.
i rebooted more than 2 times but the same issue, please your support to resolve this issue. please find the rc.log on the attached file.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2012 12:41 AM
02-18-2012 12:41 AM
Re: Starting Control Daemon Fail
>please find the rc.log on the attached file.
I'm not sure what these mean:
Starting Control Daemon
Output from "/sbin/rc3.d/S99z0OVCtrl start":
(ctrl-12) Communication error when executing 'Start' method.
(xpl-117) Timeout occurred while waiting for data.
EXIT CODE: 64
You could look into sbin/rc3.d/S99z0OVCtrl to see what's being executed. Is there another machine it's trying to contact?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2012 01:33 AM
02-18-2012 01:33 AM
Re: Starting Control Daemon Fail
Hi,
please find the attached file.
>>>>>>>>>
Is there another machine it's trying to contact?
<<<<<<<<<
i think because before installing the OS was some filesystem shared to other machine but I stop that from the client system.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2012 01:51 AM
02-19-2012 01:51 AM
Re: Starting Control Daemon Fail
>I think because before installing the OS was some filesystem shared to other machine
That wouldn't show a hang on S99z0OVCtrl.
What does "/sbin/rc3.d/S99z0OVCtrl status" show?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2012 03:42 AM
02-20-2012 03:42 AM
Re: Starting Control Daemon Fail
Hi,
this is the output
#/sbin/rc3.d/S99z0OVCtrl status
agtrep OV Discovery Agent AGENT,AgtRep Stopped
coda OV Performance Core COREXT (2459) Running
opcacta OVO Action Agent AGENT,EA Stopped
opccfgfile OVO configfile Agent AGENT,EA Stopped
opceca OVO Event Correlation AGENT,EA Stopped
opcecaas ECS Annotate Server AGENT,EA Stopped
opcle OVO Logfile Encapsulator AGENT,EA Stopped
opcmona OVO Monitor Agent AGENT,EA Stopped
opcmsga OVO Message Agent AGENT,EA Stopped
opcmsgi OVO Message Interceptor AGENT,EA Stopped
opctrapi OVO SNMP Trap Interceptor AGENT,EA Stopped
ovbbccb OV Communication Broker CORE (2255) Running
ovcd OV Control CORE (2254) Running
ovconfd OV Config and Deploy COREXT (4067) Initializing
rtmd HP Real Time Measurement AGENT (2458) Running
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2012 04:11 AM
02-20-2012 04:11 AM
Re: Starting Control Daemon Fail
>this is the output
Ok, it didn't hang but lots of things are stopped.
Try: /sbin/rc3.d/S99z0OVCtrl start
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2012 06:00 AM
02-20-2012 06:00 AM
Re: Starting Control Daemon Fail
> this is the output
The "Control Daemon" is part of the HP OpenView Operations (= OVO for short) product family. Looks like this server has OVO monitoring agents installed.
Is this system supposed to be monitored via some OVO server? If yes, the OVO server should have been alerting you that the monitoring agent is not working on this host.
If you've moved to some other monitoring system, someone might have forgotten to uninstall the agents.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2012 08:25 PM
02-20-2012 08:25 PM
Re: Starting Control Daemon Fail
Hi,
But i reinstall the HP-UX (DC-OE 11.31) on my system and there is no any montring againt installed on this system.
and i facing this when i try to start this
/sbin/rc3.d/S99z0OVCtrl start
(ctrl-12) Communication error when executing 'Start' method.
(xpl-117) Timeout occurred while waiting for data.
EXIT CODE: 64
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2012 01:46 AM
02-21-2012 01:46 AM
Re: Starting Control Daemon Fail
The output of your "/sbin/rc3.d/S99z0OVCtrl status" command definitely looks like you have an OVO agent installed but maybe not properly configured.
The OVO Agent might have been embedded in the DataCenter OE, so that it installs by default unless you unselect it when starting the installation, as a way for HP to make it easier to use OVO for monitoring HP-UX systems.
As the OS installation procedure cannot know the configuration of your OVO server (if you have one), the agent would be trying to autoconfigure itself... but obviously failing if you don't have an OVO server.
If you don't use the OVO agent, you might want to disable it, so it won't cause useless error messages in your system startup. If I recall correctly, the OVO agent was controlled by /etc/rc.config.d/OpC or a similarly-named file. The should have a variable that is currently set to 1; change it to 0 to stop the agent from starting.
You might also want to swremove the agent if you don't have any use for it; if you do that, remember the name of the software item. Next time you reinstall HP-UX, make sure that item is not selected for installation unless you really want it.