Wordpress problem after full diskpartition

Support
,
1

NethServer Version: NS8
Module: Wordpress 1.1.3

Hello to All,

Today I had a problem with a NS8 node which was running out of disk space on the /home partition. This gave some problems as you can imagine. I would like some advice on the one problem I couldn’t fix so far. I have a few Wordpress instances running, one of them does not work anymore, the others came up nicely after freeing up space and rebooting the server. I get a “Bad Gateway” prompt on pageload. Looking at the messages log it seems that mariadb has a problem, every one or two minutes this kind of errors appears:

Apr 9 21:31:59 server2 systemd[4476]: wordpress-app.service: start operation timed out. Terminating.
Apr 9 21:31:59 server2 systemd[4476]: wordpress-app.service: Control process exited, code=exited, status=1/FAILURE
Apr 9 21:31:59 server2 wordpress2[185464]: 4c85f4aa7290e36efbe2bbac5971088661f8829a53eb708d5c39ed5abdbee580
Apr 9 21:31:59 server2 systemd[4476]: wordpress-app.service: Failed with result ‘timeout’.
Apr 9 21:31:59 server2 systemd[4476]: Failed to start Podman wordpress-app.service.
Apr 9 21:31:59 server2 systemd[4476]: wordpress-app.service: Consumed 1min 29.504s CPU time.
Apr 9 21:31:59 server2 systemd[4476]: wordpress-app.service: Scheduled restart job, restart counter is at 393.
Apr 9 21:31:59 server2 systemd[4476]: Stopped Podman wordpress-app.service.
Apr 9 21:31:59 server2 systemd[4476]: wordpress-app.service: Consumed 1min 29.504s CPU time.
Apr 9 21:31:59 server2 systemd[4476]: Stopping Podman mariadb-app.service…
Apr 9 21:31:59 server2 mariadb-app[185265]: 2026-04-09 19:31:59 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
Apr 9 21:31:59 server2 mariadb-app[185265]: 2026-04-09 19:31:59 0 [Note] InnoDB: FTS optimize thread exiting.
Apr 9 21:31:59 server2 mariadb-app[185265]: 2026-04-09 19:31:59 0 [Note] InnoDB: Starting shutdown…
Apr 9 21:31:59 server2 mariadb-app[185265]: 2026-04-09 19:31:59 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
Apr 9 21:31:59 server2 mariadb-app[185265]: 2026-04-09 19:31:59 0 [Note] InnoDB: Restricted to 2028 pages due to innodb_buf_pool_dump_pct=25
Apr 9 21:31:59 server2 mariadb-app[185265]: 2026-04-09 19:31:59 0 [Note] InnoDB: Buffer pool(s) dump completed at 260409 19:31:59
Apr 9 21:32:00 server2 mariadb-app[185265]: 2026-04-09 19:32:00 0 [Note] InnoDB: Removed temporary tablespace data file: “./ibtmp1”
Apr 9 21:32:00 server2 mariadb-app[185265]: 2026-04-09 19:32:00 0 [Note] InnoDB: Shutdown completed; log sequence number 130626010543; transaction id 65295315
Apr 9 21:32:00 server2 mariadb-app[185265]: 2026-04-09 19:32:00 0 [Note] mariadbd: Shutdown complete
Apr 9 21:32:00 server2 wordpress2[185475]: f6900313792547fa156675c8b8993f2da2c466620ddbe49eb389ff6637ba508c
Apr 9 21:32:00 server2 wordpress2[185495]: f6900313792547fa156675c8b8993f2da2c466620ddbe49eb389ff6637ba508c
Apr 9 21:32:00 server2 systemd[4476]: Stopped Podman mariadb-app.service.
Apr 9 21:32:00 server2 systemd[4476]: Stopping Podman wordpress.service…
Apr 9 21:32:00 server2 systemd[4476]: Removed slice cgroup user-libpod_pod_81ae713a0a5ff604eae6506ddac4dc9841850f16d76c660fa49f30d789634f25.slice.
Apr 9 21:32:00 server2 podman[185505]: wordpress
Apr 9 21:32:00 server2 podman[185528]: 81ae713a0a5ff604eae6506ddac4dc9841850f16d76c660fa49f30d789634f25
Apr 9 21:32:00 server2 systemd[4476]: Stopped Podman wordpress.service.
Apr 9 21:32:00 server2 systemd[4476]: Starting Podman wordpress.service…
Apr 9 21:32:00 server2 systemd[4476]: Created slice cgroup user-libpod_pod_dd7d978770582ccca8c26d10375557c3f2be7666f44d1c9cc9b18ca11ff9e193.slice.
Apr 9 21:32:00 server2 podman[185541]: dd7d978770582ccca8c26d10375557c3f2be7666f44d1c9cc9b18ca11ff9e193
Apr 9 21:32:00 server2 systemd[4476]: Started libcrun container.
Apr 9 21:32:00 server2 podman[185551]: wordpress
Apr 9 21:32:00 server2 systemd[4476]: Started Podman wordpress.service.
Apr 9 21:32:00 server2 systemd[4476]: Starting Podman mariadb-app.service…
Apr 9 21:32:00 server2 systemd[4476]: Started libcrun container.
Apr 9 21:32:00 server2 wordpress2[185588]: 07ec978c7797e7d5642ee59988daeb69e61cad38412345daa5d648df1d943940
Apr 9 21:32:00 server2 mariadb-app[185600]: 2026-04-09 19:32:00+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.16+maria~ubu2204 started.
Apr 9 21:32:00 server2 wordpress2[185637]: #007mysqladmin: connect to server at ‘localhost’ failed
Apr 9 21:32:00 server2 wordpress2[185637]: error: ‘Can’t connect to server on ‘localhost’ (111)’
Apr 9 21:32:00 server2 wordpress2[185637]: Check that mariadbd is running and that the socket: ‘/run/mysqld/mysqld.sock’ exists!
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.16+maria~ubu2204 started.
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] Starting MariaDB 10.11.16-MariaDB-ubu2204 source revision 3218602d3100db9ce7a875511a591cddc173cc16 server_uid 8dWpLEtXSrICWkNY5qMr0An9z+c= as process 1
Apr 9 21:32:01 server2 zabbix-server[8011]: 249:20260409:193201.346 cannot send list of active checks to “169.254.1.2”: host [server2] not found
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Number of transaction pools: 1
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: check seccomp filters, and the kernel version (newer than 5.1 required)
Apr 9 21:32:01 server2 mariadb-app[185600]: create_uring failed: falling back to libaio
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Using Linux native AIO
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: innodb_buffer_pool_size_max=128m, innodb_buffer_pool_size=128m
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Completed initialization of buffer pool
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: End of log at LSN=130626010543
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: 128 rollback segments are active.
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12.000MiB. Physically writing the file full; Please wait …
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12.000MiB.
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: log sequence number 130626010543; transaction id 65295314
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] Plugin ‘FEEDBACK’ is disabled.
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] Server socket created on IP: ‘0.0.0.0’, port: ‘3306’.
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] Server socket created on IP: ‘::’, port: ‘3306’.
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] mariadbd: ready for connections.
Apr 9 21:32:01 server2 mariadb-app[185600]: Version: ‘10.11.16-MariaDB-ubu2204’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 ``mariadb.org`` binary distribution
Apr 9 21:32:01 server2 mariadb-app[185600]: 2026-04-09 19:32:01 0 [Note] InnoDB: Buffer pool(s) load completed at 260409 19:32:01

