Unsolved
This post is more than 5 years old
11 Posts
0
937
July 1st, 2009 15:00
Agent fails to start
Hello all, have a server that the data drive that EMC is installed on ran out of hard drive space.
On server1.
Cleared up space on the drive and rebooted, restarted EMC AutoStart and the services node fails to start. All other EMC services start.
Getting a Raima Database Error -7 in the windows server event viewer.
On Server2
Was able to get the standby node up and running, services started, software and mirror seems to be intact. Query data store and shows broken/cracked, which is common.
Has anyone seen the above error messages?
Is there a way to force the agent to start?
Options.
Thanks
David
On server1.
Cleared up space on the drive and rebooted, restarted EMC AutoStart and the services node fails to start. All other EMC services start.
Getting a Raima Database Error -7 in the windows server event viewer.
On Server2
Was able to get the standby node up and running, services started, software and mirror seems to be intact. Query data store and shows broken/cracked, which is common.
Has anyone seen the above error messages?
Is there a way to force the agent to start?
Options.
Thanks
David
No Events found!
david.fontenot
11 Posts
0
July 1st, 2009 15:00
If this helps.
Trace Buffer Dump: Wed Jul 01 13:17:28 2009
< 0x3bc0c0 trace_SetDest
< 0x3bc0c0 trace_ReadConfig
< 0x3bc0c0 adm_Init ret: 0
INFO: 0x3bc0c0 (07/01/09 13:17:26) ID00000141 I am a Primary Agent
0x3bc0c0 nm_getNTProps
0x3bc0c0 nm_getWinVer
< 0x3bc0c0 nm_getWinVer
0x3bc0c0 ipm_getNicInterfaces_api
EVENT: 0x3bc0c0 (07/01/09 13:17:26) ID00001186 NM: INTERFACE=00-0e-0c-x-x-x IP=192.168.200.1 NETMASK=255.255.255.0 REALNAME=EMC Autostart Control
EVENT: 0x3bc0c0 (07/01/09 13:17:26) ID00001186 NM: INTERFACE=00-11-85-x-x-x IP=192.168.100.1 NETMASK=255.255.255.0 REALNAME=EMC Autostart Mirror
EVENT: 0x3bc0c0 (07/01/09 13:17:26) ID00001186 NM: INTERFACE=00-14-38-x-x-x IP=x.x.x.x NETMASK=255.255.255.0 REALNAME=Local Area Connection 4
< 0x3bc0c0 ipm_getNicInterfaces_api ret: 0
< 0x3bc0c0 ipm_getNicInterfaces ret: 0
< 0x3bc0c0 nm_getNTProps ret: 0
< 0x3bc0c0 nm_CacheNodeProps ret: 0
EVENT: 0x3bc0c0 (07/01/09 13:17:27) ID00000823 About to open DB at 'D:\PROGRA~1\EMCAUT~1\server1\dbm_records51'
< 0x3bc0c0 dbm_raimaExceptionHandler
< 0x3bc0c0 dbm_mapDbErr
FATAL: 0x3bc0c0 (07/01/09 13:17:27) ID00000952 Unknown Raima Database Error:-7
0x3bc0c0 dbm_Terminate
< 0x3bc0c0 dbm_Terminate ret: 0
< 0x3bc0c0 adm_dbTerminate ret: 0
yito1
262 Posts
0
July 1st, 2009 18:00
FTC_FT_DIR
FT_DBDIR
FT_DIR
FT_DOMAIN
FT_LNODE
And, please reinstall AutoStart of Server1.
It solved it by this method though I encountered the same phenomenon before, too.
ecervant
63 Posts
0
July 2nd, 2009 08:00
If all your nodes are generating the message, then a re-install of AutoStart is necessary to get a new database. Once the environment is re-installed, a backup.def can be re-imported to the environment to recreate the managed objects and resource groups.
If only one node is experiencing the symptom, the database may be recreated from a surviving node. The surviving node must also be a primary agent as secondary agents do not contain of copy of the AutoStart database. To recreate the database on one node:
- Stop the Agent and Backbone on the troubled node.
- Rename the database directory "FT_DIR\ _ ". For instance, "FT_DIR\ _ _old".
- Verify there is at least 1 primary agent running.
- Start the Agent and Backbone on the troubled node.
david.fontenot
11 Posts
0
July 2nd, 2009 10:00
I recommend 2 nodes both running as a primary agents, so in the event something like this happens I can always run on the secondary *standby* server even if the primary is completely gone....
I haven't tried the above steps yet, and will try when I get a chance.
Thanks again.
David