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
At the present time email sent to @icloud.com addresses via our DE SMTP server is being either deferred or bounced. We're working with Apple to resolve the issue and will update this post when more information is available.
In the meantime, DE mail customers can work around the issue by using our alternate DE SMTP server in their email client settings. The alternate server is: smtp2.de.opalstack.com
The block was cleared as of 14:22 UTC today. Mail sent to iCloud email addresses via our DE SMTP are no longer bouncing.
Apple informed us that our SMTP is caught up in a block of a larger IP address range operated by our network provider. Our provider is working with Apple to resolve the issue.
If you are affected by this you can configure your mail client to use smtp2.de.opalstack.com as its SMTP server as a temporary workaround.
Apple informed us that our SMTP is caught up in a block of a larger IP address range operated by our network provider. Our provider is working with Apple to resolve the issue.
If you are affected by this you can configure your mail client to use smtp2.de.opalstack.com as its SMTP server as a temporary workaround.
No incidents reported
No incidents reported