After upgrading Confluence, Tomcat logs are no longer written on Confluence Installation folder
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Confluence was upgraded from version 6.15.X or earlier to version 7.0.5 or greater on Windows.
After the upgrade, there aren't new log messages being written on the <confluence_install>/logs folder (see Confluence Home and other important directories)
The Windows service was correctly reinstalled according to the mandatory post-upgrade step on Upgrading Confluence.
Environment
- Confluence Server or Data Center 7.0.5 or greater (upgraded from 6.15.X or lower)
- Windows Operating System
- Confluence is running as a service
Diagnosis
- Check the last created/modified date on the catalina.log files. The last message was written prior to the upgrade.
- The application logs, on Confluence Home, are being written as expected.
Cause
After the security fix developed on CONFSERVER-58808 - Getting issue details... STATUS , Confluence service was modified to run as a Network Service, as opposed to a Local System account. This new user, responsible for running the Confluence service, doesn't have write permissions over the Confluence Install directory.
Solution
Solution 1 - Granting permissions
- Check the user set to run the Confluence Service
- Grant write permissions to that user over the Confluence Install directory
Solution 2 - Using a dedicated account
- Create a dedicated account to run Confluence service on Windows
- Modify the Confluence service parameters to use the newly created account