咨询个问题，上一个操作在备份数据库，下一个操作在alert.log中就启动实例了，有什么其他地方可以查看嘛？

我来答

2021-08-18

10M

咨询个问题，上一个操作在备份数据库，下一个操作在alert.log中就启动实例了，有什么其他地方可以查看嘛？
微信图片_20210818165938.jpg
11:54 有VKTM警告
12:00 启动expdp
12:11 实例自启动了
期间主机没有重启，如果节点时间同步出现问题，应该11:54就应该出现问题，不应该12:11出现，这个还有其他日志可以查询嘛？

我来答

添加附件

问题补充

9条回答

默认

最新

不是小熊

升级问题到: 紧急故障

有用 0

打赏 0

茂材

看下crs日志有什么异常，是不是有驱逐节点动作

有用 0

打赏 0

Uncopyrightable

2021-08-18

检测了CRS相关日志，发现clssscExit: CSSD aborting from thread clssnmvKillBlockThread_0错误信息，在ocssd.trc还没有检测到具体错误信息

Uncopyrightable

上传附件：grid-alert.log

有用 0

打赏 0

Uncopyrightable

上传附件：ocssd.trc.zip

有用 0

打赏 0

Uncopyrightable

从目前日志上看是，两个节点连接不通，然后把其中一个节点踢出，
2021-08-18 12:06:41.248 : CSSD:3963295488: clssnmRemoveNodeInTerm: node 1, node1 terminated. Removing from its own member and connected bitmaps
2021-08-18 12:06:41.248 : CSSD:3963295488: ###################################
2021-08-18 12:06:41.248 : CSSD:3963295488: clssscExit: CSSD aborting from thread clssnmvKillBlockThread_0
2021-08-18 12:06:41.248 : CSSD:3963295488: ###################################
2021-08-18 12:06:41.248 : CSSD:3963295488: (:CSSSC00012:)clssscExit: A fatal error occurred and the CSS daemon is terminating abnormally

然后可能出现BUG？导致集群重启了？
Trace file /u01/app/grid/diag/crs/node1/crs/trace/ocssd.trc
Oracle Database 12c Clusterware Release 12.2.0.1.0 - Production Copyright 1996, 2016 Oracle. All rights reserved.
default:297500736: 1: clskec:has:CLSU:910 4 args[CLSD00302][mod=clsdadr.c][loc=(:CLSD00302:)][msg=clsdAdrInit: Trace file size and number of segments fetched from environemnt variable: ORA_DAEMON_TRACE_FILE_OPTIONS filesize=52428800,numsegments=10]

有用 0

打赏 0

Uncopyrightable

从版本11.2.0.2 开始，oracle新特性rebootless restart被介绍。当出现以下情况的时候，集群件（GI）会重新启动集群管理软件，而不是将节点重启:
1.当某个节点连续丢失网络心跳超过misscount时。
2.当某个节点不能访问大多数表决盘（VF）时。
3.当member kill 被升级成为node kill的时候。在之前的版本，以上情况，集群管理软件（CRS）会直接重启节点。
在GI 在重启集群之前，首先要对集群进行graceful shutdown, 基本的步骤如下：
1．停止本地节点的所有心跳（网络心跳，磁盘心跳和本地心跳）。
2．通知cssd agent，ocssd.bin即将停止
3．停止所有注册到css的具有i/o能力的进程，例如 lmon。
4．cssd通知crsd 停止所有资源，如果crsd不能成功的停止所有的资源，节点重启仍然会发生。
5．Cssd等待所有的具有i/o能力的进程退出，如果这些进程在short i/o timeout时间内不能不能全部推迟，节点重启仍然会发生。
6．通知cssd agent 所有的有i/o能力的进程全部退出。
7．Ohasd 重新启动集群。
8．本地节点通知其他节点进行集群重配置。
本次案例节点重启原因即为： RAC节点间网络心跳异常后集群驱逐了节点2，此时会符合rebootless restart特性，此时应该发生GI集群软件重启而不是主机重启；在GI集群软件重启前，在对集群进行正常关闭时(类似crsctl stop crs/has命令)，关闭时在进行到步骤:cssd通知crsd 停止所有资源时，CRSD终止资源时出现异常 [CSSD][72455936]clssscExit: CRSD cleanup failed with 184)；因此发生了节点重启。

2021-08-18 12:06:41.248 : CSSD:3963295488: clssnmRemoveNodeInTerm: node 1, node1 terminated. Removing from its own member and connected bitmaps
2021-08-18 12:06:41.248 : CSSD:3963295488: ###################################
2021-08-18 12:06:41.248 : CSSD:3963295488: clssscExit: CSSD aborting from thread clssnmvKillBlockThread_0
2021-08-18 12:06:41.248 : CSSD:3963295488: ###################################
2021-08-18 12:06:41.248 : CSSD:3963295488: (:CSSSC00012:)clssscExit: A fatal error occurred and the CSS daemon is terminating abnormally

