You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At around 20:20 PT on 17 April 2024, coco went down, the messages on the #coco_messages slack channel stopped coming and the coco panel on the System Health Quicklook Grafana page showed that coco is down. However, running systemctl status coco on csBfs showed that coco was running (attached screenshot). This caused a confusion about whether the coco service needed to be restarted.
The text was updated successfully, but these errors were encountered:
At around 20:20 PT on 17 April 2024, coco went down, the messages on the #coco_messages slack channel stopped coming and the
![Screenshot 2024-04-24 at 1 30 57 AM](https://private-user-images.githubusercontent.com/90772824/325091555-cc427d9a-34e0-41cf-8e82-b9b55eaf243d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5OTkyMDEsIm5iZiI6MTczODk5ODkwMSwicGF0aCI6Ii85MDc3MjgyNC8zMjUwOTE1NTUtY2M0MjdkOWEtMzRlMC00MWNmLThlODItYjliNTVlYWYyNDNkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDA3MTUwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM2MmI4OWE4NTIxM2Q3OTdmNTE5YTNkOTBhM2RkMzlkMjU0NDQzMWY3YmQ0NTQ5YmM3MjVkN2Q0ZjI4ZWQzZTMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.GsTByu9ggnsBYa40lkmevs7FXHeu8voWeJZw6Hx-4z0)
coco
panel on the System Health Quicklook Grafana page showed that coco is down. However, runningsystemctl status coco
on csBfs showed that coco was running (attached screenshot). This caused a confusion about whether the coco service needed to be restarted.The text was updated successfully, but these errors were encountered: