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
Carrot service should warn users when process is already running #78
Comments
I've seen this reported a couple of times but have been struggling to reliably reproduce this on my side. Please could you let me know:
I have a suspicion what might be causing this, and a potential fix, but I just need to check your definitely seeing the same issue I think you're seeing |
I waited for several seconds after that before I published the message. But when I look at the failed message log, it's there!
Then when I run it again, exact same message, somehow it magically works!
This to me feels like some kind of weird import error as I've changed the code recently from expecting an int to expecting a UUID, but for some reason it's still failing because it expected an int on the first task execution. I can't figure out why that is. |
I should mention that I'm using carrot in non-daemon mode and that after code changes I ctrl-c and then start carrot like this:
|
I went looking at the code and it became very clear to me that there was no way this could possibly be happening. I thought I had successfully issued a daemon stop, but when I did a
Once I successfully killed that, everything works as expected! Turns out it's my fault :( So this is unsolicited advice and I'm going to sound super ungrateful, but if carrot had warned me saying "you're running me in non-daemon mode but I see some carrot processes still running in the background, are you sure you want to do this?" I probably would have ctrl-c'd and figured it out. I'm not sure exactly the best way to do that, of course, other than that it's probably in the management command for non-daemon start. I'll take a look at that while I'm putting this PR together. |
So its not the issue I suspected. I'll see if I can get a warning like that into the next release |
I'm working on my PR for a django command to queue jobs. It's a little bit ugly trying to support args and kwargs and how to handle types and such.
One thing I've noticed is that the first job I queue when starting carrot up for the first time doesn't get executed and it doesn't matter if the queuing is coming from this management command or a view that also triggers a job.
This might be because I've got some stuck jobs in my queue:
Any thoughts as to what might be going on here?
Here's where I'm at with the management command:
The text was updated successfully, but these errors were encountered: