| 59 | |
| 60 | == Why is my Alert Hub not fetching messages? == |
| 61 | |
| 62 | There can be several reasons why your alert hub is not fetching the alerts from external system. There may be some potential bug due to some unforeseen condition which may cause breaking. This should be addressed by the experience developer as may lead to data loss and other issues. Other reasons can be solved through UI. Note that both the described problem may exist in the system. |
| 63 | |
| 64 | 1. Message Polling Timeout/ Error etc. |
| 65 | |
| 66 | a. Login as admin. |
| 67 | b. Go to raw database table. From UI: Administration -> Database or from URL: /eden/appadmin/index |
| 68 | c. Search for msg_rss_channel. Click on it and open up. |
| 69 | d. Look for the RSS Channel which is not fetching up the messages. Note the channel_id for the same channel. |
| 70 | e. Go back to raw database tables. |
| 71 | f. Go to scheduler_task table. |
| 72 | g. In the query, you can search for message polling as: db.scheduler_task.args =='["msg_rss_channel", channel_id]'. The channel_id is the one we got from step d. |
| 73 | h. This will bring up the required channel. Check the scheduler_task.status. This should be QUEUED. If this is TIMEOUT or STOPPED or EXPIRED or FAILED, turn this to QUEUED and set the next run time. |
| 74 | i. This should solve the problem. Check Problem Number 2 as well for confirmation. |
| 75 | |
| 76 | [http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/Evaluation Simulation and Evaluation Methodology] for ensuring your system performs to your requirements before going live. Implementers are encourage to conduct simulations and evaluate the system periodically, at least, once every year. |