search

contribsys / faktory

Language-agnostic persistent background job server
https://contribsys.com/faktory/
Other
5.78k stars 230 forks source link

Panic crash #410

Closed navaneeth closed 2 years ago

navaneeth commented 2 years ago 
panic: signal: killed

goroutine 17 [running]:
github.com/contribsys/faktory/storage.bootRedis.func2(0xc00012c420, 0xc00001c120, 0x11)
    /Users/mikeperham/src/github.com/contribsys/faktory/storage/redis.go:159 +0x10d
created by github.com/contribsys/faktory/storage.bootRedis
    /Users/mikeperham/src/github.com/contribsys/faktory/storage/redis.go:155 +0xfc5

Are you using an old version? - 1.5.1

mperham commented 2 years ago

Please try the latest version.

On Wed, Aug 3, 2022 at 21:14 Navaneeth.K.N @.***> wrote:

  • Which Faktory package and version? - 1.5.1
  • Which Faktory worker package and version? - Running as Docker container in k8s
  • Please include any relevant worker configuration
    • Golang based workers
    • 3 worker processes
  • Please include any relevant error messages or stacktraces

panic: signal: killed

goroutine 17 [running]:github.com/contribsys/faktory/storage.bootRedis.func2(0xc00012c420, 0xc00001c120, 0x11) /Users/mikeperham/src/github.com/contribsys/faktory/storage/redis.go:159 +0x10d created by github.com/contribsys/faktory/storage.bootRedis /Users/mikeperham/src/github.com/contribsys/faktory/storage/redis.go:155 +0xfc5

Are you using an old version? - 1.5.1

— Reply to this email directly, view it on GitHub https://github.com/contribsys/faktory/issues/410, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAWX3SVFKAF4XC44WTMPDVXM7RVANCNFSM55RBSAXA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

navaneeth commented 2 years ago

Looks like Faktory process was running out of memory. Raised the memory limit and it seems to fix it. I see the memory usage growing consistently. Is there a leak happening?

image

mperham commented 2 years ago

It does us no good to talk of a memory leak in an old version. I need to know if the memory leak is in the latest version, 1.6.1.