json_decode error when REDIS_BACKEND is not localhost

[chrisboulton]

json_decode error when REDIS_BACKEND is not localhost

[chrisboulton]

We sure have, and it's working well for us.

These json_decode errors that I've seen a few issues on recently are starting to alarm me. Which version of PHP are you using in production? Is it the same as development?

Can you possibly modify lib/Resque.php, and in the pop method, add an fwrite(STDOUT, "pop: $item\n"); before the return statement? That way we can have a look at what data we're getting back.

[hSATAC]

I printed out $item
It shows

array (
  0 => 'default',
)

which shouldn't be an array since it came out from lpop

and I went into redis-cli check the job queue, the args are all good.

I think when it lpop somehow it grabbed resque:queues
instead of resque:queue:default

[hSATAC]

I did some experiments.
First I edit /etc/hosts, point queue.mydomain.com to 127.0.0.1
and try start/stop php-resque 10 times, all good.

Then I point back queue.mydomain.com to other server
and try start/stop php-resque 10 times

I found that this situation is not guaranteed. For 1, 2 times it was all good.
And those 8 times with json_decode errors, I found that when it started, it gave some error:

Notice: Undefined offset:  1 in /home/ash_wu/miiicasa/lib/sdk/php-resque/lib/Resque/Worker.php on line 102
PHP Notice:  Undefined offset:  2 in /home/ash_wu/miiicasa/lib/sdk/php-resque/lib/Resque/Worker.php on line 450

I don't know if there are some connections between these error msgs.

[chrisboulton]

It looks like we've got the same problem that we're working on over in issue #32 - #32

[hSATAC]

Following #32