[SERVER-53847] How to avoid this error "Failed to refresh session cache"? Created: 15/Jan/21  Updated: 18/May/22  Resolved: 16/Feb/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Key2SoftAgent Agent Assignee: Edwin Zhou
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Hello Dears,
During the replication work this error appears
How can I avoid this error ?
Notes : my database exceeded 3.5 TB , version 4.4, Server status is “Startup2”
Thanks a lot
{{

{"t":\{"$date":"2021-01-16T02:12:33.060+04:00"}

,"s":"I", "c":"CONTROL", "id":20714, "ctx":"LogicalSessionCacheRefresh","msg":"Failed to refresh session cache, will try again at the next refresh interval","attr":{"error":"NamespaceNotFound: config.system.sessions does not exist"}}}}



 Comments   
Comment by Edwin Zhou [ 16/Feb/21 ]

Hi key2softagent@gmail.com,

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Best,
Edwin

Comment by Edwin Zhou [ 08/Feb/21 ]

Hi key2softagent@gmail.com,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please archive (tar or zip) the mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) and attach it to this ticket?
Thanks,
Edwin

Comment by Edwin Zhou [ 19/Jan/21 ]

Hi key2softagent@gmail.com,

Would you please archive (tar or zip) the mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) and attach it to this ticket?

Kind regards,
Edwin

Generated at Thu Feb 08 05:32:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.