[
https://issues.apache.org/jira/browse/GUACAMOLE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891129#comment-16891129
]
Nick Couchman commented on GUACAMOLE-854:
-----------------------------------------
This is expected behavior - it was added in a recent change (GUACAMOLE-422,
https://github.com/apache/guacamole-server/pull/219). I suppose we could make
that a TRACE-level message instead of DEBUG - [~mike.jumper], thoughts?
> Debug level guacd logs spammed with "Handler not found for"
> -----------------------------------------------------------
>
> Key: GUACAMOLE-854
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-854
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 1.1.0
> Environment: guacd: staging/1.1.0
> guacamole-common-js: staging/1.1.0
> Reporter: Richard Lancaster
> Priority: Minor
>
> When running guacd with DEBUG level logs, the logs are spammed with:
> {noformat}
> guacd[9]: DEBUG: Handler not found for "nop"
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for "nop"
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> guacd[9]: DEBUG: Handler not found for ""
> {noformat}
> I think the empty strings are caused by these instructions:
> `0.,4.ping,13.1563882935963`.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
