Skip to content

Latest commit

 

History

History
88 lines (54 loc) · 3.95 KB

faq.md

File metadata and controls

88 lines (54 loc) · 3.95 KB

FAQ

What does this error message mean?

ERROR! Decryption failed

You see this error message if you are running an ansible playbook without passing in the ansible-vault password. Read this documentation to find out how to pass in the password.

How do I deploy a new version of IMS?

Do a git push to push your updates to the ims git repo. Then run the ims playbook:

ansible-playbook --limit=ims ims.yml

This triggers a git pull on the remote vm. It will build a new docker image and then restart the uwsgi container.

How do I restore IMS after a complete failure?

Run the ims.yml playbook to configure the ims VM, including building all docker containers and starting all services.

ansible-playbook --limit=ims ims.yml

If IMS is still missing data, then restore it from a local backup:

ansible-playbook --limit=ims ims-restore.yml

How do I sync a development IMS from IMS?

ansible-playbook ims-dump.yml
ansible-playbook --limit=local-dev ims-restore.yml

Why do I see failed sshd units when I ssh into the machine?

It is OK to ignore these failed units. This is what I see when I ssh into the bastion vm:

$ ssh [email protected]
Last login: Wed Mar 15 11:22:04 UTC 2017 from 193.63.221.99 on ssh
Container Linux by CoreOS stable (1298.5.0)
Failed Units: 4
  [email protected]:22-111.73.45.208:4349.service
  [email protected]:22-111.73.45.208:2605.service
  [email protected]:22-111.73.45.208:3462.service
  [email protected]:22-111.73.45.208:3081.service

This happens when somebody (possibly us, or possibly a bad person) tried to login via ssh, and the ssh daemon failed. We have noticed that somebody (bad person) is continually trying to ssh to bastion every one second. It is acceptable for the ssh daemon to have a small number of safe fails given this level of attempted connections.

You could clear them like this: sudo systemctl reset-failed

Note that this shouldn't happen anymore since the VM has only SSH access in the Charité Intranet.

IMS ansible-playbook fails to authenticate your ssh key for the IMS git repository and perform a git pull

This can be caused by a number of problems.

On a Mac one issue might be that your ssh key is not loaded automatically so cannot be forwarded.

Edit ~/.ssh/config to contain: Host * UseKeychain yes

Then add your private ssh key to your keychain: /usr/bin/ssh-add -K /path/to/private_key (e.g. /usr/bin/ssh-add -K ~/.ssh/id_rsa)

Another possible issue could be that you forgot to associate your public ssh key with your github account.

You can follow this article to add your public key to github https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/

Other issues can be explored at https://developer.github.com/guides/using-ssh-agent-forwarding/

How to edit secrets files

Reference to the ansible documentation

How can I read logs from postgres

Postgres store its log in a specific folder that is mounted into the ims-postgres docker container. This folder is called pg_log and should be available through this path /data01/postgres_data/userdata/pg_log. The problem though is that to access this folder you need to use sudo.

You can use sudo commands to do every command inside that folder (e.g. sudo ls /data01/postgres_data/userdata/pg_log/ to check the log files) or you can start an interactive sudo terminal instance using sudo -i.

When I'm trying to get the details of a cellline, the executive dashboard return an error and pg_log shows a query error

This can happen when you restore from a backup that is a bit older and there have been schema changes since then. You can usually fix this by running

sudo systemctl start ims-deploy

on the virtual machine, which will also run the database migrations.