[ https://issues.apache.org/jira/browse/GUACAMOLE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891140#comment-16891140 ]
Richard Lancaster commented on GUACAMOLE-854: --------------------------------------------- I would expect logging of unexpected instructions, but these instructions originated from guacamole-common-js client. Personally I would give them a null handler if it's intended for them to be received but not have a side-effect. > 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)