After Q3 Patching MongoDB Service stop

Hi Team,

Can you please elaborate below query.

We have patching on Linux servers Q3, during patching server rebooted and after patching completed server came online then MongoDB service not running automatically it was stop.

So can you please anybody provide what is causes of after patching was stop MongoDB service

we have found our server permission denied on .pem file after given permission MongoDB service running and also some servers manually start service

  1. why permission was denied on .pem file how to fix issue in future.
  2. Why Q3 patching is impact on MongoDB service.

What flavor/release of Linux?
Were all MongoDB Production Notes followed initially?
What are the errors in the mongod.log file?

What flavor/release of Linux?

A) Redhat

Were all MongoDB Production Notes followed initially?

Yes

What are the errors in the mongod.log file?

 I NETWORK  [ReplicaSetMonitor-TaskExecutor-0] Marking host serversname.:27017 as failed :: caused by :: ShutdownInProgress: connection pool is in shutdown
 I NETWORK  [ReplicaSetMonitor-TaskExecutor-0] Cannot reach any nodes for set shard0_2. Please check network connectivity and the status of the set. This has happened for 1 checks in a row.
 W SHARDING [signalProcessingThread] cant reload ShardRegistry  :: caused by :: CallbackCanceled: Callback canceled
 I FTDC     [signalProcessingThread] Shutting down full-time diagnostic data capture
 I STORAGE  [WTOplogJournalThread] oplog journal thread loop shutting down
 I STORAGE  [signalProcessingThread] WiredTigerKVEngine shutting down
 I STORAGE  [signalProcessingThread] shutdown: removing fs lock...
 I CONTROL  [signalProcessingThread] now exiting
 I CONTROL  [signalProcessingThread] shutting down with code:0