You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Leslie Mann <lm...@linuxolutions.com> on 2023/11/20 05:21:09 UTC
Guacamole client build failure
I'm trying to build guacamole-client 1.5.3 but the build fails due to a
" SyntaxError: Unexpected end of JSON input" . Same error occurs when
I try building the 1.5.2 client.
Build system is AlmaLinux release 9.3. Am I missing some programs
needed for the build? Build configuration change perhaps?
...
[INFO] <s> [webpack.Progress] 92% chunk asset optimization
[INFO] <s> [webpack.Progress] 92% chunk asset optimization closure-
compiler-plugin
[INFO] undefined:1
[INFO]
[INFO]
[INFO] SyntaxError: Unexpected end of JSON input
[INFO] at JSON.parse (<anonymous>)
[INFO] at ChildProcess.<anonymous> (/home/lmann/dev/guacamole-
client/guacamole/src/main/frontend/node_modules/closure-webpack-
plugin/src/closure-compiler-plugin.js:1007:34)
[INFO] at ChildProcess.emit (node:events:517:28)
[INFO] at maybeClose (node:internal/child_process:1098:16)
[INFO] at Socket.<anonymous> (node:internal/child_process:450:11)
[INFO] at Socket.emit (node:events:517:28)
[INFO] at Pipe.<anonymous> (node:net:350:12)
[INFO]
[INFO] Node.js v18.18.0
[INFO] ----------------------------------------------------------------
--------
[INFO] Reactor Summary for guacamole-client 1.5.3:
[INFO]
[INFO] guacamole-client ................................... SUCCESS [
8.214 s]
[INFO] guacamole-common ................................... SUCCESS [
3.930 s]
[INFO] guacamole-ext ...................................... SUCCESS [
7.587 s]
[INFO] guacamole-common-js ................................ SUCCESS [
6.406 s]
[INFO] guacamole .......................................... FAILURE [
23.544 s]
[INFO] extensions ......................................... SKIPPED
[INFO] guacamole-auth-ban ................................. SKIPPED
...
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-
plugin:1.11.3:npm (npm-build) on project guacamole: Failed to run task:
'npm run build' failed. org.apache.commons.exec.ExecuteException:
Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
Re: Guacamole client build failure
Posted by Leslie Mann <lm...@linuxolutions.com>.
No problem. FYI after setting the selinuxuser_execmod boolean I now
get a clean build!
On Wed, 2023-11-22 at 14:09 -0500, Nick Couchman wrote:
>
>
> On Wed, Nov 22, 2023 at 2:02 PM Leslie Mann <lm...@linuxolutions.com>
> wrote:
> > And here is a workaround
> > from https://github.com/pterodactyl/panel/issues/4410
> >
> >
> > lordofpipes commented Nov 18, 2022
> >
> > For anyone searching this error and looking for a quick and dirty
> > workaround, for RHEL9, AlmaLinux 9, RockyLinux 9, Oracle Linux 9,
> > Amazon Linux, CentOS, Fedora 37, EuroLinux, etc. before the fix is
> > fully released
> >
> > Just run
> >
> > sudo semanage boolean -m --on selinuxuser_execmod
> >
> > to disable the SELinux restriction that causes this segmentation
> > fault.
> >
>
>
> Very interesting - looks like it was introduced after EL8 (in EL9 and
> later, along with the more recent Fedoras), which explains why I
> haven't hit it despite having SELinux enabled.
>
> Thanks for figuring this out and following back up!
>
> -Nick
>
Re: Guacamole client build failure
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Nov 22, 2023 at 2:02 PM Leslie Mann <lm...@linuxolutions.com> wrote:
> And here is a workaround from
> https://github.com/pterodactyl/panel/issues/4410
>
> * lordofpipes commented Nov 18, 2022 *
>
> *For anyone searching this error and looking for a quick and dirty
> workaround, for RHEL9, AlmaLinux 9, RockyLinux 9, Oracle Linux 9, Amazon
> Linux, CentOS, Fedora 37, EuroLinux, etc. before the fix is fully released*
>
> *Just run*
>
> *sudo semanage boolean -m --on selinuxuser_execmod*
>
> *to disable the SELinux restriction that causes this segmentation fault.*
>
Very interesting - looks like it was introduced after EL8 (in EL9 and
later, along with the more recent Fedoras), which explains why I haven't
hit it despite having SELinux enabled.
Thanks for figuring this out and following back up!
-Nick
>
Re: Guacamole client build failure
Posted by Leslie Mann <lm...@linuxolutions.com>.
And here is a workaround
from https://github.com/pterodactyl/panel/issues/4410
lordofpipes commented Nov 18, 2022
For anyone searching this error and looking for a quick and dirty
workaround, for RHEL9, AlmaLinux 9, RockyLinux 9, Oracle Linux 9,
Amazon Linux, CentOS, Fedora 37, EuroLinux, etc. before the fix is
fully released
Just run
sudo semanage boolean -m --on selinuxuser_execmod
to disable the SELinux restriction that causes this segmentation fault.
Works!!
On Wed, 2023-11-22 at 13:56 -0500, Leslie Mann wrote:
> Turns out to be an Selinux issue.
>
> My main system is Fedora 38 and it runs compiler without issue.
> Strace'd and found a permission issue with function mprotect().
>
> $ strace ./compiler
> execve("./compiler", ["./compiler"], 0x7ffd7373a9f0 /* 33 vars */) =
> 0
> open("/proc/self/exe", O_RDONLY) = 3
> mmap(NULL, 69379414, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0) = 0x7f5124fd5000
> mmap(0x7f5124fd5000, 69378989, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x7f5124fd5000
> mprotect(0x7f51291fe000, 5462, PROT_READ|PROT_EXEC) = -1 EACCES
> (Permission denied)
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR,
> si_addr=0x7f51291fed47} ---
> +++ killed by SIGSEGV (core dumped) +++
> Segmentation fault (core dumped)
>
>
> Google leads me to a Redhat bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2132528
>
>
> FYI on Maven 3.6.3, not that this is important now...
>
> $ mvn -version
> Apache Maven 3.6.3 (Red Hat 3.6.3-15)
> Maven home: /usr/share/maven
> Java version: 20.0.2, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-20-openjdk-20.0.2.0.9-1.rolling.el9.x86_64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "5.14.0-362.8.1.el9_3.x86_64", arch:
> "amd64", family: "unix"
> Press any key to continue...
>
>
> On Wed, 2023-11-22 at 13:22 -0500, Nick Couchman wrote:
> > On Wed, Nov 22, 2023 at 12:32 PM Leslie Mann
> > <lm...@linuxolutions.com> wrote:
> > > As I am! I was using a 'minimal' install and have now setup a
> > > full graphical VM with the same results. I can build 1.5.0,
> > > failures start with version 1.5.1...
> > >
> > > What system are you running? I'd like to keep drilling in on
> > > this so I'll setup a new VM with what you are using and see if I
> > > can figure out what's causing the issue.
> > >
> > >
> >
> >
> > EL8 - Rocky8 and CentOS Stream 8, mostly.
> >
> > What versions of Maven and JDK are you using?
> >
> > $ /opt/maven/bin/mvn --version
> > Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> > Maven home: /opt/maven
> > Java version: 11.0.18-ea, vendor: Red Hat, Inc., runtime:
> > /usr/lib/jvm/java-11-openjdk-11.0.18.0.9-0.3.ea.el8.x86_64
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "4.18.0-521.el8.x86_64", arch: "amd64",
> > family: "unix"
> >
> > -Nick
> >
>
Re: Guacamole client build failure
Posted by Leslie Mann <lm...@linuxolutions.com>.
Turns out to be an Selinux issue.
My main system is Fedora 38 and it runs compiler without issue.
Strace'd and found a permission issue with function mprotect().
$ strace ./compiler
execve("./compiler", ["./compiler"], 0x7ffd7373a9f0 /* 33 vars */) = 0
open("/proc/self/exe", O_RDONLY) = 3
mmap(NULL, 69379414, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -
1, 0) = 0x7f5124fd5000
mmap(0x7f5124fd5000, 69378989, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x7f5124fd5000
mprotect(0x7f51291fe000, 5462, PROT_READ|PROT_EXEC) = -1 EACCES
(Permission denied)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR,
si_addr=0x7f51291fed47} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
Google leads me to a Redhat bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2132528
FYI on Maven 3.6.3, not that this is important now...
$ mvn -version
Apache Maven 3.6.3 (Red Hat 3.6.3-15)
Maven home: /usr/share/maven
Java version: 20.0.2, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-20-openjdk-20.0.2.0.9-1.rolling.el9.x86_64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.14.0-362.8.1.el9_3.x86_64", arch:
"amd64", family: "unix"
Press any key to continue...
On Wed, 2023-11-22 at 13:22 -0500, Nick Couchman wrote:
> On Wed, Nov 22, 2023 at 12:32 PM Leslie Mann
> <lm...@linuxolutions.com> wrote:
> > As I am! I was using a 'minimal' install and have now setup a full
> > graphical VM with the same results. I can build 1.5.0, failures
> > start with version 1.5.1...
> >
> > What system are you running? I'd like to keep drilling in on this
> > so I'll setup a new VM with what you are using and see if I can
> > figure out what's causing the issue.
> >
> >
>
>
> EL8 - Rocky8 and CentOS Stream 8, mostly.
>
> What versions of Maven and JDK are you using?
>
> $ /opt/maven/bin/mvn --version
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /opt/maven
> Java version: 11.0.18-ea, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-11-openjdk-11.0.18.0.9-0.3.ea.el8.x86_64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.18.0-521.el8.x86_64", arch: "amd64",
> family: "unix"
>
> -Nick
>
Re: Guacamole client build failure
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Nov 22, 2023 at 12:32 PM Leslie Mann <lm...@linuxolutions.com>
wrote:
> As I am! I was using a 'minimal' install and have now setup a full
> graphical VM with the same results. I can build 1.5.0, failures start with
> version 1.5.1...
>
> What system are you running? I'd like to keep drilling in on this so I'll
> setup a new VM with what you are using and see if I can figure out what's
> causing the issue.
>
>
EL8 - Rocky8 and CentOS Stream 8, mostly.
What versions of Maven and JDK are you using?
$ /opt/maven/bin/mvn --version
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /opt/maven
Java version: 11.0.18-ea, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-11-openjdk-11.0.18.0.9-0.3.ea.el8.x86_64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.18.0-521.el8.x86_64", arch: "amd64", family:
"unix"
-Nick
>
Re: Guacamole client build failure
Posted by Leslie Mann <lm...@linuxolutions.com>.
As I am! I was using a 'minimal' install and have now setup a full
graphical VM with the same results. I can build 1.5.0, failures start
with version 1.5.1...
What system are you running? I'd like to keep drilling in on this so
I'll setup a new VM with what you are using and see if I can figure out
what's causing the issue.
On Tue, 2023-11-21 at 09:58 -0500, Nick Couchman wrote:
> On Mon, Nov 20, 2023 at 11:36 PM Leslie Mann
> <lm...@linuxolutions.com> wrote:
> > Turns out that the native compiler 'compiler' is a UPX packed exe
> > and after unpacking it functions normally. Don't know enough about
> > Maven to figure out how to add an 'unpack' step, nor how to avoid
> > updating NPM package with each Maven run so after resorting to some
> > crude configuration hacks I'm able to successfully compile the
> > client...
> >
> >
>
>
> I'm still curious what about your environment is causing this, as I
> build 1.5.3 and the current code in the git repo on pretty much a
> daily basis, on Intel x86_64-based systems, and I've never run into
> this error, nor have I ever had to do any unpacking or NPM updates in
> order to get the client to build properly.
>
> -Nick
>
Re: Guacamole client build failure
Posted by Nick Couchman <vn...@apache.org>.
On Mon, Nov 20, 2023 at 11:36 PM Leslie Mann <lm...@linuxolutions.com>
wrote:
> Turns out that the native compiler 'compiler' is a UPX packed exe and
> after unpacking it functions normally. Don't know enough about Maven to
> figure out how to add an 'unpack' step, nor how to avoid updating NPM
> package with each Maven run so after resorting to some crude configuration
> hacks I'm able to successfully compile the client...
>
>
I'm still curious what about your environment is causing this, as I build
1.5.3 and the current code in the git repo on pretty much a daily basis, on
Intel x86_64-based systems, and I've never run into this error, nor have I
ever had to do any unpacking or NPM updates in order to get the client to
build properly.
-Nick
>
Re: Guacamole client build failure
Posted by Leslie Mann <lm...@linuxolutions.com>.
Turns out that the native compiler 'compiler' is a UPX packed exe and
after unpacking it functions normally. Don't know enough about Maven
to figure out how to add an 'unpack' step, nor how to avoid updating
NPM package with each Maven run so after resorting to some crude
configuration hacks I'm able to successfully compile the client...
On Mon, 2023-11-20 at 22:00 -0500, Leslie Mann wrote:
> After a bit of digging I see that the closure compiler is using a
> 'native' program, "compiler", which is segfaulting. This results in
> an empty string being passed into JSON.parse()
>
> [INFO] SyntaxError: Unexpected end of JSON input
> [INFO] at JSON.parse (<anonymous>)
> [INFO] at ChildProcess.<anonymous> (/home/lmann/dev/guacamole-
> client/guacamole/src/main/frontend/node_modules/closure-webpack-
> plugin/src/closure-compiler-plugin.js:1007:34)
>
> Looks like the closure compiler can use Java or Javascript instead of
> native
>
> const ClosurePlugin = require('closure-webpack-plugin');
> module.exports = { optimization: { minimizer: [ new
> ClosurePlugin({mode: 'STANDARD'}, { // compiler flags here // // for
> debugging help, try these: // // formatting: 'PRETTY_PRINT' // debug:
> true, // renaming: false }) ] }
> };
>
> Options *
> platform - native, java or javascript. Controls which version to use
> of closure-compiler. By default the plugin will attempt to
> automatically choose the fastest option available.
> JAVASCRIPT does not require the JVM to be installed. Not all flags
> are supported.
> JAVA utilizes the jvm. Utilizes multiple threads for parsing and
> results in faster compilation for large builds.
> NATIVE only available on linux or MacOS. Faster compilation times
> without requiring a JVM.
>
> but I can't get either JAVA or JAVASCRIPT to work, for example:
>
> // Minify using Google Closure Compiler
> new ClosureWebpackPlugin({ mode: 'STANDARD'}, { platform: 'JAVA'}, {
>
> Anyone have suggestions on how to force the use of a Java compiler??
>
>
>
> On Mon, 2023-11-20 at 07:51 -0500, Leslie Mann wrote:
> > I'm building on x86_64 GNU/Linux:
> > Almalinux9 (binary compatible with RHEL)
> >
> > $ java -version
> > openjdk version "20.0.2" 2023-07-18
> > OpenJDK Runtime Environment (Red_Hat-20.0.2.0.9-1.rolling.el9)
> > (build 20.0.2+9)
> > OpenJDK 64-Bit Server VM (Red_Hat-20.0.2.0.9-1.rolling.el9) (build
> > 20.0.2+9, mixed mode, sharing)
> >
> > javac -version
> > javac 20.0.2
> >
> > $mvn -v
> > Apache Maven 3.6.3 (Red Hat 3.6.3-15)
> > Maven home: /usr/share/maven
> > Java version: 20.0.2, vendor: Red Hat, Inc., runtime:
> > /usr/lib/jvm/java-20-openjdk-20.0.2.0.9-1.rolling.el9.x86_64
> > Default locale: en, platform encoding: UTF-8
> > OS name: "linux", version: "5.14.0-362.8.1.el9_3.x86_64", arch:
> > "amd64", family: "unix"
> >
> >
> >
> > On Sun, 2023-11-19 at 21:27 -0800, Michael Jumper wrote:
> > > On 11/19/23 21:21, Leslie Mann wrote:
> > > > I'm trying to build guacamole-client 1.5.3 but the build fails
> > > > due to a
> > > > " SyntaxError: Unexpected end of JSON input" . Same error
> > > > occurs when I
> > > > try building the 1.5.2 client.
> > > >
> > > > Build system is AlmaLinux release 9.3. Am I missing some
> > > > programs
> > > > needed for the build? Build configuration change perhaps?
> > > >
> > >
> > > What architecture are you building on? IIRC, closure compiler has
> > > no ARM
> > > version available. The closure compiler webpack plugin might not
> > > be
> > > handling that kind of failure well.
> > >
> > > - Mike
> > >
> > > -----------------------------------------------------------------
> > > ----
> > > To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> > > For additional commands, e-mail: user-help@guacamole.apache.org
> > >
> >
>
Re: Guacamole client build failure
Posted by Leslie Mann <lm...@linuxolutions.com>.
After a bit of digging I see that the closure compiler is using a
'native' program, "compiler", which is segfaulting. This results in
an empty string being passed into JSON.parse()
[INFO] SyntaxError: Unexpected end of JSON input
[INFO] at JSON.parse (<anonymous>)
[INFO] at ChildProcess.<anonymous> (/home/lmann/dev/guacamole-
client/guacamole/src/main/frontend/node_modules/closure-webpack-
plugin/src/closure-compiler-plugin.js:1007:34)
Looks like the closure compiler can use Java or Javascript instead of
native
const ClosurePlugin = require('closure-webpack-plugin'); module.exports = { optimization: { minimizer: [ new ClosurePlugin({mode: 'STANDARD'}, { // compiler flags here // // for debugging help, try these: // // formatting: 'PRETTY_PRINT' // debug: true, // renaming: false }) ] }
};
Options
*
platform - native, java or javascript. Controls which version to use
of closure-compiler.
By default the plugin will attempt to automatically choose the
fastest option available.
JAVASCRIPT does not require the JVM to be installed. Not all flags
are supported.
JAVA utilizes the jvm. Utilizes multiple threads for parsing and
results in faster compilation for large builds.
NATIVE only available on linux or MacOS. Faster compilation times
without requiring a JVM.
but I can't get either JAVA or JAVASCRIPT to work, for example:
// Minify using Google Closure Compiler
new ClosureWebpackPlugin({ mode: 'STANDARD'}, { platform: 'JAVA'}, {
Anyone have suggestions on how to force the use of a Java compiler??
On Mon, 2023-11-20 at 07:51 -0500, Leslie Mann wrote:
> I'm building on x86_64 GNU/Linux:
> Almalinux9 (binary compatible with RHEL)
>
> $ java -version
> openjdk version "20.0.2" 2023-07-18
> OpenJDK Runtime Environment (Red_Hat-20.0.2.0.9-1.rolling.el9) (build
> 20.0.2+9)
> OpenJDK 64-Bit Server VM (Red_Hat-20.0.2.0.9-1.rolling.el9) (build
> 20.0.2+9, mixed mode, sharing)
>
> javac -version
> javac 20.0.2
>
> $mvn -v
> Apache Maven 3.6.3 (Red Hat 3.6.3-15)
> Maven home: /usr/share/maven
> Java version: 20.0.2, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-20-openjdk-20.0.2.0.9-1.rolling.el9.x86_64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "5.14.0-362.8.1.el9_3.x86_64", arch:
> "amd64", family: "unix"
>
>
>
> On Sun, 2023-11-19 at 21:27 -0800, Michael Jumper wrote:
> > On 11/19/23 21:21, Leslie Mann wrote:
> > > I'm trying to build guacamole-client 1.5.3 but the build fails
> > > due to a
> > > " SyntaxError: Unexpected end of JSON input" . Same error occurs
> > > when I
> > > try building the 1.5.2 client.
> > >
> > > Build system is AlmaLinux release 9.3. Am I missing some
> > > programs
> > > needed for the build? Build configuration change perhaps?
> > >
> >
> > What architecture are you building on? IIRC, closure compiler has
> > no ARM
> > version available. The closure compiler webpack plugin might not be
> > handling that kind of failure well.
> >
> > - Mike
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> > For additional commands, e-mail: user-help@guacamole.apache.org
> >
>
Re: Guacamole client build failure
Posted by Leslie Mann <lm...@linuxolutions.com>.
I'm building on x86_64 GNU/Linux:
Almalinux9 (binary compatible with RHEL)
$ java -version
openjdk version "20.0.2" 2023-07-18
OpenJDK Runtime Environment (Red_Hat-20.0.2.0.9-1.rolling.el9) (build
20.0.2+9)
OpenJDK 64-Bit Server VM (Red_Hat-20.0.2.0.9-1.rolling.el9) (build
20.0.2+9, mixed mode, sharing)
javac -version
javac 20.0.2
$mvn -v
Apache Maven 3.6.3 (Red Hat 3.6.3-15)
Maven home: /usr/share/maven
Java version: 20.0.2, vendor: Red Hat, Inc., runtime:
/usr/lib/jvm/java-20-openjdk-20.0.2.0.9-1.rolling.el9.x86_64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.14.0-362.8.1.el9_3.x86_64", arch:
"amd64", family: "unix"
On Sun, 2023-11-19 at 21:27 -0800, Michael Jumper wrote:
> On 11/19/23 21:21, Leslie Mann wrote:
> > I'm trying to build guacamole-client 1.5.3 but the build fails due
> > to a
> > " SyntaxError: Unexpected end of JSON input" . Same error occurs
> > when I
> > try building the 1.5.2 client.
> >
> > Build system is AlmaLinux release 9.3. Am I missing some programs
> > needed for the build? Build configuration change perhaps?
> >
>
> What architecture are you building on? IIRC, closure compiler has no
> ARM
> version available. The closure compiler webpack plugin might not be
> handling that kind of failure well.
>
> - Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
>
Re: Guacamole client build failure
Posted by Michael Jumper <mj...@apache.org>.
On 11/19/23 21:21, Leslie Mann wrote:
> I'm trying to build guacamole-client 1.5.3 but the build fails due to a
> " SyntaxError: Unexpected end of JSON input" . Same error occurs when I
> try building the 1.5.2 client.
>
> Build system is AlmaLinux release 9.3. Am I missing some programs
> needed for the build? Build configuration change perhaps?
>
What architecture are you building on? IIRC, closure compiler has no ARM
version available. The closure compiler webpack plugin might not be
handling that kind of failure well.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org