On Mon, Aug 17, 2020 at 7:50 AM Devine, Harry (FAA) <[email protected]> wrote:
> So late last week I tried to upgrade Guacamole from 1.0.0 to 1.2.0 to see > if that helped. The version on the bottom right of the login page still > says 1.0.0. After I restarted Tomcat, I see the following in > /var/log/messages: > > > > Aug 17 07:42:07 tbfm-access server: 07:42:07.270 [localhost-startStop-1] > ERROR o.a.g.extension.ExtensionModule - Extension > "guacamole-auth-jdbc-mysql-1.2.0.jar" could not be loaded: Extension "MySQL > Authentication" is not compatible with this version of Guacamole. > > Aug 17 07:42:07 tbfm-access server: 07:42:07.274 [localhost-startStop-1] > ERROR o.a.g.extension.ExtensionModule - Extension > "guacamole-auth-ldap-1.2.0.jar" could not be loaded: Extension "LDAP > Authentication" is not compatible with this version of Guacamole. > > Aug 17 07:42:07 tbfm-access server: 07:42:07.282 [localhost-startStop-1] > INFO o.a.g.environment.LocalEnvironment - GUACAMOLE_HOME is > "/usr/share/tomcat/.guacamole". > > > It looks like you got the new extension files in place, but the WAR file (which contains the core of the Guacamole Client) is the old version. You'll need to make sure you update the WAR file, too. > I have an Ansible role that installs Guacamole, and it appears as though > the “upgrade” was only partial. So, my 3 choices are: > > > > 1) How to I make add the missing pieces so this installation is > 1.2.0? > Make sure to update the WAR file. > 2) Do I remove Guacamole completely and re-run the Ansible role to > install as a new installation? If so, how? > This Ansible role is not something that I'm familiar with - it isn't something that is part of the Guacamole project - so I can't help much with that. > 3) Do I just remove the VM completely and recreate it? > This should not be necessary, no - just need to make sure you get all the correct pieces updated, which seems to just be the WAR file at this point. -Nick >
