Skip to content

Latest commit

 

History

History
15 lines (13 loc) · 1.35 KB

troubleshooting.md

File metadata and controls

15 lines (13 loc) · 1.35 KB

Troubleshooting

This section lists some commands that may help you to find and solve issues in a new deployment on staging or production server. To connect on our servers you need a working yubikey.

  • connect via ssh ssh <username>@entitlementcard.tuerantuer.org or (entitlementcard-test.tuerantuer.org)
  • switch to root user sudo -i or sudo - u <user> to a particular user.
  1. Check backend health log: journalctl -u eak-backend.service --since "1h ago"
  2. Check backend log for particular message: journalctl -u eak-backend.service --since "1h ago" | grep "<your message>"
  3. Restart backend service: systemctl restart eak-backend.service
  4. Check installed version of particular debian package: apt-cache policy eak-administration same works for backend with eak-backend
  5. Check available debian package versions: ll -trh /srv/local-apt-repository
  6. Check if latest database migration was applied: sudo -u backend psql entitlementcard then SELECT * from migrations;
  7. Create admin/store manager accounts: sudo -u backend /opt/ehrenamtskarte/backend/bin/backend create-admin <command>. You can find example in runConfigs
  8. Check if webhook for the debian package installation worked: journalctl -x --since "48 hours ago" | grep webhook and find info about the debian package installation: vim /var/log/apt/history.log