Hello Mike:

That's what I originally did, then had no guacadmin user login (which is a 
problem I see a ton of people having), then Nick Couchman had me install 
Postgresql, and that turned out to be a big nightmare...Originally, I tried 
1.0.0, but it had some sort of known issue that isn't being fixed until 1.10.0, 
so I went back to 0.9.14...I can start over, but am afraid I would end up like 
I did yesterday - i.e. basically no admin GUI, editing XML files, etc., before 
I blew that away. The instructions need improvement - especially chapters 5 and 
6. In chapter 5, for example, it says "GUACAMOLE_HOME is the name given to 
Guacamole's configuration directory, which is located at /etc/guacamole by 
default." - that directory does not exist if you follow the chapter 2 
instructions. In chapter 6, I did not know that knowing how to install and 
configure a SQL server was a prerequesite for installing Guacamole. That is a 
bit more difficult than the Guacamole installation itself, and could use some 
explanation (at least minimal explanation). The guy in the link I sent does 
MySQL in about 7 steps. So what I might try to 0.9.14 under CentOS 7, built 
from source with the instructions that other guy gave for MySQL, since that 
part of it seems to be working. To make things even more difficult for me here, 
I have to go through a squid proxy server, which means custom settings for ftp, 
yum, wget, maven, and several other things just to complete the task. 
Originally, to get the machine going yesterday, I had to configure an identical 
system at home using yum --downloadonly to get the files, then bring them in on 
a USB key.

Lance

From: Mike Jumper <[email protected]>
Sent: Tuesday, April 30, 2019 4:12 PM
To: [email protected]
Subject: Re: RDP


[ CAUTION ]

This email originated outside Deluxe.



On Tue, Apr 30, 2019, 16:01 Lance Gropper 
<[email protected]<mailto:[email protected]>> 
wrote:
Hello Mike:

I followed these instructions - this is a clean install:

https://deviant.engineer/2016/11/guacamole-incubator-centos7/<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeviant.engineer%2F2016%2F11%2Fguacamole-incubator-centos7%2F&data=02%7C01%7CLance.Gropper%40encorehollywood.com%7Cea0923785df74ffc482008d6cdc146b2%7C8688c7c41f2a4115a918361023dde469%7C1%7C0%7C636922627350310776&sdata=m542wWnH%2FTNmLEK3gFIAVQjLxqgZiAzXWncTqIPdvBc%3D&reserved=0>

Somehow, all of the libraries appear to be 1.0.0:

[root@guacamole-post etc]# rpm -qa | grep uac
libguac-client-ssh-1.0.0-1.el7.x86_64
libguac-client-vnc-1.0.0-1.el7.x86_64
libguac-client-rdp-1.0.0-1.el7.x86_64
libguac-1.0.0-1.el7.x86_64

Yikes.

The instructions linked above are incorrect. You shouldn't be installing 
libguac, etc. from RPMs and then also building guacamole-server from source. 
The libguac and libguac-client-* libraries are part of guacamole-server and 
will now be mismatched, with different versions of structures being expected by 
different components.

You should remove the versions installed via RPMs or remove the version built 
from source. Ideally, remove everything, pick one (your distro's RPMs or the 
source) and install that. If you're in a position where you can blow everything 
away and start over, that would be better.

Official instructions for install+build are in the manual:

http://guacamole.apache.org/doc/gug/installing-guacamole.html<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fguacamole.apache.org%2Fdoc%2Fgug%2Finstalling-guacamole.html&data=02%7C01%7CLance.Gropper%40encorehollywood.com%7Cea0923785df74ffc482008d6cdc146b2%7C8688c7c41f2a4115a918361023dde469%7C1%7C0%7C636922627350320781&sdata=0woahy5Oi5XEUUnWhzzS4vva2pCZeNqGnFKjSXCT2oo%3D&reserved=0>

If you choose to go with your distribution's packages, don't also build from 
source. If your distribution provides libguac and libguac-client-*, it should 
also provide a guacd package.

- Mike




[ CAUTION ]

DO NOT open attachments or click links from unknown senders. Only respond if 
you can validate the senders legitimacy.




This e-mail and any attachments are intended only for use by the addressee(s) 
named herein and may contain confidential information. If you are not the 
intended recipient of this e-mail, you are hereby notified any dissemination, 
distribution or copying of this email and any attachments is strictly 
prohibited. If you receive this email in error, please immediately notify the 
sender by return email and permanently delete the original, any copy and any 
printout thereof. The integrity and security of e-mail cannot be guaranteed.

Reply via email to