Mike Jumper wrote > On Sat, Sep 9, 2017 at 12:28 PM, vnick < > vnick@
> > wrote: >> EricSten wrote >>> ... >>> guacd[51911]: INFO: Creating new client for protocol "rdp" >>> guacd[51911]: INFO: Connection ID is >>> "$425c3cfe-029f-4465-b2fa-059d51f253b8" >>> guacd[51911]: INFO: Connection >>> "$425c3cfe-029f-4465-b2fa-059d51f253b8" >>> removed. >>> ... >> >> If I get a chance I'll try to spin up a FreeBSD VM and see if I can >> replicate it or if I can get it to work. >> > > Assuming that you succeed in reproducing this, it may help to run > guacd under gdb. Normally, when a connection terminates, even > unsuccessfully, there will be at least two log messages: one from the > protocol-specific plugin noting that the client has closed, and > another from guacd noting that it has cleaned up after the connection. > As only the latter is present here, that suggests that something might > be causing the connection's child process to crash completely. > > - Mike Eric, Well, I have good news and bad news. I was unable to reproduce the failure you're seeing. (That's both the good and bad, by the way.) I built a FreeBSD 10.3 virtual machine (64-bit) and installed all of the required packages on it to get it up and running. This included installing several development packages so that I could compile the guacd component with RDP and SSH support. I tested out both the latest git master branch and the 0.9.13-incubating version. My process was something like this: - Install FreeBSD 10.3 into Intel 64-bit VM - Install a few support packages (git, wget, bash, pkg, etc.) - Install Tomcat8 and PostgreSQL - Checkout the latest git master of Guacamole client and server - Build and install server (took some tweaking to get the build to work, and had to install several required packages) - Build client, copy JDBC PostgreSQL authentication extension to /etc/guacamole/extensions and configure guacamole.properties. - Load Guacamole PostgreSQL schema into new database. - Load guacamole WAR file into Tomcat - Go to Guacamole page, log in, and configure two connections - one RDP and one SSH. - Test connections - both worked fine. - Remove all of those Guacamole components from the system. - Download the Guacamole server source, build, (tweak a few things) and install. - Download the pre-built Guacamole client files, including the JDBC extensions and the WAR file - Deploy pre-built client files into Tomcat, log in, test connections - both RDP and SSH work fine. - Remove JDBC support, configure user-mapping.xml, and test connections that way - both RDP and SSH work fine. So, it seems like there's something about your FreeBSD setup that's at least slightly different from my quick-and-dirty test. I don't know if it's some sort of Mandatory Access Control system, application firewall, or what, but something is causing guacd on your system to drop the connection immediately. Can you confirm when you compiled guacd (guacamole server) that the end of your configure script showed something like this: In particular, that, under Protocol Support, you see "yes" for the protocols you're trying to use? As I alluded to before, it took me some tweaking to actually get the guacd compile to run correctly and recognize all of the libraries - I'm curious if maybe you ended up with a guacd instance that supports no protocols, or at least doesn't support RDP and SSH? -Nick -- Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
