Contrib.social

Package Manager tasks can exceed wait_timeout on cheap hosting

Open on Drupal.org →
Created on 10 March 2025, 27 days ago

Problem/Motivation

I've been setting up a hobby site using Drupal CMS on cheap shared hosting which has composer and SSH access (using Hostinger). I ran into a problem because the hosts default wait_timeout on database connections is 20 seconds. This meant I was unable to install any modules or run updates from Drupal.org because the DB connection is dropped while we're off doing composer commands. When the kernel terminates we crash because the DB connection is gone and we're unable to release the locks.

Steps to reproduce

Set wait_timeout to a short time and try to use package manager.

Proposed resolution

A few thoughts:

  • Should we have a warning or error on system status if we find this to be short?
  • Can we implement a re-connection - ala ✨ Database ping, close, and reconnect capabilities Active - these timeouts are problematic for more than just package manager
  • Could package manager issue SQL commands to increase the timeout (not sure I like this solution because it is likely to be DB dependent).

Remaining tasks

User interface changes

TBD

Introduced terminology

API changes

TBD

Data model changes

TBD

Release notes snippet

🐛 Bug report
Status

Active

Version

11.0 🔥

Component

package_manager.module

Created by

🇬🇧United Kingdom alexpott 🇪🇺🌍

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @alexpott
  • Comment 27 days ago →
    🇬🇧United Kingdom alexpott 🇪🇺🌍

    I worked around the problem by adding

    $databases['default']['default']['init_commands'] = [
  'waits' => 'SET SESSION wait_timeout=28800',
  'wait 2' => 'SET SESSION interactive_timeout=28800',
];

    to settings.php but I don't think the target audience is going to find that an easy solution.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024