starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[GH-ISSUE #10445] Wordpress MariaDB fails to start after container reboot #2256

New issue

Closed

opened 2026-02-26 12:51:49 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:51:49 +03:00

Owner

Originally created by @notgriffin on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10445

Originally assigned to: @MickLesk, @Copilot on GitHub.

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

wordpress.sh

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wordpress.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.10

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

When a Wordpress container is restarted, I encountered an issue where MariaDB failed to start, resulting in Wordpress failing to load due to a database connection error. I found the permanent solution to be as follows:

echo "d /run/mysqld 0755 mysql mysql -" > /etc/tmpfiles.d/mariadb.conf
systemd-tmpfiles --create
systemctl restart mariadb

The following is a temporary check for if this was the issue:

mkdir -p /run/mysqld
chown mysql:mysql /run/mysqld
chmod 755 /run/mysqld
systemctl restart mariadb

I assume this occurred because the /run/mysqld folder is created on the script creating the Wordpress site, but fails to recreate on container restart.

🔄 Steps to reproduce the issue.

Start a wordpress container using the proxmox script.
Set up some basic Wordpress configurations.
Restart the container.
Connect back to the site to see the error.

❌ Paste the full error output (if available).

~# systemctl status mariadb.service

× mariadb.service - MariaDB 12.2.1 database server
     Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/mariadb.service.d
             └─migrated-from-my.cnf-settings.conf
     Active: failed (Result: exit-code) since Wed 2025-12-31 10:23:32 EST; 2s ago
 Invocation: 2f55d5567d344b3894ab600f6245c5d9
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 1875 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && echo _WSREP_START_POSITION=$VAR > /run/mysqld/wsrep-start-position || exit 1 (code=exited, status=1/FAILURE)
   Mem peak: 3.1M
        CPU: 23ms

🖼️ Additional context (optional).

No response

Originally created by @notgriffin on GitHub (Dec 31, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10445 Originally assigned to: @MickLesk, @Copilot on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? wordpress.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wordpress.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.10 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. When a Wordpress container is restarted, I encountered an issue where MariaDB failed to start, resulting in Wordpress failing to load due to a database connection error. I found the permanent solution to be as follows: ```bash echo "d /run/mysqld 0755 mysql mysql -" > /etc/tmpfiles.d/mariadb.conf systemd-tmpfiles --create systemctl restart mariadb ``` The following is a temporary check for if this was the issue: ```bash mkdir -p /run/mysqld chown mysql:mysql /run/mysqld chmod 755 /run/mysqld systemctl restart mariadb ``` I assume this occurred because the /run/mysqld folder is created on the script creating the Wordpress site, but fails to recreate on container restart. ### 🔄 Steps to reproduce the issue. 1. Start a wordpress container using the proxmox script. 2. Set up some basic Wordpress configurations. 3. Restart the container. 4. Connect back to the site to see the error. ### ❌ Paste the full error output (if available). ``` ~# systemctl status mariadb.service × mariadb.service - MariaDB 12.2.1 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/mariadb.service.d └─migrated-from-my.cnf-settings.conf Active: failed (Result: exit-code) since Wed 2025-12-31 10:23:32 EST; 2s ago Invocation: 2f55d5567d344b3894ab600f6245c5d9 Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Process: 1875 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && echo _WSREP_START_POSITION=$VAR > /run/mysqld/wsrep-start-position || exit 1 (code=exited, status=1/FAILURE) Mem peak: 3.1M CPU: 23ms ``` ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:51:49 +03:00

closed this issue
added the
bug
label

kerem referenced this issue

2026-02-26 13:34:12 +03:00

[PR #2256] [MERGED] [core] update .app files #3641

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2256

No description provided.

Rows
Columns