The home of Alitheia Core

Running Alitheia Core

The usual workflow for running Alitheia Core is the following:

• Install and run the software
• Choose and install a few of plug-ins
• Install a project
• Depending on the size of the project, wait for some time
• Results are in the database

When things go wrong

When things go wrong (and with Alitheia Core being a research tool things can often go wrong), all the user has to do is restart the metadata or plug-in synchronisation options. Alitheia Core usualy isolates failures and tries hard to maintain metadata consistency. If there is an error, you could do the following:

• Check the logs. There is a lot of information that is being written in various logs. The logs reside in $ALITHEIA/runner/logs. Errors and debugging information are recorded in at least the following logs:
  • alitheia.log General debugging info and job results (or errors)
  • updater.log Log specific to the updater service functions. Tons of debugging messages.
  • webadmin.log Log specific to the Web Administration console
  • hibernate.log Log specific to the Hibernate ORM system. Check here for exceptions when creating new plug-ins that use custom tables.

• See the reason (exception) that caused the problem. All jobs in Alitheia Core will die with an exception, which is recorded in either the log or the Jobs web admin tab or both.

• Report it to the devel mailing list. Problems that are not reported cannot be fixed. Attempts to debug the problem and patches are also most welcome.