If you are self-hosting and used to reviewing your logs via the systems journal, after upgrading to 5.109.3, you may find they are no longer there.
Before this release, Ghost logged both to a file and to STDOUT, which goes to the systemd journal if you were running Ghost as a systemd service. If you were running Ghost in a container, this may or may not affect your ability to find your logs.
Restoring logging to STDOUT is easy. Find your config.production.json and add stdout back to the logging.transports section:
If you are running Ghost in a container, you may need to set a related config variable.
Also, if you are certain you are not using the feature to log to a file, you can disable that logging method at the same time. Generally, apps don’t need to log to two locations like this, so the Ghost team made the change. Extra, unnecessary logging impacts performance.
Related change on Github: Removed stdout from logging by rmgpinto · Pull Request #22126 · TryGhost/Ghost · GitHub