Logfiles

Retrospectiva – as a RubyOnRails application – comes with a built-in logger. All messages are usually written to the log/production.log file (unless you are not running in production mode). You can open and read the file using a simple text editor. To monitor the current processing of your installation, go to your Retrospectiva directory and type

  tail -f log/production.log

General

Before you despair, Retrospectiva comes together with a small diagnostics tool called fix. If you want to test your installation for possible error sources just run the script with the user account that will later run the application on the web. It you (for example) run your application using Webrick or Mongrel as hugo, you need to use the following example:

  su hugo -c "ruby script/fix" 

If you run Retrospectiva within Apache+FCGI, your executing user account will most likely be www-data. In that case the right command would be:

  su www-data -c "ruby script/fix" 

Browser hangs when accessing source browser or changesets

Every time you visit a site which accesses the repository, Retrospectiva will sync the changesets to its database, which can take a very long time and may cause a timeout.

Fortunately you can also sync it manually using script/repository_syncer. See the Rails log for status messages.