[jira] [Closed] (GUACAMOLE-1712) tuneD profile causes Guacamole connection issues

["Chris F (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris F closed GUACAMOLE-1712.
------------------------------
    Resolution: Not A Problem

> tuneD profile causes Guacamole connection issues
> ------------------------------------------------
>
>                 Key: GUACAMOLE-1712
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1712
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacd-docker
>    Affects Versions: 1.4.0
>         Environment: RHEL 8
>            Reporter: Chris F
>            Priority: Minor
>
> Guacamole connection is failing when starting tuneD service with command "systemctl start tuned" when tuneD config has a profile config set. After restarting guac-pod, guac connection will fail again after a few minutes if tuneD is enabled. 
> When tuned.conf file contains any one of these lines, starting the tuned service results in the guac connection failure. 
>  
> {code:java}
> [main]
> summary=Optimize for deterministic performance at the cost of increased power consumption, focused on low latency network performance
> include=latency-performance
> [sysctl]
> net.core.busy_read=50
> net.core.busy_poll=50
> net.ipv4.tcp_fastopen=3
> kernel.numa_balancing=0 {code}
> Tried using a few different default profiles provided in the tuneD documentation, result was the same.
> tuneD version: tuned-2.15.0-2.el8_4.1.noarch.rpm
> link to tuneD docs: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/monitoring_and_managing_system_status_and_performance/getting-started-with-tuned_monitoring-and-managing-system-status-and-performance



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