Thank you for the suggestion, Jan. The Groovy Console command returned the correct directory. The issue ended up being due to the use of a symlink in the logging path listed in magnolia.properties.
In the course of upgrading to 4.4.11-jr24, we created a "current" deployment symlink, which points to the currently active copy of Magnolia. (e.g., <application_name>/deployments/current points to <application_name>/deployments/magnolia-enterprise-4.4.11-jr24-20130531.) In turn, we configured daemon tools and magnolia.properties to use files located in the "current" directory. The LogViewerPage code [1] calls the function isValidPath(), which compares the value of magnolia.logs.dir with the value of the getCanonicalPath() function. [2] Either getCanonicalPath() is throwing an error because the canonical pathname requires filesystem queries due to the symlinks, or it's returning the actual path to the logs exclusive of any symlinks, which doesn't match the value of magnolia.logs.dir. I created a folder called <application_name>/logs, copied the existing logs into this folder, and modified the magnolia.properties file to log to this new location. After these changes, log viewing worked normally. tl;dr: The path to your logs folder cannot include a symlink. [1] http://nexus.magnolia-cms.com/content/sites/magnolia.public.sites/ref/4.4.11-SNAPSHOT/magnolia-module-admininterface/xref/info/magnolia/module/admininterface/pages/LogViewerPage.html [2] http://docs.oracle.com/javase/6/docs/api/java/io/File.html#getCanonicalPath() -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=1430e982-7abd-4d4a-88ca-3be02b178c11 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
