#1999 Prosody is no longer logging to file

Reporter mopp
Owner Nobody
Created
Updated
Stars ★ (1)
Tags
  • Status-New
  • Priority-Medium
  • Type-Defect
  1. mopp on

    What steps will reproduce the problem? 1. Have info logging and error logging enabled into two different files, as described in https://prosody.im/doc/logging. This has been going for years, I've never changed this. 2. Upgrade to current trunk on June 27th 2026 (build 2085 (2026-06-13, ce31fdde0ad1)), the update before that was on May 16th 2026, also trunk. 3. The info log file is no longer updated, watch:logs() and journalctl are still displaying logs What is the expected output? Prosody continues logging to file, e.g. I should be able to the the startup messages from the recent restart after upgrading- What do you see instead? Log files are no longer updated, watch:logs() and journalctl are still displaying logs What version of the product are you using? On what operating system? Debian 12, build 2085 (2026-06-13, ce31fdde0ad1) Please provide any additional information below. The last log messages in the info log are from when prosody shutdown before restarting after the upgrade to build 2085. I had a look at the commit messages from May to now but didn't catch anything obvious related to this.

New comment

Not published. Used for spam prevention and optional update notifications.