cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Urgent to fix the problem

Dear All,

I find the two node the cluster failed to start VCS servies and check the log message below.

Aug 15 12:27:21 devuaedms12 genunix: [ID 603404 kern.notice] NOTICE: core_log: pkginfo[4234] core dumped: /var/core/core.pkginfo.300.100.devuaedms12
Aug 15 12:29:39 devuaedms12 genunix: [ID 603404 kern.notice] NOTICE: core_log: pkginfo[4267] core dumped: /var/core/core.pkginfo.0.0.devuaedms12
Aug 15 12:29:39 devuaedms12 genunix: [ID 603404 kern.notice] NOTICE: core_log: pkginfo[4279] core dumped: /var/core/core.pkginfo.0.0.devuaedms12
Aug 15 12:30:23 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS NOTICE V-16-1-10619 'HAD' starting on: devuaedms12
Aug 15 12:30:23 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS NOTICE V-16-1-10620 Waiting for local cluster configuration status
Aug 15 12:30:23 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS NOTICE V-16-1-10625 Local cluster configuration valid
Aug 15 12:30:23 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS NOTICE V-16-1-11034 Registering for cluster membership
Aug 15 12:30:23 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS NOTICE V-16-1-11035 Waiting for cluster membership
Aug 15 12:30:27 devuaedms12 gab: [ID 316943 kern.notice] GAB INFO V-15-1-20036 Port h gen 6b8220 membership ;1
Aug 15 12:30:27 devuaedms12 gab: [ID 674723 kern.notice] GAB INFO V-15-1-20038 Port h gen 6b8220 k_jeopardy 0
Aug 15 12:30:27 devuaedms12 gab: [ID 513393 kern.notice] GAB INFO V-15-1-20040 Port h gen 6b8220 visible 0
Aug 15 12:30:27 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS INFO V-16-1-10077 Received new cluster membership
Aug 15 12:30:27 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS NOTICE V-16-1-10086 System devuaedms12 (Node '1') is in Regular Membership - Membership:
0x2
Aug 15 12:30:27 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS NOTICE V-16-1-10073 Building from local configuration
Aug 15 12:30:29 devuaedms12 vxfen: [ID 214757 kern.notice] NOTICE: VCS FEN INFO V-11-1-34 The ioctl VXFEN_IOC_CLUSTSTAT returned 0
Aug 15 12:30:29 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
Aug 15 12:30:30 devuaedms12 vxfen: [ID 214757 kern.notice] NOTICE: VCS FEN INFO V-11-1-34 The ioctl VXFEN_IOC_CLUSTSTAT returned 0
Aug 15 12:30:44 devuaedms12 last message repeated 14 times
Aug 15 12:30:44 devuaedms12 Had[4291]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
Aug 15 12:30:45 devuaedms12 vxfen: [ID 214757 kern.notice] NOTICE: VCS FEN INFO V-11-1-34 The ioctl VXFEN_IOC_CLUSTSTAT returned 0

I can see the vxfencoorddg in the vxdisk list , and failed to start up .  Can I see if there is any advice to fix this problem?

 

Thanks,

 

 

1 Reply
Highlighted

Re: Urgent to fix the problem

cluster failed to start? 

So you made some changes to the cluster, right?

Try the solutions in the technotes below first

https://www.veritas.com/support/en_US/article.100029763

https://www.veritas.com/support/en_US/article.100026825

https://www.veritas.com/support/en_US/article.100008337