Hmm, I must have missed a step as when I reinstalled everything after I
switched to Baruwa enterprise (I wanted upgrades/fixes to be easier to
apply), I am no longer getting status to work on Server B. Not only does
it not show the correct status on Server A for Server B. But Server B
does nto show the correct status of itself. Though I just realized that
I get an error when I try to release a message stored on Server A and Im
doing it from Server B. Need to look into that first I guess.
On 2013-02-22 09:31, Raymond Norton wrote:
Does anyone know what I might be missing or have configured wrong
here?
I set server A & B to use memcached, rabbitmq, and postgres of server
A.
Server A I added it as a node to itself. Check status and celery
shows the request was properly processed.
Server B I added it as a node to itself. Check status and all comes
back fine on Server A celery log, so we know rabitmq is working.
Added Server B as a node on Server A, but it comes up faulty and
nothing is logged in celery. Same the other way around (Adding Server
A node to B)
However, I can release messages from either server, if I am on the
local web interface that the message passed through.
It seems like its the way rabbitmq is called from the local box, vs a
remote connection. Either that, or I am missing a config change on
Server B.
_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056
