# 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
```