IO Fencing messages from CoordPoint agent do not appear in agent log on 6.0.1 Cluster Server
Article ID: 100034118
Updated On:
Description
Error Message
n/aCause
Earlier releases such as 6.0.1 actually placed the debug in the Cluster Server (VCS) engine log.
Resolution
e.g.
Additional debug was enabled for the CoordPoint agent in VCS:
# haconf -makerw
# hatype -modify CoordPoint LogDbg DBG_1 DBG_10
# haconf -dump -makero
The messages appeared in the VCS engine log, e.g.
2017/06/01 04:50:49 VCS DBG_10 V-16-10061-602 (cemdb01) CoordPoint:coordpoint:monitor:Starting Level Two Monitoring
2017/06/01 04:50:49 VCS DBG_10 V-16-10061-601 (cemrt04) CoordPoint:coordpoint:monitor:Starting Level One Monitoring
2017/06/01 04:50:49 VCS DBG_10 V-16-10061-555 (cemrt04) CoordPoint:coordpoint:monitor:VxFEN module is running in SCSI3 or Sybase mode
Additional debug was enabled for the CoordPoint agent in VCS:
# haconf -makerw
# hatype -modify CoordPoint LogDbg DBG_1 DBG_10
# haconf -dump -makero
The messages appeared in the VCS engine log, e.g.
2017/06/01 04:50:49 VCS DBG_10 V-16-10061-602 (cemdb01) CoordPoint:coordpoint:monitor:Starting Level Two Monitoring
2017/06/01 04:50:49 VCS DBG_10 V-16-10061-601 (cemrt04) CoordPoint:coordpoint:monitor:Starting Level One Monitoring
2017/06/01 04:50:49 VCS DBG_10 V-16-10061-555 (cemrt04) CoordPoint:coordpoint:monitor:VxFEN module is running in SCSI3 or Sybase mode
Issue/Introduction
After switching on debug for the CoordPoint VCS agent, it was discovered that the debug didn't appear in the corresponding agent log.
Was this article helpful?
Yes
No
Powered by