2021-08-18 12:06:43.184 : CSSD:3963295488: ### Begin diagnostic data for the NM layer ###
2021-08-18 12:06:43.184 : CSSD:3963295488: Local node node1, number 1, state is clssnmNodeStateMEMBER
2021-08-18 12:06:43.184 : CSSD:3963295488: Status for node node1, number 1, uniqueness 1628892484, node ID 522785939
2021-08-18 12:06:43.184 : CSSD:3963295488: State clssnmNodeStateMEMBER, Connect: started 1 completed 1 OK
2021-08-18 12:06:43.184 : CSSD:3963295488: Status for node node2, number 2, uniqueness 1628645418, node ID 522785937
2021-08-18 12:06:43.184 : CSSD:3963295488: State clssnmNodeStateMEMBER, Connect: started 0 completed 0 !Error!
2021-08-18 12:06:43.184 : CSSD:3963295488: #### End diagnostic data for the NM layer ####
2021-08-18 12:06:43.184 : CSSD:3963295488: ######## End Diagnostic Dump ########
2021-08-18 12:06:43.184 : CSSD:3963295488: clssscExit: closing monitor listening endpoint

Trace file /u01/app/grid/diag/crs/node1/crs/trace/ocssd.trc
Oracle Database 12c Clusterware Release 12.2.0.1.0 - Production Copyright 1996, 2016 Oracle. All rights reserved.
default:297500736: 1: clskec:has:CLSU:910 4 args[CLSD00302][mod=clsdadr.c][loc=(:CLSD00302:)][msg=clsdAdrInit: Trace file size and number of segments fetched from environemnt variable: ORA_DAEMON_TRACE_FILE_OPTIONS filesize=52428800,numsegments=10]

CLSB:297500736: Argument count (argc) for this daemon is 3
CLSB:297500736: Argument 0 is: /u01/app/12c/grid/bin/ocssd.bin
CLSB:297500736: Argument 1 is: 
CLSB:297500736: Argument 2 is: OSD2PORTIF
复制

2021-08-18 12:10:20.631 : CSSD:297500736: (TLM) Starting CSS daemon, version 12.2.0.1.0 with uniqueness value 1629259820

有用 1

打赏 0

Uncopyrightable

从ossd.trc上看日志主要是网络方面的原因？这个信息不太懂，有哪位大神可以帮忙解释下嘛？

