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

problem in Symfony 4 #230

Open
HecFranco opened this issue Apr 12, 2019 · 3 comments
Open

problem in Symfony 4 #230

HecFranco opened this issue Apr 12, 2019 · 3 comments

Comments

@HecFranco
Copy link

It launches the jobs and persists in the table, but they are never executed. Does anyone know how they are thrown?

@HecFranco
Copy link
Author

How is the supervisor configured? in what file for symfony 4?

@versh23
Copy link

versh23 commented May 6, 2019

supervisor is not a part of symfony.
http://supervisord.org/configuration.html

@cmmata
Copy link

cmmata commented May 7, 2019

I have this bundle running with Supervisor and SF3.4, but it must be the same with SF4. Here you have an example configuration I'm using. I think it should work only removing the --env=prod argument.

[program:jms_job_queue_runner_long]
command=php /var/www/example/bin/console jms-job-queue:run --env=prod --queue=long
process_name=%(program_name)s
numprocs=1
directory=/tmp
autostart=true
autorestart=true
startsecs=60
startretries=10
user=nginx
redirect_stderr=false
stdout_logfile=/var/www/example/var/logs/jms_job_queue_runner_long.out.log
stdout_capture_maxbytes=1MB
stderr_logfile=/var/www/example/var/logs/jms_job_queue_runner_long.error.log
stderr_capture_maxbytes=1MB

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

3 participants