"Gentile cliente,
Il vostro nome di dominio bsd.cafe è attualmente registrato presso di noi.
Desideriamo informarvi che è stato rinnovato con successo."
"Dear Customer,
Your domain name bsd.cafe is currently registered with us.
We wish to inform you that it has been successfully renewed."
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
It's Tuesday evening here.
It's cold outside, so I'm already home.
Relaxing with some music.
Have a great [morning, afternoon, evening, night], #BSDCafe
Have a great [morning, afternoon, evening, night], #illumosCafe
Have a great [morning, afternoon, evening, night], #Fediverse
https://song.link/s/7io1erAh1tMxG5VMBC8rVw
#Music #MastoMusic #MastoRadio #FediMusic #FediRadio #JukeBox
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.
It’s been down for more than three hours now. Nothing critical, it’s just one of the nodes in my "CDN" that serves the BSD Cafe’s media (and a bit more), and DNS has already taken it out since it’s not responding.
Still, I’ve never experienced such a long outage on #Hetzner before.
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
Sometimes my soul rises and becomes a white cloud drifting across the sky. It watches, lives in the sunlight, stays quiet and, when it feels sorrow, it cries.
Yet the sky above it is, and will always be, bright and blue.
Have a great week, #BSDCafe
Have a great week, #illumosCafe
Have a great week, #Fediverse
The weeks towards the end of the year are always stressful because of the annual audits in the IT security area. But it's good that I have some time to also do more "interesting" stuff (ok, some parts of the audit topics are also interesting)
But now I'm tired. Good night, BSD Cafe.