MariaDB on OPAL4 has crashed, we're working to identify the cause and solution now.
We've seen no further problems since our last update.
The issue with database permissions is resolved and the MariaDB service is back online and operating normally. We will continue to monitor.
We've discovered that there is still a problem with database permissions. We're working to resolve that at this time.
The data restoration has completed and we are continuing to monitor the server as usage increases.
The restoration is approximately 75% complete.
The data restoration is approximately 50% complete.
The MariaDB restore process is still running.
The database corruption is unrecoverable so we will proceed with restoring from backups. The most recent valid backups were from 1.5 hours before the server crashed so we'll proceed with the restore from there.
The restoration process varies in completion time. It may take up to 6 hours or more. We'll keep this post updated.
No incidents reported
No incidents reported
No incidents reported
One of our DE MX servers, mx2.de.opalstack.com on IP 178.162.221.165, was recently blocked by Microsoft. As a result, mail sent to addresses which forward to Microsoft services like hotmail.com, outlook.com, and their international variants would be bounced back to the original sender with an error message.
We've already resolved this issue with Microsoft but they say that it may take 24-48 hours for the block to be fully lifted.
We'll update this post after we've seen no further blocks in a 24 hour period.
No incidents reported
The MariaDB service on opal7.opalstack.com (Phoenix AZ shared hosting) is currently down. We're attempting to restore service and will follow up as soon as possible.
The recovery and repair is complete and the MariaDB service is operating normally.
The cause of the MariaDB outage was corruption in the service's InnoDB store.
The service is now operational while running recovery and repair routines in the background. We expect the recovery and repair to take several hours but the service should remain operational in the interim.
The MariaDB service is back online at this time but service may be intermittent as we continue to troubleshoot.
opal6.opalstack.com (Fraankfurt shared hosting) is currently under heavy load and is responding very slowly. We're attempting to identify and correct the cause at this time and will follow up when more info is available.
The server is back online following the reboot. The cause was a runaway Apache httpd process consuming all of the server's available RAM.
We'll identify the site that caused the problem and will work with the site owner to prevent the problem from occurring again.
We're unable to troubleshoot due to the extremely high load, so we are rebooting the server at this time.
No incidents reported