Updating the file server’s OS files #

Each file server container automatically pulls catalog updates every 6 hours, so under normal operation you do not need to do anything. Run a manual update only if you want changes sooner — for example right after a new ISO has been added to the catalog and you don’t want to wait for the next 6-hour tick.

Make sure the file server has enough disk space for the OS files. The full catalog is around 9 GB as of 2026. The updater checks free space before each download and skips entries that wouldn’t fit.

Automatic updates #

Inside each file server container, a supervised loop runs update-pxe-files.sh six hours after the container starts and every sixhours thereafter. The loop writes its own log to /scp/app/logs/pxe-updater.log inside the container, which can be used to check and ensure the updates are running.

If on SynergyCP 5.3.0 or newer, the app will also show you the last time the files were updated, as part of the health check section.

The automatic update will update the files that SynergyCP provides under /scp/pxe/file/srv/. Any files you put into SynergyCP-provided directories for OS profile kernels and initrds and such will be overwritten by the automatic updater. To avoid this if e.g. you have your own OS reload profiles with different kernels/initrds etc, please place these into a different directory.

Triggering a manual update #

Run as the root user on the file server:

curl -fsSL https://install.synergycp.com/bm/update-pxe-files.sh | bash

The script prints a per-file status table and a final summary like Updated: N | Skipped: M | Errors: 0.

Optional flags #

To pass flags through the pipe, use bash -s --:

curl -fsSL https://install.synergycp.com/bm/update-pxe-files.sh | bash -s -- --dry-run

Child file servers #

If you have any child file servers, sync the changes to them using the Sync Files to Children button on the master file server’s edit page under OS Reloads → Deploy File Servers.