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.

Upstream on port 3000 not listening

See original GitHub issue

Hi, I’ve been running Esplora for 2 weeks with Docker. Bitcoin Core sync’ed quickly since I already had the data. Electrs then started working hard but has been using only around 1% of the CPU for several days.

I’m having a look at nginx logs in the container and I can see it’s trying to connect to the upstream but the connection is refused when I hit the server. Port 3000 is indeed not a listening port in the container, nor is it on the host.

2019/03/02 03:55:18 [error] 199#199: *224 connect() failed (111: Connection refused) while connecting to upstream, client: 139.28.218.30, server: , request: "GET /api/blocks/tip/height HTTP/1.1", upstream: "http://127.0.0.1:3000/blocks/tip/height", host: "esplora-mainnet:8080", referrer: "http://esplora-mainnet:8080/"

Around 750GB of disk space is used on a total of 1TB.

I haven’t changed anything to the configs, except adding -vvv to the supervisord config to know what was going on.

...
2019-03-01T21:42:12.850+00:00 - DEBUG - Starting pre-cache for scripthash 26/10692
2019-03-01T22:48:43.007+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable
2019-03-02T00:39:57.217+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable
2019-03-02T02:15:11.364+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable
2019-03-02T02:15:11.373+00:00 - DEBUG - Starting pre-cache for scripthash 31/10692
2019-03-02T03:25:11.233+00:00 - DEBUG - writing 1 rows to RocksDB { path: "/data/electrs_bitcoin_db/mainnet/mainnet/newindex/cache" }, flush=Enable

It looks fine, I don’t see errors anywhere. When is electrs going to listen to port 3000?

Thanks.

Issue Analytics

State:
Created 5 years ago
Comments:30

Top GitHub Comments

2reactions

Kexkeycommented, Mar 4, 2019

Ok, I restarted from scratch with a brand new beast VM (the most powerful one on lunanode) and it’s now all good! Here are some stats (mainnet) for the record:

Bitcoin Core syncing whole chain: 7 hours Electrs indexing: 9 hours RocksDB compaction: 1.5 hours Electrs pre-caching: 2 hours

Total cost to be up and running: around 10 CAD.

Now I’ll quickly copy the data on a reusable volume, destroy that monster VM and use data on a more reasonable VM. 😃

Thanks!

1reaction

shesekcommented, Oct 14, 2020

Nice! 😃

I’m closing this issue for now, @Kexkey @benwilliams please report back if you’re still having issues.

Top Results From Across the Web

Nginx does not listen to port 3000 - node.js - Stack Overflow

I have a Nuxt app and I try to config Nginx , when I use curl localhost:3000 I can see my website tag...

nginx as a reverse proxy on port 3000 fails - DigitalOcean

If I load up my_server_ip:3000, nothing happens, even though localhost:3000 shows Hello World, from the node tutorial.

Issue - Port 3000 is closed and not listening - Plesk Forum

I have an android and ios application that i pointed to listen to mydomain.com:3000 but it keeps failing to connect each time i...

error connection refused node js

1: 8080 Is your server running on Port 3000 or 8080?What Is the ERR_CONNECTION_REFUSED Error? How to Fix Fix ERR_CONNECTION_REFUSED – Video Tutorial...

Configuring the proxy server - AWS Elastic Beanstalk

PORT || 3000; var server = app.listen(port, ... The default NGINX configuration forwards traffic to an upstream server that's named nodejs at 127.0.0.1:8081 ......