This is a long shot but maybe someone had the same problem as i do. On my production server (ubuntu 12.04) i have supervisor running a queue:listen job which grabs stuff from beanstalk. This works, for the most part. Problem is that queue:listen only processes some of the jobs, but i can't end up with a patern.

Beanstalk queue is being cleared, which tells me that the job is actually being pulled from the queue. I have put some Log:info inside the job, in the fire method but they are not writting anything on the log (again sometimes)

So to recap, job is pushed to queue, pulled from beanstalk EVERY time (i can see it on the console), but sometimes it doesn't execute. The laravel log writes NO errors during those jobs, neither does the PHP or supervisor ones.

All the above lead me to believe there is something wrong with the listen command when run by supervisor, cause when i run it manually it fires every time.

Supervisor version is 3.0 and i can see it running the artisan command on the top. Supervisor is running as a user which has priviliges. Laravel version is 4.2 and updated daily Supervisor job follows : command=php artisan queue:listen --tries=2 directory=httpdocs/laravel stout_logfile=httpdocs/laravel/app/storage/logs/supervisor.log stderr_logfile=httpdocs/laravel/app/storage/logs/supervisor-err.log redirect_stderr=true numprocs=100 process_name=%(program_name)s_%(process_num)s autostart=true autorestart=true stderr_logfile_maxbytes=1MB

Any input is welcome....