Stefano Marinelli
boosted
Stefano Marinelli
boosted
Quick status update regarding usa02.bsd.cafe.
Yesterday, at 16:11 my monitoring reported the server as unreachable.
The provider’s console indicated urgent maintenance on the physical host, and the VM was not manageable. The console could be opened, but the system was entirely unresponsive.
A support ticket was opened at 21:00. There was no reply until the following morning.
After posting an update on Mastodon, I was contacted and asked for the ticket number. Once provided, the server became reachable through the console again, although still disconnected from the network. It appeared to have been running during the outage, just isolated.
Several tests were performed, but network connectivity did not return.
At 10:56 support replied stating that the VM had been relocated to a new node. In practice it remained offline, and I reported this.
Around 11:10 they accessed the console; I joined as well. A hard reboot was performed, leading to a filesystem check.
At 11:15 the server became reachable again. Support then confirmed they had identified and resolved the underlying issue.
It took more effort than it should have to get this resolved, and the whole process was far from smooth. Still, this is the first time anything like this has happened in many years, and my trust remains.
RE: https://mastodon.bsd.cafe/@stefano/115609842637396244
usa02.bsd.cafe is back
Quick status update regarding usa02.bsd.cafe.
Yesterday, at 16:11 my monitoring reported the server as unreachable.
The provider’s console indicated urgent maintenance on the physical host, and the VM was not manageable. The console could be opened, but the system was entirely unresponsive.
A support ticket was opened at 21:00. There was no reply until the following morning.
After posting an update on Mastodon, I was contacted and asked for the ticket number. Once provided, the server became reachable through the console again, although still disconnected from the network. It appeared to have been running during the outage, just isolated.
Several tests were performed, but network connectivity did not return.
At 10:56 support replied stating that the VM had been relocated to a new node. In practice it remained offline, and I reported this.
Around 11:10 they accessed the console; I joined as well. A hard reboot was performed, leading to a filesystem check.
At 11:15 the server became reachable again. Support then confirmed they had identified and resolved the underlying issue.
It took more effort than it should have to get this resolved, and the whole process was far from smooth. Still, this is the first time anything like this has happened in many years, and my trust remains.
RE: https://mastodon.bsd.cafe/@stefano/115609842637396244
usa02.bsd.cafe is back
Quick status update regarding usa02.bsd.cafe.
Yesterday, at 16:11 my monitoring reported the server as unreachable.
The provider’s console indicated urgent maintenance on the physical host, and the VM was not manageable. The console could be opened, but the system was entirely unresponsive.
A support ticket was opened at 21:00. There was no reply until the following morning.
After posting an update on Mastodon, I was contacted and asked for the ticket number. Once provided, the server became reachable through the console again, although still disconnected from the network. It appeared to have been running during the outage, just isolated.
Several tests were performed, but network connectivity did not return.
At 10:56 support replied stating that the VM had been relocated to a new node. In practice it remained offline, and I reported this.
Around 11:10 they accessed the console; I joined as well. A hard reboot was performed, leading to a filesystem check.
At 11:15 the server became reachable again. Support then confirmed they had identified and resolved the underlying issue.
It took more effort than it should have to get this resolved, and the whole process was far from smooth. Still, this is the first time anything like this has happened in many years, and my trust remains.
usa02.bsd.cafe isn't accessible as Hetzner is having problems on the physical node.
This shouldn't be a problem as the DNS should have disabled it as soon as it stopped responding
Stefano Marinelli
boosted
Stefano Marinelli
boosted
Stefano Marinelli
boosted
Stefano Marinelli
boosted
I've just incremented the number of streaming and puma processes so Mastodon should be more responsive and show less 500 errors.
It was already quite fast and the 500 errors were rare, but this won't harm
I've just incremented the number of streaming and puma processes so Mastodon should be more responsive and show less 500 errors.
It was already quite fast and the 500 errors were rare, but this won't harm
Stefano Marinelli
boosted
The BSD Cafe instances have just been updated to Mastodon v4.5.0.
There was a bit of a slowdown as the secondary instance went smoothly (but it's underpowered), while the primary one took longer because I had to update Node.
But we're there!
Among the main new features: quote posts and other things, like the remote fetching of replies - which I had, however, already enabled on v4.4.x in recent weeks.
Enjoy!
#Mastodon #BSDCafe #BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements
The BSD Cafe instances have just been updated to Mastodon v4.5.0.
There was a bit of a slowdown as the secondary instance went smoothly (but it's underpowered), while the primary one took longer because I had to update Node.
But we're there!
Among the main new features: quote posts and other things, like the remote fetching of replies - which I had, however, already enabled on v4.4.x in recent weeks.
Enjoy!
#Mastodon #BSDCafe #BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements
Stefano Marinelli
boosted
Stefano Marinelli
boosted