Closed i5okie closed 3 years ago
Hi @i5okie, I do not have enough information to help. Maybe you are not exposing the port in your dockerfile? Dockerfile
EXPOSE 7433
Try running your image locally and curl to the port
docker run -p 7433:7433 IMAGE bin/bundle exec sidekiq
curl localhost:7433
OK, It looks like port is exposed. Can you check in the web interface if the sidekiq_alive queues are running/ added to the queue list?
Hi. I have the same problem than this ticket: I checked and queues are here, the jobs are regulary launched, the redis key is written.
I see a puma starting from sidekiq (with 4 workers, which seems a lot). Port 7433
is unreachable.
Hi, This seems a network configuration out of the scope of this library. If you want to provide examples of configurations or common network configuration errors and the solution as documentation in a PR I'm happy to merge it, otherwise not much to do here. Thanks
Hi,
I'm using : sidekiq (5.2.7) sidekiq_alive (2.0.1)
Deployment:
I have another deplyimg mirrors config above, except i'm specifying a different queue there.
it keeps failing the liveness or readiness probe every few minutes and reboots:
some are saying
Detected parent died, dying
others show nothing in logs that would indicate anything going wrong.