Showing results for 
Search instead for 
Do you mean 

my tru cluster trouble

Advisor

my tru cluster trouble

The use of asemgr command switch ase server
Reported the following error.
But the ase service switch sucessful.

Enter your choice: 1
Relocating service `in_service` to member `smp003`...
Start failed - Unable to start service.
Check syslog's daemon log to determine the error.
Unable to start service `in_service` on `smp003` - Relocation not successful.
Unable to relocate `in_service` to `smp003`.
5 REPLIES
Honored Contributor

Re: my tru cluster trouble

Hi,

I would start by checking the cluster interconnects between each node...

If that doesn't highlight any issues, then please share more of the hardware/software configuration with the rest of us.

Cheers,

Rob

Advisor

Re: my tru cluster trouble

hello rob
thank you very much
I use a ping command checked network, are normal, there is no packet loss.
My machine did not use MC card, use network card doing cluster, system version is 4.0F, ase service packs use LSM disk management, shared disk are used in BA356, you would also like to know what other information?
Valued Contributor

Re: my tru cluster trouble

You should check the usual Tru64 logs for events around the time of the attempted relocation. Specifically, in an ASE environment you may find some interresting messages in the daemon.log, or in one of the other syslog logs, but how much information is recorded there depends on what level of logging you have selected.
Nobody can serve both God and Money
Advisor

Re: my tru cluster trouble

Today, My machine automatically restart again, and I upload in the annex I can check the log
Honored Contributor

Re: my tru cluster trouble

- host name incorrect ??? or mistmatch of hostname between clusternodes.

- do these adresses and routers fall within the same or separate subnets ?
>>>
Jan 22 00:49:01 smp001 ASE: local HSM Notice: /var/ase/sbin/ase_run_sh: change host 132.229.34.136: gateway 132.229.34.136
Jan 22 00:49:01 smp001 ASE: local HSM Notice: /var/ase/sbin/ase_run_sh: change host 132.229.34.234: gateway 132.229.34.234
<<<

smp002 -> smp2
>>>
smp001
smp001:/var/adm/syslog.dated/current>vi daemon.log
"daemon.log" 375 lines, 37172 characters
Jan 22 00:49:00 smp001 ASE: local HSM Warning: Can't ping smp002_tu1 over the network
Jan 22 00:49:01 smp001 ASE: local HSM Warning: Can't ping smp002 over the network
Jan 22 00:49:01 smp001 ASE: local HSM Notice: /var/ase/sbin/ase_run_sh: change host 132.229.34.136: gateway 132.229.34.136
Jan 22 00:49:01 smp001 ASE: local HSM Notice: /var/ase/sbin/ase_run_sh: change host 132.229.34.234: gateway 132.229.34.234
Jan 22 00:49:01 smp001 ASE: local HSM ***ALERT: HSM_PATH_STATUS:132.229.34.136:DOWN:132.229.34.234:DOWN

.....
smp2
Jan 21 23:43:02 smp2 dnascd[551]: Process exit (PID 2002), status EX_TEMPFAIL
Jan 21 23:43:02 smp2 dnascd[551]: Process exit (PID 32444), status EX_TEMPFAIL
Jan 21 23:43:02 smp2 dnascd[551]: Process exit (PID 348), status EX_TEMPFAIL
Jan 22 00:43:12 smp2 dnascd[551]: Process exit (PID 8713), status E
<<<

//Add this to "OnDomLoad" event