On Mon, Jan 20, 2020 at 12:44 PM Newman, Dennis <[email protected]> wrote:
> No other messages when guacd started > > Connecting to the website as guacadmin gives me the full user and system > config pages – but attempting to connect to any remote desktop times out > > Forgive my ignorance, but where would I read the guacd log? I don’t see > any logs by that name. > guacd logs to syslog. On CentOS, this will likely be the systemd journal, which you would access using the "journalctl" command. My suspicion is that upgrades were indeed applied, and that the RDP support cannot be loaded when connection attempts are made because it was built against an older version of FreeRDP. CentOS 7 recently switched their FreeRDP packages over to FreeRDP 2.0.0-rc4, which is not compatible with software built against an older version. Up until recently, guacamole-server also could not be built against FreeRDP 2.0.0 as the API is entirely different. If this is the case, and you find the guacd logs, you should see a message nothing that support for RDP could not be found, and you will need to do one of the following: 1) Revert the upgrade, bringing back the older version of the freerdp package OR: 2) Install the freerdp1.2-devel package from EPEL, which Fedora has provided as a stopgap for those that need an older FreeRDP, and rebuild guacamole-server. It will not work as-is, as this version of FreeRDP is also incompatible, but it is supported by guacamole-server 1.0.0 and older. ... OR: 3) Try building the "staging/1.1.0" branch of guacamole-server, as we recently added support for FreeRDP 2.0.0 while also dropping support for older versions of the library. ... OR: 4) Stop the local guacd service and use the "guacamole/guacd" Docker image instead. If you're in a time crunch to get things back up, I'd recommend trying the Docker approach for now. - Mike
