Changes between Version 22 and Version 23 of Deployments/SAMBRO/FAQs


Ignore:
Timestamp:
12/29/16 05:31:09 (5 years ago)
Author:
Biplov Bhandari
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Deployments/SAMBRO/FAQs

    v22 v23  
    6363
    64641. Message Polling Timeout/ Error etc.
    65 
     65[[BR]]
    6666a. Login as admin.
    6767b. Go to raw database table. From UI: Administration -> Database or from URL: /eden/appadmin/index
     
    7373h. 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.
    7474i. This should solve the problem. Check Problem Number 2 as well for confirmation.
     75[[BR]][[BR]]
    7576
     772. Message Parsing Timeout/ Error etc.
     78[[BR]]
     79a. Login as admin.
     80b. Go to raw database table. From UI: Administration -> Database or from URL: /eden/appadmin/index
     81c. Search for msg_rss_channel. Click on it and open up.
     82d. Look for the RSS Channel which is not fetching up the messages. Note the channel_id for the same channel.
     83e. Go back to raw database tables.
     84f. Go to scheduler_task table.
     85g. In the query, you can search for message polling as: db.scheduler_task.args == '[channel_id, "parse_rss_2_cap"]'. The channel_id is the one we got from step d.
     86h. 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.
     87i. This should solve the problem.
     88[[BR]][[BR]]
     89NB: If it didn't run after you try to solve the problem by following above steps, give it one/two more try. If the problem persists, then its best to contact the Service Providers to look at the problem.
    7690[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.