You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by "Newman, Dennis" <de...@spglobal.com> on 2020/01/20 20:17:25 UTC
Guacamole Stopped - guacd = Unable to bind socket to any addresses.
Guacamole 1.0.0 installed on CentOs7 with Tomcat
Installed as a VmWare Guest and granting Windows remote desktop sessions to almost 100 Windows virtual systems.
Everything has been running perfectly for almost 6 months - No issues at all.
Sometime over the weekend - something seems to have changed.
This morning the gateway seemed unreachable - I was remote myself, so I re-booted the Guacamole system.
At that time, it "may" have done some Linux updates - not sure.
Now the Guacamole Gateway is reachable - but nobody can connect to their RDP sessions.
Killed guacd
Restarted guacd - get
Guacamole proxy daemon (guacd) version 1.0.0 started
But still cannot connect to any remote desktop sessions
I'm a Novell and Windows "expert" honestly to get this running I just followed the directions.
I'm at a loss as to where to look to find what is wrong.
ANY assistance pointing me where to look would be appreciated.
This system was tested and running - Now I have users who cannot connect to do their work
Thanks in advance
Dennis Newman
Senior Infrastructure Engineer | Wisconsin office
RateWatch + S&P Global Market Intelligence
201 N. Main Street, Suite 4
Fort Atkinson, WI 53538
T: 920.568.1401 x4300
C: +1.920.397.1344
S&P ext 2684300
Dennis.newman@spglobal.com<ma...@spglobal.com>
[rtwtchspg_mrkt_vt_emailSign_RGB_pos]
________________________________
The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.
RE: Guacamole Stopped - guacd = Unable to bind socket to any
addresses.
Posted by "Newman, Dennis" <de...@spglobal.com>.
Mike – ok Messages log Probably clipped more than is needed but –
Jan 20 18:06:57 remote guacd: guacd[1534]: INFO:#011Connection "$fb796c29-6626-4445-a87c-9565fb899323" removed.
Jan 20 18:06:58 remote server: 18:06:58.898 [http-bio-8080-exec-67] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:06:59 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:06:59 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:06:59 remote guacd[1534]: Connection ID is "$bdf94728-75ca-4866-b010-61e993a53552"
Jan 20 18:06:59 remote guacd: guacd[1534]: INFO:#011Connection ID is "$bdf94728-75ca-4866-b010-61e993a53552"
Jan 20 18:06:59 remote guacd[19087]: Support for protocol "rdp" is not installed
Jan 20 18:06:59 remote guacd: guacd[19087]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:06:59 remote guacd[1534]: Connection "$bdf94728-75ca-4866-b010-61e993a53552" removed.
Jan 20 18:06:59 remote guacd: guacd[1534]: INFO:#011Connection "$bdf94728-75ca-4866-b010-61e993a53552" removed.
Jan 20 18:07:01 remote server: 18:07:01.169 [http-bio-8080-exec-20] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:03 remote server: 18:07:03.098 [http-bio-8080-exec-51] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:12 remote server: 18:07:12.006 [http-bio-8080-exec-70] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:14 remote server: 18:07:14.253 [http-bio-8080-exec-73] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:16 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:07:16 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:07:16 remote guacd[1534]: Connection ID is "$6b57ed42-07cb-4855-81a8-5a700d93719f"
Jan 20 18:07:16 remote guacd: guacd[1534]: INFO:#011Connection ID is "$6b57ed42-07cb-4855-81a8-5a700d93719f"
Jan 20 18:07:16 remote guacd[19103]: Support for protocol "rdp" is not installed
Jan 20 18:07:16 remote guacd: guacd[19103]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:07:16 remote guacd[1534]: Connection "$6b57ed42-07cb-4855-81a8-5a700d93719f" removed.
Jan 20 18:07:16 remote guacd: guacd[1534]: INFO:#011Connection "$6b57ed42-07cb-4855-81a8-5a700d93719f" removed.
Jan 20 18:07:17 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:07:17 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:07:17 remote guacd[1534]: Connection ID is "$3812b5b5-e85a-4dc4-8ded-bb3ff88811a3"
Jan 20 18:07:17 remote guacd: guacd[1534]: INFO:#011Connection ID is "$3812b5b5-e85a-4dc4-8ded-bb3ff88811a3"
Jan 20 18:07:17 remote guacd[19108]: Support for protocol "rdp" is not installed
Jan 20 18:07:17 remote guacd: guacd[19108]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:07:17 remote guacd[1534]: Connection "$3812b5b5-e85a-4dc4-8ded-bb3ff88811a3" removed.
Jan 20 18:07:17 remote guacd: guacd[1534]: INFO:#011Connection "$3812b5b5-e85a-4dc4-8ded-bb3ff88811a3" removed.
Jan 20 18:07:20 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:07:20 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:07:20 remote guacd[1534]: Connection ID is "$01d75095-b9bb-4e7a-a60e-5add60f835ad"
Jan 20 18:07:20 remote guacd: guacd[1534]: INFO:#011Connection ID is "$01d75095-b9bb-4e7a-a60e-5add60f835ad"
Jan 20 18:07:20 remote guacd[19114]: Support for protocol "rdp" is not installed
Jan 20 18:07:20 remote guacd: guacd[19114]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:07:20 remote guacd[1534]: Connection "$01d75095-b9bb-4e7a-a60e-5add60f835ad" removed.
Jan 20 18:07:20 remote guacd: guacd[1534]: INFO:#011Connection "$01d75095-b9bb-4e7a-a60e-5add60f835ad" removed.
Jan 20 18:07:27 remote journal: unable to create file '/run/user/0/dconf/user': Permission denied. dconf will not work properly.
Jan 20 18:07:27 remote journal: unable to create file '/run/user/0/dconf/user': Permission denied. dconf will not work properly.
Jan 20 18:07:29 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:07:29 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:07:29 remote guacd[1534]: Connection ID is "$bb6e3465-91fc-48df-a851-279004927f85"
Jan 20 18:07:29 remote guacd: guacd[1534]: INFO:#011Connection ID is "$bb6e3465-91fc-48df-a851-279004927f85"
Jan 20 18:07:29 remote guacd[19134]: Support for protocol "rdp" is not installed
Jan 20 18:07:29 remote guacd: guacd[19134]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:07:29 remote guacd[1534]: Connection "$bb6e3465-91fc-48df-a851-279004927f85" removed.
Jan 20 18:07:29 remote guacd: guacd[1534]: INFO:#011Connection "$bb6e3465-91fc-48df-a851-279004927f85" removed.
Jan 20 18:07:31 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:07:31 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:07:31 remote guacd[1534]: Connection ID is "$9e3726ec-0ad5-4baa-bcb7-751002367f9c"
Jan 20 18:07:31 remote guacd: guacd[1534]: INFO:#011Connection ID is "$9e3726ec-0ad5-4baa-bcb7-751002367f9c"
Jan 20 18:07:31 remote guacd[19140]: Support for protocol "rdp" is not installed
Jan 20 18:07:31 remote guacd: guacd[19140]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:07:31 remote guacd[1534]: Connection "$9e3726ec-0ad5-4baa-bcb7-751002367f9c" removed.
Jan 20 18:07:31 remote guacd: guacd[1534]: INFO:#011Connection "$9e3726ec-0ad5-4baa-bcb7-751002367f9c" removed.
Jan 20 18:07:31 remote server: 18:07:31.516 [http-bio-8080-exec-66] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:32 remote server: 18:07:32.457 [http-bio-8080-exec-67] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:35 remote server: 18:07:35.110 [http-bio-8080-exec-57] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:44 remote server: 18:07:44.026 [http-bio-8080-exec-68] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:46 remote server: 18:07:46.278 [http-bio-8080-exec-20] ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation of WebSocket tunnel to guacd failed: Connection to guacd timed out.
Jan 20 18:07:47 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:07:47 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:07:47 remote guacd[1534]: Connection ID is "$c021640a-dde7-4a51-989d-33e12fc2c835"
Jan 20 18:07:47 remote guacd: guacd[1534]: INFO:#011Connection ID is "$c021640a-dde7-4a51-989d-33e12fc2c835"
Jan 20 18:07:47 remote guacd[19154]: Support for protocol "rdp" is not installed
Jan 20 18:07:47 remote guacd: guacd[19154]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:07:47 remote guacd[1534]: Connection "$c021640a-dde7-4a51-989d-33e12fc2c835" removed.
Jan 20 18:07:47 remote guacd: guacd[1534]: INFO:#011Connection "$c021640a-dde7-4a51-989d-33e12fc2c835" removed.
Jan 20 18:07:48 remote guacd[1534]: Creating new client for protocol "rdp"
Jan 20 18:07:48 remote guacd: guacd[1534]: INFO:#011Creating new client for protocol "rdp"
Jan 20 18:07:48 remote guacd[1534]: Connection ID is "$03914516-d7f4-4ca5-bdac-b4b2719bb8e1"
Jan 20 18:07:48 remote guacd: guacd[1534]: INFO:#011Connection ID is "$03914516-d7f4-4ca5-bdac-b4b2719bb8e1"
Jan 20 18:07:48 remote guacd[19161]: Support for protocol "rdp" is not installed
Jan 20 18:07:48 remote guacd: guacd[19161]: WARNING:#011Support for protocol "rdp" is not installed
Jan 20 18:07:48 remote guacd[1534]: Connection "$03914516-d7f4-4ca5-bdac-b4b2719bb8e1" removed.
Jan 20 18:07:48 remote guacd: guacd[1534]: INFO:#011Connection "$03914516-d7f4-4ca5-bdac-b4b2719bb8e1" removed.
From: Mike Jumper <mi...@glyptodon.com>
Sent: Monday, January 20, 2020 2:26 PM
To: user@guacamole.apache.org
Subject: Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
On Mon, Jan 20, 2020 at 12:17 PM Newman, Dennis <de...@spglobal.com>> wrote:
... Now the Guacamole Gateway is reachable – but nobody can connect to their RDP sessions.
Killed guacd
Restarted guacd – get
Guacamole proxy daemon (guacd) version 1.0.0 started
But still cannot connect to any remote desktop sessions
Is guacd now running? What other messages are logged by guacd as it starts?
What messages are logged by guacd when a failed attempt is made to connect to a remote desktop?
- Mike
________________________________
The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.
Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
Posted by Mike Jumper <mi...@glyptodon.com>.
On Tue, Jan 21, 2020 at 7:38 AM Newman, Dennis <de...@spglobal.com>
wrote:
> Mike,
>
> Sorry for this old man’s confusion.
>
> Not sure just how to run Guacamole using the docker image. Is that
> something that would have been installed when I first set Guac up?
>
No, you would need to first install Docker. Most distributions have Docker
in their repositories, and Docker provides a repository of their own for
their "Docker CE" version. There should be instructions galore on the
general internet for setting up Docker on CentOS 7.
I have however managed to uninstall freerdp 2 and reinstall
> freerdp1.2/1.2.0/13.el7/x86_64
>
> Using the instructions from Gelap78’s comment at
> https://github.com/Zer0CoolX/guacamole-install-rhel/issues/78
>
>
>
> Changing the freerdp and just rebooting the server still gives me no rdp
> connections –
>
> do I now need to reinstall Guac?
>
No. You need to rebuild guacamole-server.
FreeRDP 1.2 is different from the version that CentOS 7 previously used and
is not compatible with that older version. The version of Guacamole you
have is compatible with FreeRDP 1.2, but would need to be specifically
built against it. The various versions of FreeRDP are not API-compatible
nor ABI-compatible with each other.
If so, will a re-install blow away my users and connections database?
>
You don't need to reinstall the web application. If you decide to reinstall
it, you do not need to reinstall the database that it's using, nor would
you need to rerun the SQL scripts. Nothing should be blown away. If you are
concerned you may accidentally follow a step which is not applicable to
your case and does blow things away, I recommend backing up your database
first.
- Mike
Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
Posted by Mike Jumper <mi...@glyptodon.com>.
On Tue, Jan 21, 2020 at 8:11 AM Newman, Dennis <de...@spglobal.com>
wrote:
> Mike,
>
> Everything seems to be working now – THANK YOU! For your assistance.
>
> Turns out that after following the uninstall and reinstall of freerdp
> instructions, I had missed the
>
> yum install libguac-client-rdp
>
> After running that – everything popped.
>
>
>
Assuming the libguac-client-rdp package you installed was built against the
FreeRDP package you installed, this should work fine, but beware that you
may well now have multiple versions of libguac-client-rdp present (one from
your old build and one from the distribution package) and multiple versions
of libguac (one from your old build and one pulled in from distribution
packages as a dependency for libguac-client-rdp). You may also have
multiple versions of guacd present.
I recommend taking time to make sure things are sane when you have a
maintenance window, etc. and things can be taken down / brought back up
with minimal disruption.
- Mike
RE: Guacamole Stopped - guacd = Unable to bind socket to any
addresses.
Posted by "Newman, Dennis" <de...@spglobal.com>.
Mike,
Everything seems to be working now – THANK YOU! For your assistance.
Turns out that after following the uninstall and reinstall of freerdp instructions, I had missed the
yum install libguac-client-rdp
After running that – everything popped.
I’m a 65 year old “Script Kiddie”
Set my Guac up following Zer0CoolX’s install script, and using Guac to allow about 100 out of country data entry workers access to virtual windows 7 systems running in VmWare to connect and enter rate data into an IBM iSeries Power 8 server.
Without the help of groups like this – I and my team would be dead in the water.
Thanks Again!
Dennis
From: Newman, Dennis <de...@spglobal.com>
Sent: Tuesday, January 21, 2020 9:15 AM
To: user@guacamole.apache.org
Subject: RE: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
Mike,
Sorry for this old man’s confusion.
Not sure just how to run Guacamole using the docker image. Is that something that would have been installed when I first set Guac up?
I have however managed to uninstall freerdp 2 and reinstall freerdp1.2/1.2.0/13.el7/x86_64
Using the instructions from Gelap78’s comment at https://github.com/Zer0CoolX/guacamole-install-rhel/issues/78
Changing the freerdp and just rebooting the server still gives me no rdp connections –
do I now need to reinstall Guac?
If so, will a re-install blow away my users and connections database?
Thanks
Dennis
From: Mike Jumper <mi...@glyptodon.com>>
Sent: Monday, January 20, 2020 4:37 PM
To: user@guacamole.apache.org<ma...@guacamole.apache.org>
Subject: Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
On Mon, Jan 20, 2020 at 2:14 PM Newman, Dennis <de...@spglobal.com>> wrote:
Mike,
Ok looking at what seems to be installed – it does look like freerdp updated - I see
freerdp-devel.x86_64 2.0.0-1.rc4.el7 @base
freerdp-libs.x86_64 2.0.0-1.rc4.el7 @base
My latest update (5) shows
freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
2.0.0-1.rc4.el7.x86_64 @base
freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
freerdp-devel-2.0.0-1.rc4.el7.x86_64 @base
Attempting yum history undo 5 gives me
Error no packages available to install
So how do I go about either using the "guacamole/guacd" Docker image – OR
How would I go about upgrading my entire Guac install. – Or moving my user and system database to a fresh install.
Just pointing to the proper instruction pages would help.
Here you go:
http://guacamole.apache.org/doc/gug/guacamole-docker.html#guacd-docker-external
You don't need to tear down your existing Guacamole install - just killing the local guacd service and starting the "guacamole/guacd" Docker image as its replacement should solve things for the time being. I would then keep an eye out for 1.1.0, which is looking like it will be released soon and has support for FreeRDP 2.0.0.
- Mike
________________________________
The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.
RE: Guacamole Stopped - guacd = Unable to bind socket to any
addresses.
Posted by "Newman, Dennis" <de...@spglobal.com>.
Mike,
Sorry for this old man’s confusion.
Not sure just how to run Guacamole using the docker image. Is that something that would have been installed when I first set Guac up?
I have however managed to uninstall freerdp 2 and reinstall freerdp1.2/1.2.0/13.el7/x86_64
Using the instructions from Gelap78’s comment at https://github.com/Zer0CoolX/guacamole-install-rhel/issues/78
Changing the freerdp and just rebooting the server still gives me no rdp connections –
do I now need to reinstall Guac?
If so, will a re-install blow away my users and connections database?
Thanks
Dennis
From: Mike Jumper <mi...@glyptodon.com>
Sent: Monday, January 20, 2020 4:37 PM
To: user@guacamole.apache.org
Subject: Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
On Mon, Jan 20, 2020 at 2:14 PM Newman, Dennis <de...@spglobal.com>> wrote:
Mike,
Ok looking at what seems to be installed – it does look like freerdp updated - I see
freerdp-devel.x86_64 2.0.0-1.rc4.el7 @base
freerdp-libs.x86_64 2.0.0-1.rc4.el7 @base
My latest update (5) shows
freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
2.0.0-1.rc4.el7.x86_64 @base
freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
freerdp-devel-2.0.0-1.rc4.el7.x86_64 @base
Attempting yum history undo 5 gives me
Error no packages available to install
So how do I go about either using the "guacamole/guacd" Docker image – OR
How would I go about upgrading my entire Guac install. – Or moving my user and system database to a fresh install.
Just pointing to the proper instruction pages would help.
Here you go:
http://guacamole.apache.org/doc/gug/guacamole-docker.html#guacd-docker-external
You don't need to tear down your existing Guacamole install - just killing the local guacd service and starting the "guacamole/guacd" Docker image as its replacement should solve things for the time being. I would then keep an eye out for 1.1.0, which is looking like it will be released soon and has support for FreeRDP 2.0.0.
- Mike
________________________________
The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.
Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
Posted by Mike Jumper <mi...@glyptodon.com>.
On Mon, Jan 20, 2020 at 2:14 PM Newman, Dennis <de...@spglobal.com>
wrote:
> Mike,
>
> Ok looking at what seems to be installed – it does look like freerdp
> updated - I see
>
>
>
> freerdp-devel.x86_64 2.0.0-1.rc4.el7 @base
>
> freerdp-libs.x86_64 2.0.0-1.rc4.el7 @base
>
>
>
> My latest update (5) shows
>
> freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
>
> 2.0.0-1.rc4.el7.x86_64
> @base
>
> freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
>
> freerdp-devel-2.0.0-1.rc4.el7.x86_64 @base
>
>
>
> Attempting yum history undo 5 gives me
>
> Error no packages available to install
>
>
>
> So how do I go about either using the "guacamole/guacd" Docker image – OR
>
> How would I go about upgrading my entire Guac install. – Or moving my user
> and system database to a fresh install.
>
> Just pointing to the proper instruction pages would help.
>
Here you go:
http://guacamole.apache.org/doc/gug/guacamole-docker.html#guacd-docker-external
You don't need to tear down your existing Guacamole install - just killing
the local guacd service and starting the "guacamole/guacd" Docker image as
its replacement should solve things for the time being. I would then keep
an eye out for 1.1.0, which is looking like it will be released soon and
has support for FreeRDP 2.0.0.
- Mike
RE: Guacamole Stopped - guacd = Unable to bind socket to any
addresses.
Posted by "Newman, Dennis" <de...@spglobal.com>.
Mike,
Ok looking at what seems to be installed – it does look like freerdp updated - I see
freerdp-devel.x86_64 2.0.0-1.rc4.el7 @base
freerdp-libs.x86_64 2.0.0-1.rc4.el7 @base
My latest update (5) shows
freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
2.0.0-1.rc4.el7.x86_64 @base
freerdp-devel-1.0.2-15.el7_6.1.x86_64 @updates
freerdp-devel-2.0.0-1.rc4.el7.x86_64 @base
Attempting yum history undo 5 gives me
Error no packages available to install
So how do I go about either using the "guacamole/guacd" Docker image – OR
How would I go about upgrading my entire Guac install. – Or moving my user and system database to a fresh install.
Just pointing to the proper instruction pages would help.
I’m no expert – but am able to follow directions – Setting up Guac was as simple as following the directions and everything just worked, so knowing what to do “under the hood” escapes me.
Dennis
From: Mike Jumper <mi...@glyptodon.com>
Sent: Monday, January 20, 2020 2:57 PM
To: user@guacamole.apache.org
Subject: Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
On Mon, Jan 20, 2020 at 12:44 PM Newman, Dennis <de...@spglobal.com>> 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
________________________________
The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.
Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
Posted by Mike Jumper <mi...@glyptodon.com>.
On Mon, Jan 20, 2020 at 12:44 PM Newman, Dennis <de...@spglobal.com>
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
Re: Guacamole Stopped - guacd = Unable to bind socket to any
addresses.
Posted by ivanmarcus <iv...@yahoo.com.INVALID>.
Dennis,
I've had nothing to do with CentOS (so you might need to modifiy the
paths/filenames I give below) but the detail Mike is talking about may
be located in your syslog.
This is what I'd do in Ubuntu/Debian:
cat /var/log/syslog | grep guacd - this will troll through the system
log and report any line that starts with 'guacd'
At some point you may also want to look at the tomcat catalina.out file.
tail -600 /var/log/tomcat7/catalina.out | less - would give you the
last 600 lines of this log file, piping it to less which will allow you
to scroll through it nicely. You can change the 600 to any number you
like, or use 'f' which will give you a live view.
With luck the data in these log files will give you some pointers as to
what's going on.
On 21/01/2020 9:44 a.m., Newman, Dennis 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.
>
> Dennis
>
> *From:* Mike Jumper <mi...@glyptodon.com>
> *Sent:* Monday, January 20, 2020 2:26 PM
> *To:* user@guacamole.apache.org
> *Subject:* Re: Guacamole Stopped - guacd = Unable to bind socket to
> any addresses.
>
> On Mon, Jan 20, 2020 at 12:17 PM Newman, Dennis
> <dennis.newman@spglobal.com <ma...@spglobal.com>> wrote:
>
> ... Now the Guacamole Gateway is reachable – but nobody can
> connect to their RDP sessions.
>
> Killed guacd
>
> Restarted guacd – get
>
> Guacamole proxy daemon (guacd) version 1.0.0 started
>
> But still cannot connect to any remote desktop sessions
>
> Is guacd now running? What other messages are logged by guacd as it
> starts?
>
> What messages are logged by guacd when a failed attempt is made to
> connect to a remote desktop?
>
> - Mike
>
>
> ------------------------------------------------------------------------
>
> The information contained in this message is intended only for the
> recipient, and may be a confidential attorney-client communication or
> may otherwise be privileged and confidential and protected from
> disclosure. If the reader of this message is not the intended
> recipient, or an employee or agent responsible for delivering this
> message to the intended recipient, please be aware that any
> dissemination or copying of this communication is strictly prohibited.
> If you have received this communication in error, please immediately
> notify us by replying to the message and deleting it from your
> computer. S&P Global Inc. reserves the right, subject to applicable
> local law, to monitor, review and process the content of any
> electronic message or information sent to or from S&P Global Inc.
> e-mail addresses without informing the sender or recipient of the
> message. By sending electronic message or information to S&P Global
> Inc. e-mail addresses you, as the sender, are consenting to S&P Global
> Inc. processing any of your personal data therein.
RE: Guacamole Stopped - guacd = Unable to bind socket to any
addresses.
Posted by "Newman, Dennis" <de...@spglobal.com>.
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.
Dennis
From: Mike Jumper <mi...@glyptodon.com>
Sent: Monday, January 20, 2020 2:26 PM
To: user@guacamole.apache.org
Subject: Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
On Mon, Jan 20, 2020 at 12:17 PM Newman, Dennis <de...@spglobal.com>> wrote:
... Now the Guacamole Gateway is reachable – but nobody can connect to their RDP sessions.
Killed guacd
Restarted guacd – get
Guacamole proxy daemon (guacd) version 1.0.0 started
But still cannot connect to any remote desktop sessions
Is guacd now running? What other messages are logged by guacd as it starts?
What messages are logged by guacd when a failed attempt is made to connect to a remote desktop?
- Mike
________________________________
The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. S&P Global Inc. reserves the right, subject to applicable local law, to monitor, review and process the content of any electronic message or information sent to or from S&P Global Inc. e-mail addresses without informing the sender or recipient of the message. By sending electronic message or information to S&P Global Inc. e-mail addresses you, as the sender, are consenting to S&P Global Inc. processing any of your personal data therein.
Re: Guacamole Stopped - guacd = Unable to bind socket to any addresses.
Posted by Mike Jumper <mi...@glyptodon.com>.
On Mon, Jan 20, 2020 at 12:17 PM Newman, Dennis <de...@spglobal.com>
wrote:
> ... Now the Guacamole Gateway is reachable – but nobody can connect to
> their RDP sessions.
>
>
>
> Killed guacd
>
> Restarted guacd – get
>
> Guacamole proxy daemon (guacd) version 1.0.0 started
>
> But still cannot connect to any remote desktop sessions
>
Is guacd now running? What other messages are logged by guacd as it starts?
What messages are logged by guacd when a failed attempt is made to connect
to a remote desktop?
- Mike