2021-08-18 12:06:39.027 :GIPCHAUP:3968550656: gipchaUpperProcessDisconnect: processing DISCONNECT for hendp 0x7f7664035dd0 [0000000000000489] { gipchaEndpoint : port ‘609f-a6f5-28d4-cf69’, peer ‘node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, srcCid 00000000-00000489, dstCid 00000000-012e4e71, numSend 0, maxSend 100, groupListType 1, hagroup 0x123ff00, priority 0, forceAckCount 0, usrFlags 0x4000, flags 0x204 }
2021-08-18 12:06:39.027 :GIPCGMOD:3968550656: gipcmodGipcCallbackDisconnect: [gipc] Disconnect forced for endp 0x7f76640337d0 [0000000000000477] { gipcEndpoint : localAddr ‘gipcha://node1:609f-a6f5-28d4-cf69’, remoteAddr ‘gipcha://node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, numPend 1, numReady 1, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef 0x125f990, ready 1, wobj 0x7f7664035d60, sendp (nil) status 0flags 0x20038606, flags-2 0x0, usrFlags 0x0 }
2021-08-18 12:06:39.027 :GIPCGMOD:2801772288: gipcmodGipcDisconnect: [gipc] Issued endpoint close for endp 0x7f76640337d0 [0000000000000477] { gipcEndpoint : localAddr ‘gipcha://node1:609f-a6f5-28d4-cf69’, remoteAddr ‘gipcha://node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, numPend 1, numReady 0, numDone 1, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef 0x125f990, ready 1, wobj 0x7f7664035d60, sendp (nil) status 0flags 0x20038606, flags-2 0x0, usrFlags 0x0 }
2021-08-18 12:06:39.028 :GIPCGMOD:3968550656: gipcmodGipcCallbackEndpClosed: [gipc] Endpoint close for endp 0x7f76640337d0 [0000000000000477] { gipcEndpoint : localAddr ‘gipcha://node1:609f-a6f5-28d4-cf69’, remoteAddr ‘gipcha://node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, numPend 0, numReady 1, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef 0x125f990, ready 0, wobj 0x7f7664035d60, sendp (nil) status 0flags 0x2003860e, flags-2 0x0, usrFlags 0x0 }
2021-08-18 12:06:39.028 :GIPCHDEM:3966973696: gipchaDaemonProcessClientReq: processing req 0x7f7688064430 type gipchaClientReqTypeDeleteName (12)
2021-08-18 12:06:39.028 : CSSD:2801772288: clssnmeventhndlr: Disconnecting endp 0x477 ninf 0x1261a50
2021-08-18 12:06:39.028 : CSSD:2801772288: clssnmDiscHelper: node2, node(2) connection failed, endp (0x477), probe((nil)), ninf->endp 0x7f7600000477
2021-08-18 12:06:39.028 : CSSD:2801772288: clssnmDiscHelper: node 2 clean up, endp (0x477), init state 3, cur state 3
2021-08-18 12:06:39.028 :GIPCXCPT:2801772288: gipcInternalDissociate: obj 0x7f76640337d0 [0000000000000477] { gipcEndpoint : localAddr ‘gipcha://node1:609f-a6f5-28d4-cf69’, remoteAddr ‘gipcha://node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, numPend 0, numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef (nil), ready 1, wobj 0x7f7664035d60, sendp (nil) status 0flags 0x2003860e, flags-2 0x0, usrFlags 0x0 } not associated with any container, ret gipcretFail (1)
2021-08-18 12:06:39.028 :GIPCXCPT:2801772288: gipcDissociateF [clssnmDiscHelper : clssnm.c : 3900]: EXCEPTION[ ret gipcretFail (1) ] failed to dissociate obj 0x7f76640337d0 [0000000000000477] { gipcEndpoint : localAddr ‘gipcha://node1:609f-a6f5-28d4-cf69’, remoteAddr ‘gipcha://node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, numPend 0, numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef (nil), ready 1, wobj 0x7f7664035d60, sendp (nil) status 0flags 0x2003860e, flags-2 0x0, usrFlags 0x0 }, flags 0x0
2021-08-18 12:06:39.028 :GIPCXCPT:2801772288: gipcInternalDissociate: obj 0x7f76640337d0 [0000000000000477] { gipcEndpoint : localAddr ‘gipcha://node1:609f-a6f5-28d4-cf69’, remoteAddr ‘gipcha://node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, numPend 0, numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef (nil), ready 1, wobj 0x7f7664035d60, sendp (nil) status 0flags 0x2003860e, flags-2 0x0, usrFlags 0x0 } not associated with any container, ret gipcretFail (1)
2021-08-18 12:06:39.028 :GIPCXCPT:2801772288: gipcDissociateF [clssnmDiscHelper : clssnm.c : 4054]: EXCEPTION[ ret gipcretFail (1) ] failed to dissociate obj 0x7f76640337d0 [0000000000000477] { gipcEndpoint : localAddr ‘gipcha://node1:609f-a6f5-28d4-cf69’, remoteAddr ‘gipcha://node2:nm2_node-cluster/ac85-5111-87f3-8f1b’, numPend 0, numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef (nil), ready 1, wobj 0x7f7664035d60, sendp (nil) status 0flags 0x2003860e, flags-2 0x0, usrFlags 0x0 }, flags 0x0
2021-08-18 12:06:39.028 : CSSD:2801772288: clssscSelect: gipcwait returned with status gipcretPosted (17)
2021-08-18 12:06:39.028 : CSSD:2801772288: clssnmDiscEndp: gipcDestroy 0x477
2021-08-18 12:06:39.028 : CSSD:2801772288: clssscSelect: gipcwait returned with status gipcretPosted (17)

有用 0

打赏 0

Uncopyrightable

从错误上看是心跳网络超过30秒没有连接，导致节点异常，触发rebootless restart机制

2021-08-18 12:06:41.229 : 2021-08-18 12:06:41.229 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : 2021-08-18 12:06:41.248 : CSSD:3973293824: clssgmFenceComplete: Death fence, operation(0x7f76982ea0d0), completed(0/1),
CSSD:3973293824: clssgmFenceComplete: Death fence, operation(0x7f76981f8530), completed(0/1),
CSSD:3963295488: (:CSSNM00005:)clssnmvDiskKillCheck: Aborting, evicted by node node2, number 2, sync 522785940, stamp 613792634
CSSD:3963295488: clssnmCheckForNetworkFailure: Entered
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 0 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: expiring 0 evicted 1 evicting node 2 this node 1
CSSD:3963295488: clssnmCheckForNetworkFailure: expiring 0 evicted 1 evicting node 2 this node 2
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 3 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 4 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 5 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 6 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 7 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 8 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 9 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 10 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 11 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 12 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 13 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 14 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 15 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 16 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 17 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 18 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 19 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 20 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 21 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 22 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 23 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 24 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 25 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 26 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 27 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 28 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 29 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 30 defined 0
CSSD:3963295488: clssnmCheckForNetworkFailure: skipping 31 defined 0
CSSD:3963295488: clssnmRemoveNodeInTerm: node 1, node1 terminated. Removing from its own member and connected bitmaps
CSSD:3963295488: ###################################
CSSD:3963295488: clssscExit: CSSD aborting from thread clssnmvKillBlockThread_0
CSSD:3963295488: ###################################
CSSD:3963295488: (:CSSSC00012:)clssscExit: A fatal error occurred and the CSS daemon is terminating abnormally

有用 0

打赏 0

Uncopyrightable

根据时间推断，是集群的数据资源出现提交hang住了，导致节点间通讯不顺畅等大量等待请求，最后心跳网络超过30秒无响应触发rebootless restart机制

2021-08-18 12:06:08.514 : CSSD:3988805376: clssgmpHandleFenceReq: Received fence request from node node2, number 2, for clientID 1:64:1, request does not kill primary
2021-08-18 12:06:08.515 : CSSD:3988805376: clssgmpcSendLocalFenceReq: Sending a fence rquest to node node1, number 1, for clientID 1:64:1
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmfInitLocalFence: Member level fence for global groupmemberID 167:2:0:4, fence type 1
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmfInitLocalFence: Fencing member (0x7f769005b250) with memberID 167:2:0 at the request of clientID 2:42:1
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmFenceMember: global grock(DB+ASM), member(0), type(1), cookie(0x7f76ecbab3f8)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmFenceObj: fencing member (0x7f769005b250) memberID 167:2:0 grock DB+ASM fence type 1
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcFenceDeath: Fencing target(0x7f769005b250), type(3)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceMembership: member(0x7f769005b250), memberID 167:2:0
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceClient: Client clientID 1:64:1 with pid(22942), proc(0x7f76982b0010), client(0x7f76982b5e40)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssscpidentry_construct: entry(0x7f7690099c00) initialized(1), context(0x7f769005b250), name(0x7f7690099c20/22942), pid(0x7f769005b810)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceMembership: Scheduled primary pid(22942), entry(0x7f7690099c00)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceClient: Client clientID 1:66:1 with pid(23093), proc(0x7f76982e9d50), client(0x7f76982df230)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssscpidentry_construct: entry(0x7f7690120190) initialized(1), context(0x7f76982ed2e0), name(0x7f76901201b0/23093), pid(0x7f769011eb70)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceMembership: Scheduled shared pid(23093), entry(0x7f7690120190)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceClient: Client clientID 1:71:2 with pid(22956), proc(0x7f769834a1a0), client(0x7f7698349bb0)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssscpidentry_construct: entry(0x7f7690120210) initialized(1), context(0x7f769834d840), name(0x7f7690120230/22956), pid(0x7f769011eb90)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceMembership: Scheduled shared pid(22956), entry(0x7f7690120210)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceClient: Client clientID 1:77:2 with pid(23153), proc(0x7f76983866b0), client(0x7f7698377fa0)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssscpidentry_construct: entry(0x7f76901206b0) initialized(1), context(0x7f769838cdb0), name(0x7f76901206d0/23153), pid(0x7f769011db10)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceMembership: Scheduled shared pid(23153), entry(0x7f76901206b0)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceClient: Client clientID 1:67:5 with pid(22954), proc(0x7f7698308df0), client(0x7f76983b5a70)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssscpidentry_construct: entry(0x7f769011eea0) initialized(1), context(0x7f76983b60d0), name(0x7f769011eec0/22954), pid(0x7f769011e850)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceMembership: Scheduled shared pid(22954), entry(0x7f769011eea0)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmQueueFenceForCheck: (0x7f769011de80) Death check for object type 3, pid NULL
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmFenceMember: global grock(DG_DATA), member(0), type(1), cookie((nil))
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmFenceObj: fencing member (0x7f7690076e70) memberID 17:2:0 grock DG_DATA fence type 1
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcFenceDeath: Fencing target(0x7f7690076e70), type(3)
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceMembership: member(0x7f7690076e70), memberID 17:2:0
2021-08-18 12:06:08.515 : CSSD:3971716864: clssgmProcessFenceClient: Client clientID 1:68:3 with pid(22971), proc(0x7f7698325200), client(0x7f76983190f0)
2021-08-18 12:06:08.515 : CSSD:3973293824: clssgmPrintFenceStatus: DEATH fencing for Share 0x7f769838cdb0 type 1 clientID 1:77:2 Pid 23153 Not Completed
2021-08-18 12:06:08.515 : CSSD:3973293824: clssgmFenceComplete: Death fence, operation(0x7f769011de80), completed(0/5),

有用 1

打赏 0

回答交流

Markdown

请输入正文

导入word

提交