Apr 9 21:32:02 server2 wordpress2[185637]: mysqld is alive
Apr 9 21:32:02 server2 systemd[4476]: Started Podman mariadb-app.service.
Apr 9 21:32:02 server2 systemd[4476]: Starting Podman wordpress-app.service…

Unfortunately I don’t know where to start on fixing this problem, any pointers are very appreciated!

Wijnand

2

It seems the wordpress app reaches a timeout before mariadb is available.

Is there high load on the server or are you using slow spinning disks?

Does it help to restart the failing wordpress app from the applications page, see Applications — NS8 documentation

Did you already try to restore the failing wordpress instance from backup?

3

Hi Markus,

The NS8 instance is a VM on a proxmox server (thanks to our late Andy!) with shared storage on a nas with 10GB network, this has been a stable solution for me.

Yes, there is a high load on the server now but that is entirely caused by the defunct wordpress module itself. When I stop the module the load goes back to normal.

afbeelding
afbeelding661×168 26.6 KB

Unfortunately I only have backups of the complete VM and not from the module itself (is on the too long to-do list :roll_eyes:) but using that would cause loss of mail, changed files etc. that came in since than. So I rather would like to try to get the module working again.

Could the mariadb part of the module in a way be broken? Maybe I can try to do a restore on file-bases on certain parts of the module? I’m not sure if file ownership can give problems that way.

4

The path to the mariadb data for app instance wordpress1 (replace with the failing wordpress instance) is /home/wordpress1/.local/share/containers/storage/volumes/mysql-data/_data/

Check owner/permissions before to be able to set them for copied files from backup.

5

Update: I have done a file restore on the databasefiles (with the correct ownership of the files) but it made no difference to the situation; the moment that mysqld says its alive the wordpress-app service is started but after a minute or so again stopped due to timeout, and then also the mariadb-app is stopped. I have no clue why.

Is it possible to adjust the timeout time so that mariadb maybe gets a chance to clean things up?

I’m now as a kind of last resort restoring a backup of the Nethserver VM to a new one and planning to copy the complete wordpress module filetree from that to the existing one to see whether that will work.

6

Yes, that’s possible:

7

Final update: adjusting the timeout period did not solve the problem, the module kept restarting, only less frequent.

Therefor I restored the VM from a backup to a separate VM in Proxmox and temporarily added the virtual disk containing the /home partition to the original VM. That way I could copy the wordpress module filetree from the backup over to the de-functional module, and after starting the module the website came alive. A bit of a hassle but in the end it is working again.

Next step: finally get those module backups in place!

@mrmarkuz thanks for the pointers!

1 Like