Video Screencast Help

Nessus scan causing VCS failover - known problem?

Created: 23 Feb 2011 • Updated: 23 Feb 2011 | 1 comment

 

 

I'm running a series of recently-mandated Nessus scans on some of our database VLANs.

VCS clusters are going into failover with message traffic below.

Obtaining version/install info from sysadmins now.

Anyone seen this sort of thing before?

sample log traffic below.

----------------------

2011/02/17 15:21:35 VCS WARNING V-16-1-10514 IpmHandle::open getpeername failed errno = 107
2011/02/17 15:22:57 VCS ERROR V-16-2-13067 (qcudubvcsrdb9a2) Agent is calling clean for resource(CU-cs_ntfr) because the resource became OFFLINE unexpectedly, on its own.

2011/02/17 15:22:58 VCS INFO V-16-2-13068 (qcudubvcsrdb9a2) Resource(CU-cs_ntfr) - clean completed successfully.
2011/02/17 15:22:58 VCS ERROR V-16-2-13073 (qcudubvcsrdb9a2) Resource(CU-cs_ntfr) became OFFLINE unexpectedly on its own. Agent is restarting (attempt number 1 of 3) the resource.
2011/02/17 15:22:58 VCS NOTICE V-16-2-13076 (qcudubvcsrdb9a2) Agent has successfully restarted resource(CU-cs_ntfr).
2011/02/17 15:30:19 VCS NOTICE V-16-1-10300 Initiating Offline of Resource CU-cs_ntfr (Owner: unknown, Group: ClusterService) on System qcudubvcsrdb9a2
2011/02/17 15:30:20 VCS INFO V-16-1-10305 Resource CU-cs_ntfr (Owner: unknown, Group: ClusterService) is offline on qcudubvcsrdb9a2 (VCS initiated)
2011/02/17 15:33:09 VCS NOTICE V-16-1-10233 Clearing Restart attribute for group ClusterService on all nodes
2011/02/17 15:33:09 VCS NOTICE V-16-1-10301 Initiating Online of Resource CU-cs_ntfr (Owner: unknown, Group: ClusterService) on System qcudubvcsrdb9a2
2011/02/17 15:33:10 VCS INFO V-16-1-10298 Resource CU-cs_ntfr (Owner: unknown, Group: ClusterService) is online on qcudubvcsrdb9a2 (VCS initiated)
2011/02/17 15:33:10 VCS NOTICE V-16-1-10447 Group ClusterService is online on system qcudubvcsrdb9a2
2011/02/21 16:27:23 VCS INFO V-16-1-50135 User root fired command: haconf -makerw from localhost
2011/02/21 16:27:28 VCS INFO V-16-1-50135 User root fired command: hagrp -unfreeze CDORA-oview3db  from localhost
2011/02/21 16:27:28 VCS INFO V-16-1-50135 User root fired command: hagrp -unfreeze CDORA-oview3db  from localhost
2011/02/21 16:27:28 VCS INFO V-16-1-50135 User root fired command: hagrp -unfreeze CDORA-oview4db  from localhost
2011/02/21 16:27:28 VCS INFO V-16-1-50135 User root fired command: hagrp -unfreeze CDORA-oview4db  from localhost
2011/02/21 16:27:28 VCS INFO V-16-1-50135 User root fired command: hagrp -unfreeze CDORA-qarmn11db  from localhost

Comments 1 CommentJump to latest comment

avsrini's picture

Hi,

The resource CU-cs_ntfr, looks to be a notifier resource in ClusterService SG, which listens on

port 14144 and 34581. Thus when Nessus scan was run, looks like its causing this notifier process to die.

Do you find any core file on / from notifier?

 

Suspect it may be due to bad connection on notifier port, but need more data to confirm.

 

Regards

Srini