-
Notifications
You must be signed in to change notification settings - Fork 20
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
All jobs are in new
state and not running
#7
Comments
Otherwise |
I am facing the same issue while using cli flags. OS is not able to create a new process for running worker job when I am using flag package of golang. I need to use it for getting environment specific variables. Can you please help me with a way around? Thanks! |
@mmt7172 use NewFlagSet, |
I also have the same issue, no job are started. Any fixes for that ? |
@x0rzkov as mentioned by slava-vishnyakov: workers run by spawning a second instance of your main binary with because of this several things can interfere with the qor/worker package leaving a job in When the binary runs with example:
this example works only for jobs which will be started immediate (without worker.Schedule embedded in the job Resource) or if the schedule is set to something in the past, seeing the same behavior in the qor-example repo |
Hi everybody!
I was trying to run jobs and everything was fine until I added
bleve.Open
into my script init.The problem is that
bleve.Open
runs a file-based locking for concurrent processes.Suddenly, jobs stopped working. All new Workers got into
new
state and that's about it.After some debugging I found out that Worker works by starting second process and that process was basically locked, because
bleve.Open
was called beforeAdmin
initialization.I think the documentation for qor/worker would benefit from information on how default
cron
runner works.Something along these lines:
The text was updated successfully, but these errors were encountered: