From a0a1bc77887e5c979e6457ed861a709b2aee6bc8 Mon Sep 17 00:00:00 2001
From: Pierre-Yves Chibon <pingou@pingoured.fr>
Date: Wed, 12 Feb 2020 11:55:44 +0100
Subject: [PATCH] Document how to check on robosignatory

Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>
---
 fix_robosignatory.md | 46 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)
 create mode 100644 fix_robosignatory.md

diff --git a/fix_robosignatory.md b/fix_robosignatory.md
new file mode 100644
index 0000000..fd4c6bc
--- /dev/null
+++ b/fix_robosignatory.md
@@ -0,0 +1,46 @@
+# How to check/fix robosignatory on misbehaving
+
+/!\ sysadmin-main can access robosignatory in staging, but production is only
+    accessible to a very limited set of people.
+
+* Check the status of robosignatory:
+..* Log into: ``autosign01.stg.phx2.fedoraproject.org``
+..* Check the logs:
+
+```
+# journalctl -f -l -u fm-consumer@robosignatory
+```
+
+..* If the service is not running properly, restart it:
+
+```
+# systemctl restart fm-consumer@robosignatory.service
+```
+
+* Check the status of the signing-vault
+..* Log into: ``sign-vault01.stg.phx2.fedoraproject.org``
+..* Check the status of sigul server:
+
+```
+# tail -f /var/log/sigul_server.log
+```
+
+..* If needed, restart the sigul server:
+
+```
+# sigul_server -dvv
+```
+
+* Check the status of the signing-bridge
+..* Log into: ``sign-bridge01.stg.phx2.fedoraproject.org``
+..* Check the status of the sigul bridge:
+
+```
+# tail -f /var/log/sigul_bridge.log
+```
+
+..* If needed, restart the sigul bridge:
+
+```
+# sigul_bridge -dvv
+```