You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Marco van Zwetselaar (Jira)" <ji...@apache.org> on 2026/07/26 21:55:00 UTC

[jira] [Created] (GUACAMOLE-2309) "log-level: warn" is broken

Marco van Zwetselaar created GUACAMOLE-2309:
-----------------------------------------------

             Summary: "log-level: warn" is broken 
                 Key: GUACAMOLE-2309
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-2309
             Project: Guacamole
          Issue Type: Bug
          Components: guacamole
    Affects Versions: 1.6.0
            Reporter: Marco van Zwetselaar


Setting {{'log-level: warn'}} in {{guacamole.properties}} does not limit logging to {{WARN}} and above. At startup, catalina.out shows that the level is being set:

{{[2026-07-26 21:34:51] [info] 21:34:51.388 [main] INFO org.apache.guacamole.log.LogModule -- Logging will be at the "warning" level.}}

However, these two DEBUG level lines are logged every minute:

{{[2026-07-26 00:45:42] [info] 00:45:42.650 [pool-1-thread-1] DEBUG o.a.g.rest.auth.HashTokenSessionMap - Session check completed in 0 ms.}}
{{[2026-07-26 00:46:42] [info] 00:46:42.650 [pool-1-thread-1] DEBUG o.a.g.rest.auth.HashTokenSessionMap - Checking for expired or invalid sessions...}}

When keeping {{log-level}} unset, or setting it to {{info}} or {{{}error{}}}, these DEBUG lines are not logged. Nor are they logged when I drop a file {{/etc/guacamole/logback.xml}} with {{{}<configuration><root level="warn" /></configuration>{}}}.

This is on Tomcat 10.1.16 on Ubuntu 24.04, in a no-frills installation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)