tamiwiki:internal:networks:tami_sre
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| tamiwiki:internal:networks:tami_sre [2023/03/05 00:00] – 444b | tamiwiki:internal:networks:tami_sre [2023/03/15 22:35] – 444b | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | This page detials | + | This page details |
| ---- | ---- | ||
| - | Currently, we have a Raspberry pi in the space that runs a realtime Status webpage from UptimeRobot | + | Currently, we have a Raspberry pi in the space that runs a realtime |
| - | The Status page of our Services is here | + | |
| - | |||
| - | In case the network is not functioning, | ||
| Line 14: | Line 11: | ||
| The first step is to identify the nature of the root cause and whether it is related to the network or the infrastructure. | The first step is to identify the nature of the root cause and whether it is related to the network or the infrastructure. | ||
| Use the [https:// | Use the [https:// | ||
| - | * If everything is down, is it definetly | + | * If everything is down(including Tamis IP, 82.80.54.64), is it definitely |
| * If the IP address of Tami is reachable (Ping and Telnet), but the yunohost services are down, its likely just an infra issue | * If the IP address of Tami is reachable (Ping and Telnet), but the yunohost services are down, its likely just an infra issue | ||
| + | * In case the stuff is still not functioning after trying all these steps, you should reach out to someone from the [[tamiwiki/ | ||
| ==== Network ==== | ==== Network ==== | ||
| Line 31: | Line 28: | ||
| * Try to ssh into yunohost. The password is your yunohost SSO password | * Try to ssh into yunohost. The password is your yunohost SSO password | ||
| * ssh < | * ssh < | ||
| + | * Check out the output from the following services | ||
| + | * sudo systemctl status nginx.service (for website issues) | ||
| + | * sudo systemctl status mautrix_telegram.service (for telegram bridge issues) | ||
| + | * For any errors or for any other reason, try restart the service if it is already broken) | ||
| + | * sudo systemctl restart < | ||
| + | * Failing this, try look for more logs. Look up any error messages and go down the rabbit holes | ||
| + | * sudo journalctl -u < | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ---- | ||
| + | QR Code for page, do not delete | ||
| + | {{: | ||
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
