❌

Normal view

Managed Database Clusters

Jul 3, 08:20 UTC
Resolved - Our engineering team has resolved the issue with Managed Database Clusters. All database systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Jul 3, 06:08 UTC
Monitoring - Our engineering team has implemented a fix to resolve the issue with Managed Database Clusters and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

Jul 3, 02:28 UTC
Update - Our engineering team is still investigating the issue affecting Managed Database Clusters. Users may still encounter delays creating/scaling/forking/restoring the aforementioned Managed Database Clusters.

We are working to resolve this as soon as possible. we apologize for the inconvenience. We will post an update here once we have more information.

Jul 2, 22:04 UTC
Investigating - Our engineering team is investigating an issue affecting Managed Database Clusters. Currently, users may encounter delays when creating/scaling/forking and restoring Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka, and Valkey clusters through the Cloud Control Panel or API.

We apologize for the inconvenience and will provide further updates as soon as more information is available.

Upgrade from 11.3.x to 11.4.0 results in a 500 error

So I did a standard composer upgrade.

sudo -u www-data /usr/bin/php8.4 /usr/local/bin/composer update "drupal/*" --with-all-dependencies

and all went well.
Then I opened my browser at example.com/update.php and got a 500.

AH01071: Got error 'PHP message: PHP Warning: require_once(autoload_runtime.php): Failed to open stream: No such file or directory in /var/www/website.com/web/update.php on line 13; PHP message: PHP Fatal error: Uncaught Error: Failed opening required 'autoload_runtime.php' (include_path='.:/usr/share/php') in /var/www/website.com/web/update.php:13\nStack trace:\n#0 {main}\n thrown in /var/www/website.com/web/update.php on line 13'

So in the update.php and the index.php I had to change this bit:

// require_once 'autoload_runtime.php';
require_once __DIR__ . '/../vendor/autoload_runtime.php';

What's wrong on my system? I can't imagine this should need to be done?

submitted by /u/Chris8080
[link] [comments]

DNS Lookup Failures for Managed Database

Jul 1, 16:28 UTC
Resolved - The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.

Jul 1, 12:15 UTC
Update - We are continuing to investigate this issue.

Jul 1, 11:35 UTC
Investigating - As of 06:39 UTC, our Engineering team is investigating reports of intermittent DNS lookup failures for Managed Database hostnames from Managed Kubernetes, primarily affecting connections from Managed Kubernetes to Managed Database hostnames.

At this point, customers in the FRA1 region may experience intermittent connectivity issues.

We apologize for the inconvenience and will share an update once we have more information.

Droplet Resize

Jul 1, 13:28 UTC
Resolved - Our Engineering team has confirmed that the issue impacting Droplet resizes using the "Downscale Anytime" option has been fully resolved. Users can now resize their Droplets using the "Downscale Anytime" option without any issues.

We appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.

Jul 1, 12:43 UTC
Monitoring - Our Engineering team has identified the root cause of the issue affecting Droplet resizes using the "Downscale Anytime" option and has implemented a fix. Users should now be able to resize their Droplets using the "Downscale Anytime" option without experiencing any issues or errors.

We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

Jul 1, 11:13 UTC
Investigating - Our Engineering team is investigating an issue affecting Droplet resizes using the "Downscale Anytime" option. At this time users may find this option unavailable or unresponsive in the Cloud Control Panel.

As a workaround, resizes can be performed via the API while we work to resolve this issue.

We apologize for the inconvenience and will share an update once we have more information.

Agent Timeouts While Retrieving Data from Knowledge Bases

Jul 2, 03:38 UTC
Resolved - This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.

Jul 1, 08:39 UTC
Identified - Our Engineering team has identified the issue causing Agents to experience timeouts while retrieving data from Knowledge Bases.

Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority.

We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

Jul 1, 06:25 UTC
Investigating - Our Engineering team is currently investigating an issue where Agents are experiencing timeouts while retrieving data from Knowledge Bases. As a result, affected Agents may fail to retrieve data and return the following error:

"Failed to retrieve data from Knowledge base(s) - timeout"

Please be assured that we are treating this as a high-priority issue and are actively working to mitigate it.

We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.

Breadcrumbs keep spontaneously disappearing and I’m losing my mind

In my Drupal 10’s site breadcrumb trails, I noticed that my nodes were only displaying the top-level node and the current node, despite being several levels deep in the menu navigation. So, for example, a node four levels deep:

Top-level Node > Second-level Node > Third-level Node > Current Node

Will only show the top and current node in the breadcrumb:

Top Level Node > Current Node

The only thing that will get the breadcrumb to show correctly is if I make a brand new node to replace the top-level node and then move the other nodes one at a time underneath it via each node's node edit page (moving things in the menu editor doesn't help).

This seems to be ok for a while... and then some unknown action triggers all of the breadcrumbs within the current menu trail to vanish while I’m not paying attention!

This site hosted on Pantheon. For those familiar with Pantheon, this is a multidev clone of another site whose breadcrumbs are working fine. After making the multidev clone, I changed some content before I noticed that the breadcrumbs were misbehaving.

Any troubleshooting ideas would be of great help! Google and ChatGPT just lead me in circles.

submitted by /u/trammeloratreasure
[link] [comments]

Droplet Backup Service

Jun 27, 18:24 UTC
Resolved - Between 00:00 UTC & 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets. During this period, backups scheduled within this window may not have been created and may appear as missing.

Our team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected.

We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. However, if you have any further questions or concerns, please create a support ticket for further analysis.

❌