Kubernetes: puma parent process being killed about passwordpusher HOT 5 CLOSED

Thank you. the problem was with the memory.

from passwordpusher.

Hello @amirnazarizadeh, thanks for contributing to the Password Pusher community! We will respond as soon as possible.

from passwordpusher.

Hi @amirnazarizadeh,

When the application boots, puma launches a master process and then child processes to handle the HTTP requests.

Something is killing that parent process but it's not clear what... Could you check the container for any other logs? Inside the container there is also a logs directory that may have some evidence.

Could you also set these environment variables? We can lower that other one to debug if needed too.

from passwordpusher.

thank you for fast response.
I enabeld debug logs and got:
D, [2023-08-08T12:43:00.738297 #14] DEBUG -- : source=rack-timeout id=70786ecc-087b-491c-8509-02c863dddf56 timeout=15000ms state=ready D, [2023-08-08T12:43:00.743355 #14] DEBUG -- : source=rack-timeout id=70786ecc-087b-491c-8509-02c863dddf56 timeout=15000ms service=5ms state=active containers/docker/pwpush-ephemeral/entrypoint.sh: line 16: 9 Killed bundle exec puma -C config/puma.rb -e private

from passwordpusher.

One thing to eliminate might be feeding it more resources. Could it have been OOM killed?

pwpush.com is running with 1GB and 79% utilisation currently but that is a high traffic site too...

from passwordpusher.