cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! Site migration is underway. Phase 2: migrate recent content

Neo4jError Could not perform discovery. No routing servers available

In the backend, we have an application that using this Driver  https://www.npmjs.com/package/@zibix/neod  for link to a Neo4j database. It contains a portal via which we loaded data from the Nodejs application. When we reload the portal, the problem occurs. Error used to appear in the dashboard, resulting in a breakout in the portal, however after a few seconds (about 10sec), it returns to normal with response from neo4j. When you reloaded the portal multiple times, the Neo4jError would appear in neo4j logs (if you load/reload portal for 10 times, you will see the error at least 8 times).. I have attached a snippets as well as error logs from the application and neo4j to help you troubleshoot the issue.

Below log from Nodejs application:

 

 

"message":"neoderror: Neo4jError: Could not perform discovery. No routing servers available. Known routing table: RoutingTable[database=stageport, expirationTime=0, currentTime=1665999278179, routers=[], readers=[], writers=[]]Below log from neo4j debug log

 

 

Below logs from Neo4j application:

 

 

{"time":"2022-10-17 09:34:38.146+0000","level":"DEBUG","category":"o.n.b.v.m.BoltResponseMessageWriterV3","message":"Encoding a fatal failure message to send. Message: FAILURE AuthenticationRateLimit The client has provided incorrect authentication details too many times in a row."} 
{"time":"2022-10-17 09:34:38.147+0000","level":"WARN","category":"o.n.b.r.DefaultBoltConnection","message":"The client has provided incorrect authentication details too many times in a row."}

 

 

Screenshot from the portal:

jaybamaniya_1-1666075174080.png

 

 

0 REPLIES 0