Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Repository ping exceeded 30 seconds ([values > 30])
See original GitHub issueGetting warnings time to time as
warn: Explorer: Repository ping exceeded 30 seconds (100), please report the issue to NBXplorer developers
It looks like this doesn’t affect NBX instance but since it says ‘please report the issue’ it is better to have an issue for this.
Setup details; One NBX instance is running for btc/ltc/dash. RabbitMq publishing is active.
Issue Analytics
- State:
- Created 3 years ago
- Comments:22 (22 by maintainers)
Top Results From Across the Web
wrapper.ping.timeout Property
Number of seconds to allow between two ping responses coming from the JVM. The default value is "30 seconds". Example: wrapper.ping.timeout=30.
Read more >i/o timeout errors in redis and argocd-repo-server PODs
The plan was to ping kube api server IP (which is K8 master IP) to see if there is communication between two. argocd@argocd-application- ......
Read more >Fatal error: Maximum execution time of 30 seconds exceeded
I ran into this problem while upgrading to WordPress 4.0. By default WordPress limits the maximum execution time to 30 seconds. Add the ......
Read more >PingAccess - PingFederate
PingAccess will automatically make the changes effective within 30 seconds. Configure a class or package log level. You can use the log4j2.xml file...
Read more >Repositories tab (Agent policy pages)
Ping timeout (seconds) — Specifies the time the McAfee ePO server waits for the response from the repositories. Default value is 30 seconds....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@junderw @joemphilips btw by rewritting DBReeze, I found out the underlying reason of huge file handle opening.
It is because every single transaction I save in the DB, create one file… I will fix that as well.
I rewrote DBriize, I need additional testing and porting to NBXplorer.
I go down from 2 second to 200 ms for query of 4000 transactions on my machine. The next bottleneck will probably be CPU. RAM requirements probably going down as well. There is also a mode for big RAM machines, which can drop the query to 100 ms. But I think I will not activate it until somebody hit a problem.