No alerts are being displayed in the BES Dashboard, yet daemons and message channels appear to be running.
Error in POWERpack_Log
Error: Alert Server Connection failed(146 Connection refused) -1
The problem is down to the AlertServer not initialising, of which there could be several reasons. One of the most common causes of this problem is a high number of active alerts in the BES Database (10,000+).
usually, you can check the number of active alerts via a telnet to the AlertServer (telnet localhost 40000 - option s - all messages stored), but as the AlertServer has not initialised, you will be unable to telnet to the AlertServer.
therefore, to check the number of active alerts, perform an SQL query on the BES Database as follows:
1> select count(*) from ISS_PP_Alerts_Table where state = 1
If the number of active alerts is exceedingly high, it may be best to close off all the alerts to allow the AlertServer to initialise. If this is the option you choose, perform the following:
1. Stop the AlertServer and the dbi with the following command=
ppStop -n AlertServer
ppStop -n dbi
2. Connect to the Database with
1> update ISS_PP_Alerts_Table set state = 0 where state = 1
>update iss_pp-alerts_table set state = 0 where state = 1;
3. Restart the AlertServer and the dbi with the following commands
ppStart -n AlertServer
ppStart -n dbi
You should then see the AlertServer initialise in the POWERpack_Log, and also be able to perform a telnet to the AlertServer. Login to the BSD and check that alerts are now coming through to the dashboard.