Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seg fault 11 on setprocname #2029

Open
HarryAnkers opened this issue Jan 22, 2024 · 1 comment
Open

Seg fault 11 on setprocname #2029

HarryAnkers opened this issue Jan 22, 2024 · 1 comment

Comments

@HarryAnkers
Copy link

I'm having an issue where I keep getting:
{"event": "Moving job to FailedJobRegistry (Work-horse terminated unexpectedly; waitpid returned 11 (signal 11); )", "level": "warning", "logger": "rq.worker", "timestamp": "2024-01-22T14:07:18.190151Z"}

By tracing logs I was able to tell the seg fault was coming from
https://github.com/rq/rq/blob/2f5fecc1badb75b3e379b5d15c0b60b9c4931baa/rq/worker.py#L893C9-L893C20

When adding a print statement to this on {self.name}: {message} I get:
all-queues-worker_70d3491c-3be4-4a7b-b987-d87a726faa19 Processing perform from test_queue since 1705932438.1094751

If I comment this out in the dependancy it works fine

Running MacOS 14.2.1 (23C71)

@krlx
Copy link

krlx commented Feb 5, 2024

Hi @HarryAnkers, unrelated question: How did you get rq to log the "Moving job to FailedJobRegistry"? Thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants