Not Working correctly with Resque 1.26

[Ahmed--Mohsen]

I have recently updated from resque 1.25 to 1.26 and things start to get wired, the workers would appear to be forked but not registered with the Resque.workers

In my case I was supposed to have 10 workers, after running resque:start I only got 5 workers

when entering ps aux | grep resque the 10 workers appear
but in the terminal using Resque.workers or resque-web only 5 appears that are accepting jobs

[dmarkow]

It looks like 1.26 made some changes to how background processes are handled. I'll take a look when I have a chance, but any pull requests are welcome in the mean time.

[YusefOuda]

+1 same issue

[MarlBurroW]

+1 Same issue
ps: http://puu.sh/paS8d/cf1615e60f.png
ui: http://puu.sh/paS9F/302d2a91cf.png

[trappist]

Any movement on this?

[dmarkow]

I haven't had any time to look at this but as I mentioned, anyone else is welcome to debug and figure out what's going on and submit a pull request. I'll try and revisit this soon.

[davegudge]

@dmarkow I was experiencing this issue and after investigating, it appears that the issue is with the resque gem resque/resque#1357.

resque/resque@bfd6b5a appears to fix the issue. I have added a comment to the issue in the resque repository.