CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).

最新推荐文章于 2025-05-14 13:36:34 发布

原创最新推荐文章于 2025-05-14 13:36:34 发布 · 9.3k 阅读

2 ·

CC 4.0 BY-SA版权

RAC 专栏收录该内容

4 篇文章

订阅专栏

本文分析了Oracle RAC环境中出现的OCR错误日志，解释了这些错误产生的原因及为何可以忽略它们，并提供了检查主节点的方法。

警告内容：

<message-time timezone="GMT">2015-12-05T03:17:58.209+00:00</message-time>
<product-name>EM ASR Product</product-name>
<event-timetimezone="Asia/Shanghai">2015-12-05T11:17:57.000+00:00</event-time>
<property name="IssueType">EVENT_METRIC_ALERT</property>
<property name="TargetType">Oracle High Availability Service</property>
<property name="TargetName">has_erp02</property>
<property name="TargetVersion">11.2.0.4.0</property>
<property name="HWArchitecture">GenuineIntel x86_64</property>
<property name="OS">Oracle Linux Server release 5.11</property>
<property name="IncidentCategories">Error</property>
<property name="IncidentSummary">[cssd(90423)]CRS-1601:CSSD Reconfiguration complete. Active nodes are erpdb01 erpdb02 . See /u01/PSPROD/11.2.0.4/grid/log/erpdb02/alerterpdb02.log for details.</property>
<property name="IncidentCreatedTime">2015-12-05T11:17:57.000+00:00</property>
<property name="EventName">CRSAlert:clusterwareErrStack</property>
<property name="EventClass">metric_alert</property>
<property name="EventExpression">has:metric_alert:CRSAlert:clusterwareErrStack</property>
<property name="eventMessage">[cssd(90423)]CRS-1601:CSSD Reconfiguration complete. Active nodes are erpdb01 erpdb02 . See /u01/PSPROD/11.2.0.4/grid/log/erpdb02/alerterpdb02.log for details.</property>

去查询相应的集群日志：

2015-12-12 10:37:11.369:

[/u01/PSPROD/11.2.0.4/grid/bin/orarootagent.bin(15547)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).

往前搜索发现6月份也有

2015-06-06 05:26:16.572:
[/u01/PSPROD/11.2.0.4/grid/bin/orarootagent.bin(90128)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).

2013-11-28 19:39:32.503:
[/u01/PSPROD/11.2.0.4/grid/bin/orarootagent.bin(8294)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).

2013-11-28 19:32:45.931:
[ohasd(5834)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).

2013-11-28 19:32:41.617:
[/u01/PSPROD/11.2.0.4/grid/bin/orarootagent.bin(8131)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).

2013-11-28 19:15:28.470:
[/u01/PSPROD/11.2.0.4/grid/bin/orarootagent.bin(8125)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).

解决：

这种错误一般是由数据库主动维护引起的，一般可以忽略

从RAC的原理上分析，集群中同一时刻，只有一个节点，也就是MASTER NODE能访问OCR资源，
其他节点读到的OCR信息都来自这个主节点的一份CACHE，集群重组后，由于OCR被另一个节点掌管，
该节点访问不了OCR，所以抛出这种错误OCR都是被MASTER NODE控制的，
用以下命令可以查看集群中的MSTER NODE：
[root@node1 cssd]# for x in `ls -tr /u01/11.2.0/ghome/log/node1/cssd/ocssd* `; do grep -i "master node" $x ; done | tail -1
2015-12-15 09:02:46.886: [CSSD][1112426816]clssgmCMReconfig: reconfiguration successful, incarnation 340380455 with 2 nodes, local node number 1, master node number 1
[root@node1 cssd]#
[root@node3 ~]# for x in `ls -tr /u01/11.2.0/ghome/log/node3/cssd/ocssd* `; do grep -i "master node" $x ; done | tail -1
2015-12-15 09:02:47.213: [ CSSD][1079871808]clssgmCMReconfig: reconfiguration successful, incarnation 340380455 with 2 nodes, local node number 2, master node number 1
[root@node3 ~]#
每一套RAC的OCR备份都有master node来进行，基于以上分析，这种日志错误可以忽略，
至于master node的决定管理权，按照官方的说法，当两个节点的投票数一样的情况下，是由集群中number数比较小的来掌管