Worker exiting - ERROR pid:15

Troubleshooting and help
,
1

[2025-01-27 21:01:37 +0000] [15] [INFO] Worker exiting (pid: 15)

01/27/2025, 10:01:37 PM [2025-01-27 21:01:37 +0000] [1] [INFO] Handling signal: term

01/27/2025, 10:01:37 PM [2025-01-27 21:01:37 +0000] [1] [ERROR] Worker (pid:15) was sent SIGTERM!

01/27/2025, 10:01:37 PM [2025-01-27 21:01:37 +0000] [1] [INFO] Shutting down: Master

Hello, sorry i’m quite new here, i used to run a python file without any problem.
I had the chance to add some features but now I get this error instead

Anyone faced the same issue?

Thank you!

2

Hi!

You need to add logging on the code you’ve added. Did you try to reproduce locally?

It is not possible to exactly know what happened with the current error.

3

In local it works fine, i dont understand when the problems are and i really need to fix it

Any other chance to know where the problem can be?
What is it linked to?

4

Hi @Maurizio,

We need more details to be able to help. What change caused the failure?
Could you share the code ot this worker?

5

Hello, unfortunatly it’s happening again - it worked well for nearly a month but now after a couple of hours it gives me the same error.

I have no idea how to solve it as this is everything i get from the log.

The program is huge and it doesn’t perform any action - so i dont understand why it’s behaving like this

6

Hi everyone, on local it works fine and never stops - this happens only when uploaded in Koyeb.

Looking for a kind response, thanks

7

Hi @Maurizio,

You are deploying on the Free instance which automatically sleeps after 1 hour of inactivity. This is why your instance stops.

If you want to keep your instance running, you need to update your Service and deploy it on an Eco or Standard instance. This way you can disable scale to zero in the scaling section of your Service settings.

8

Hello David, thank you for your kind response.
I upgraded to PRO today and it gives me the same error.

Additionally i just doesnt go to sleep, it stops and any API call or actions after 1 hour of inactivity are ignored as server results inactive

Thank you for your time and your help, looking forward for your response

9

I see you updated your Free instance to an eNano. Your service would not sleep anymore using this instance so it should resolve your problem.