From b2b5d799e5439a6f9e74378e2ecc888439889446 Mon Sep 17 00:00:00 2001 From: Vladimir Babin Date: Sat, 19 Sep 2026 12:21:38 +0300 Subject: [PATCH] fix(admin): use an absolute path in the file logging example The example set logfile to a bare "nextcloud.log", which is resolved relative to the installation directory rather than the data directory. A log file created there makes the updater's expected-files check fail. Use an absolute path in the example and note that the parameter is optional and defaults to nextcloud.log inside datadirectory. Signed-off-by: Vladimir Babin --- .../configuration_server/logging_configuration.rst | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/admin_manual/configuration_server/logging_configuration.rst b/admin_manual/configuration_server/logging_configuration.rst index ab0842739c7..31fc3be41b3 100644 --- a/admin_manual/configuration_server/logging_configuration.rst +++ b/admin_manual/configuration_server/logging_configuration.rst @@ -54,10 +54,15 @@ date format in the example below, the date/time format will be written in the fo :: "log_type" => "file", - "logfile" => "nextcloud.log", + "logfile" => "/var/log/nextcloud/nextcloud.log", "loglevel" => 3, "logdateformat" => "F d, Y H:i:s", +The **logfile** parameter is optional. If it is omitted, the log is written to **nextcloud.log** in the +**datadirectory**. When setting it, use an absolute path: a relative path such as ``"nextcloud.log"`` is resolved +against the working directory of the PHP process (usually the Nextcloud installation directory), and a log file +placed there makes the updater's check for expected files fail. + Additional file-based logging parameters ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^