FOR ARCHIVAL PURPOSES ONLY

The information in this wiki hasn't been maintained for a good while. Some of the projects described have since been deprecated.

In particular, the "Ushahidi Platform v3.x" section contains information that is often misleading. Many details about this version of Platform have changed since.

This website is an extraction of the original Ushahidi wiki into a static form. Because of that, functions like logging in, commenting or searching will not work.

For more documentation, please refer to https://docs.ushahidi.com

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once that's done, do an apache2ctl restart for good measure and you should be good to go. Visit http://localhost and do another dance.

mod_rewrite

If you get an a "Not Found" response when the system redirects you to /login, maybe mod_rewrite is getting in the way. If that's the case.:

  • Check that mod_rewrite is installed and enabled. (run a2enmod rewrite in case it isn't)
  • Make sure you have AllowOverride All (as opposed to None) for your directory on the apache conf file (restart apache Apache after that!)

Indexing / Crawling / Messaging services

...

Now that we configured everything, all you have to do is copy and paste the lines below on your command line so that Swiftriver runs as a service

...

More info

Logs to watch

If during instalationinstallation, anything doesn't behave as expected, here are the logs your you should check (double points when if you past paste log dumps on into bug reports!):

  • Apache logs (/var/logs/apache2, mainly error.log)
  • Tomcat logs (/var/logs/tomcat7, mainly catalina.out)
  • Application logs (i.e.: /var/www/application/logs)
  • MySQL logs - enable the general log if you want to really get to the thick of what's going on
  • Service logs - each service will have logs being written on their respective logs directory. Keep an eye on those!

We can't stress enough how helpful these are enough(smile)

Issues with RabbitMQ

If you run rabbitmqctl status and you see something like Error: unable to connect to node 'rabbit@swiftriver-dev': nodedown as a response, RabbitMQ is having proplem problems starting.

Run sudo service rabbitmq-server restart and live RabbitMQ should be good again.


Example swiftriver-api.xml

...

ParameterDescription
mqHostThe host running the RabbitMQ server
mqUserUser to connect to RabbitMQ
mqPasswordPasword Password for the user used to connect to RabbitMQ
solr/serverURLURL of your Solr server
solr/indexerPropertiesLocation of the properties file for the indexer - a background process that periodically updates Solr with the new drops
indexer/lastDropIDPropKeyThe property key that specifies the ID of the last drop to be posted to Solr. This value serves as the reference point for fetching new drops
indexer/batchSizePropKeyThe property key that specifies the maximum no. number of drops to post to Solr during each run
indexer/runIntervalThe property key that specifies how often (in msmilliseconds) the indexer should check for new drops and update Solr
authSchemeNameName of the authentication scheme. The possible values are database and crowdmapid
crowdmapid/serverURLURL of the CrowdmapID deployment