Error Problem investigation

Since we now deployed master again, a lot of work to be done, is expected to be error/bug related work. So i thought it would be best to list some of the tools at our disposal (and maybe even some methods) to find the specific error that caused a problem.

Tools at our disposal

• Every admin on ontohub.org, develop.ontohub.org and staging.ontohub.org has access to the failures produced during a sidekiq run:
  • Click on User Name (top bar to the right) -> Jobs -> Failures (Sidekiq top bar)
  • You can click on a specific error to get the (poorly formatted) stack-trace.
• On every machine we have the ontohub-console.sh script which will allow you to fire up a pry console to work on the system (like rails c but in production mode).
  • ssh into-a-ontohub-machine
  • ./ontohub-console.sh
• On every machine we can (of course) look directly into the database:
  • ssh into-a-ontohub-machine
  • su postgres
  • psql -d ontohub

Filesystem?

• You can find the current instance here: /srv/http/ontohub/current/
• git-user home (ssh-push): /srv/http/ontohub/shared/data/git_user
• git-daemon (public read-access): /srv/http/ontohub/shared/data/git_daemon

Logs

• Sidekiq: /srv/http/ontohub/shared/log/sidekiq.log
• Git/SSH: /srv/http/ontohub/shared/log/git.log
• Everything-Else: /srv/http/ontohub/shared/log/production.log

How do i make myself an admin?

The easiest (and usually best way, is to talk to an admin). But if it needs to happen fast because is is eleven o'clock at night you can do this:

• ssh into-a-ontohub-machine
• ./ontohub-console.sh
• user = User.where(email: 'my-email-here').first
• user.admin = true
• user.save

If you also need to manually confirm your account you can issue this:

• user.confirm!

Discovering a new issue

If you discover a new issue, you should report it, some useful informations on that can be found here: Reporting Errors and Issues.