Well right now I am just working on getting everything working with a single node first and then just going to clone it make the changes to point to the primary. To many changes that had to be made to simply apply them all to the secondary that I already have setup.

Anyway, I got the primary node monitoring itself just fine now. Everything else seems to be working correctly with its status page. I did have to go int the production.ini and correct the hostnames listed and then I had to reboot to get it to work. I used the FQDN which also matches what i have in my hosts file that points the to server primary wan ip. I have plenty of other problems (like email not actually being delivered to the final destination), but as far as the status page, its good to go so far.

On 2013-02-20 13:55, Raymond Norton wrote:
I just about have my 2.0 cluster working, but having trouble with rabbitmq.

As per the docs,  memcached and mq broker are the same for both
scanners. Production.ini of both boxes point to the  scanner A IP.

The remote node is working fine and celery shows the transactions
taking place from the remote box. I am able to check status, release
messages, etc...


However, the local node is not communicating with the broker. No
stats, releasing messages, or log activity. Have tried adding the node by IP and name, but the fqdn is the only way to see the message count,
but all other stats are blank.


Any ideas

_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056

_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056

Reply via email to