Article Content
Article Number | 000031318 |
Applies To | RSA Product Set: Security Analytics RSA Product/Service Type: SA Security Analytics Server RSA Version/Condition: 10.4.1.0 Platform: CentOS O/S Version: 6 |
Issue | This issue describes when customers try to perform an SA upgrade from 10.4.1 to 10.5.0 and they run into issues with rabbitmq after Log Hybrid is upgraded. LogCollector device doesn't show up to date on SA UI and also appears unavailable. [root@igteblrsiemhyb1 tmp]# service rabbitmq-server status DIAGNOSTICS Also /var/log/rabbitmq/startup_log file shows following error: [{app_utils,load_applications,2,[]}, |
Cause | We've seen a few issues like this that stem from the nw_admin plugin.This is sometimes fixed by editing the /etc/rabbitmq/rsa_enabled_plugins file, removing nw_admin from it, then running puppet agent -t. |
Workaround | Steps for the workaround in order to fix this issue are listed below: 1- Check RabbitMQ port is opened: "netstat -ntpl |grep 4369" 2 - Take a backup of the /etc/rabbitmq/rsa_enabled_plugins file 3- Edit the /etc/rabbitmq/rsa_enabled_plugins file 4- Remove nw_admin from it 5- Then run puppet agent -t 6 - Check RabbitMQ service: # service rabbitmq-server status 7- If RabbitMQ is up, restart jettysrv on the SA server: # stop jettysrv 8 - Restart the nwlogcollector service from the Log Hybrid device: # stop nwlogcollector 9- If this doesn't work, try reinstalling the rsa-puppet-modules rpm: # yum reinstall rsa-puppet-modules 10- If there is no relief from either of these, run the command manually and capture the output to attach to a Jira case for further troubleshooting: # rabbitmq-plugins enable rabbitmq_federation |