Disk, logs and housekeeping
Each server keeps what it hosts under /srv. One nightly job removes most of what grows there,
on every server. This page says where the space goes, where to read the logs, what that job
removes, how much memory MariaDB takes, and how the firewall is set up.
Find where disk goes
Section titled “Find where disk goes”| Path | Holds |
|---|---|
/srv/sites/<slug> |
A site’s files, the files a restore set aside, and its quarantine |
/srv/mysql |
Every database on the server |
/srv/backups |
Backups, unless the server’s backup location is elsewhere |
/srv/plugins |
The plugin catalog’s zips |
/srv/traefik |
Certificates |
/srv/mail |
The mail relay’s settings and DKIM keys |
/srv/panel |
The panel’s database and SSH key, on the panel’s server only |
Disk on a server’s page and on a site’s Overview tab is the site’s folder under
/srv/sites. Its database is not counted. To see the whole picture, run these in the
Terminal:
df -h /srvsudo du -sh /srv/*Docker keeps its images, its build cache and the containers’ logs in /var/lib/docker, outside
/srv. Each site’s page cache is there too, about 256 MB at most, and so are
request bodies while they arrive. Every start of a container empties its page cache. This shows what
each takes:
sudo docker system dfBackups usually grow fastest. Keep fewer of them locally and more offsite, or give them a disk of their own under Backup storage.
Read the logs
Section titled “Read the logs”Every part of the stack is a Docker container. Read a container’s log in the Terminal:
sudo docker logs --tail 100 wp-northwind-bakery| Container | What its log says |
|---|---|
wpl7-panel |
The panel and its jobs, on the panel’s server only |
wpl7-traefik |
Routing and certificates |
wpl7-mariadb |
The database server |
wpl7-mail |
Mail delivery and the queue, also shown under Mail → Traffic |
wpl7-dkim |
DKIM signing |
wp-<slug> |
A site’s nginx, Apache, PHP and Redis errors |
wpl7-ftp |
FTP and SFTP logins and transfers, on servers with FTP logins |
Docker rotates these logs and keeps three files of 10 MB per container. The panel’s own work is in each job’s log, under Jobs.
The system journal holds the logs of SSH, the firewall and Docker itself. setup.sh limits it to
500 MB, and has apt empty its package cache once a week. To keep more of the journal, add a file
that sorts after /etc/systemd/journald.conf.d/wpl7.conf, such as zz-local.conf.
What the nightly housekeeping removes
Section titled “What the nightly housekeeping removes”The Nightly housekeeping schedule starts at 04:00 on the panel’s clock. Under Automations → Schedules you can choose Run now, or pause it. While it is paused, nothing in this table is removed, and disks keep growing.
| What | How much is kept | Where to change it |
|---|---|---|
| Scheduled backups and panel snapshots | The newest 10 per site | Keep last N scheduled backups per site in Settings → Backups |
| Backups older than the keep period, but for manual and final ones and each site’s newest | Every one, until you set a number of days | Delete site backups after (days) and Delete panel backups after (days) in Settings → Backups, and Delete backups after on a site’s Backups tab |
| Offsite copies of those two kinds | The newest 30 per site, at each destination | The destination’s Keep last N scheduled per site |
| Files a restore set aside | At least a day | |
| A moved site’s old copy | Until its hostnames point only at the new server, and at least a day | Finalize now on the site’s page |
| Resource samples | 7 days | |
| Mail traffic | 30 days | Keep traffic history for (days) in Settings → Mail |
| Visitor statistics, and visitor addresses | 90 days, and 7 days | Settings → Monitoring |
| The API request log | 30 days | Keep requests for on the API keys’ Activity tab |
| Malware scan history | The last 100 scans per site, and a year of resolved findings | |
| Quarantined files | Until someone deletes them | Keep quarantined files (days) in Settings → Security |
| Finished jobs | 90 days | Finished jobs are kept for, below the job list |
| Docker images no container uses | Those the panel still needs: a site image for each PHP version, and the newest panel image besides the running one | |
| Docker’s build cache | 1 GiB of what no image shares |
The same job refreshes the vulnerability data for what your sites run. Once a week it also refreshes the country lookup data and the address lists Cloudflare, Jetpack and the AI companies publish.
Set MariaDB’s memory
Section titled “Set MariaDB’s memory”MariaDB keeps data and indexes in its buffer pool. MARIADB_POOL_SIZE in deploy/.env sets its
size. auto, the default, is an eighth of the server’s memory, from 256 MB to 4 GB, worked out at
every start, so it follows a resized server. Any other value, such as 2G, is used as it is. Run
setup.sh after you change it, which restarts MariaDB.
How the firewall is set up
Section titled “How the firewall is set up”setup.sh turns on UFW. It refuses every incoming connection except SSH, 80 and 443, and it limits
how quickly SSH connections may be opened. It also allows UDP on 443, for HTTP/3. Ports that Docker
publishes go past UFW. Only two containers publish any: Traefik on 80 and 443, and the FTP gateway
once a site on that server has an FTP login. A cloud firewall in front of the server has to allow
the FTP ports set under FTP & SFTP in Settings. It also has to allow UDP 443, or browsers
stay on HTTP/2.
Blocked addresses have an nftables table of their own,
inet wpl7. It drops connections to 80 and 443, and UDP packets to 443, from a blocked address
before Docker forwards them, and leaves UFW’s and Docker’s rules alone. The wpl7-firewall helper controls it on each
server. This command prints what is loaded, as one line of JSON:
sudo wpl7-firewall statusThis one empties the table and keeps it empty, whatever the panel sends, until you run
sudo wpl7-firewall on:
sudo wpl7-firewall offA systemd unit of its own loads the last list at boot. Leave nftables.service disabled: its
default configuration starts by deleting every rule, Docker’s and UFW’s included.
Limits
Section titled “Limits”- A site’s disk figure counts its files, not its database. Databases shows the databases’ sizes.
- A backup needs free disk of one and a half times the site’s size. With less, it fails.
- Docker publishes its ports past UFW. A UFW rule does not close 80, 443 or the FTP ports.
- The FTP ports are published on IPv4 only.
- Housekeeping runs once a night. During the day, the panel only emails you when a server has less than 10% of its disk free.
- Docker images under names of your own are left alone, used or not. A container app’s images are its deploys’ to clear: each keeps the image it runs and the two before it. On a server that builds its own site images, a WordPress base image a newer pull left without a name goes too.
- While an update of the panel runs, the panel’s server keeps its unused images until the next night.
- The panel shows no container logs. Read them in the Terminal.