EADDRINUSE due to hard coded prometheus port conflict with blockchain api
Closed this issue · 2 comments
{"level":"info","time":"2024-07-20T20:37:02.642Z","pid":94902,"hostname":"nixos","name":"api","msg":"Initializing API service..."}
{"level":"error","time":"2024-07-20T20:37:02.810Z","pid":94902,"hostname":"nixos","name":"api","err":{"type":"Error","message":"listen EADDRINUSE: address already in use 0.0.0.0:9153","stack":"Error: listen EADDRINUSE: address already in use 0.0.0.0:9153\n at Server.setupListenHandle [as _listen2] (node:net:1897:16)\n at listenInCluster (node:net:1945:12)\n at doListen (node:net:2109:7)\n at process.processTicksAndRejections (node:internal/process/task_queues:83:21)","code":"EADDRINUSE","errno":-98,"syscall":"listen","address":"0.0.0.0","port":9153},"msg":"App failed to start"}
Token metadata API and blockchain API are hard coded to use the same port 9153 for prometheus, so they cannot run on the same host.
token-metadata-api/src/index.ts
Line 108 in 0fafe1c
🎉 This issue has been resolved in version 1.0.0-beta.1 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀
🎉 This issue has been resolved in version 1.0.0 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