krallin
commented
3 years ago This means something is killing your program. It’s not something Supercronic does or control
A common thing that kills your programs is using too much memory.
Check if perhaps there is anything in dmesg, or review how you enforce memory limits.
Hope this helps!
On Thu, 6 May 2021 at 17:57, bjsmiley @.***> wrote:
Hello,
testing locally everything is running fine however once supercronic is started in k8s, I get this error message every minute:
level=error msg="error running command: signal: killed" iteration=6 job.command="dotnet /app/myapp.dll > /proc/1/fd/1 2> /proc/1/fd/2" job.position=1 job.schedule=" *"
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/aptible/supercronic/issues/87, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANIHVUWWAK6BODYA7JB3XTTMLC5ZANCNFSM44HOWAUA .
bjsmiley
Hello,
testing locally everything is running fine however once supercronic is started in k8s, I get this error message every minute:
level=error msg="error running command: signal: killed" iteration=6 job.command="dotnet /app/myapp.dll > /proc/1/fd/1 2> /proc/1/fd/2" job.position=1 job.schedule="* * * * *"