Re: Why did I not install guacd as systemd

[Johnnie W Adams]

Thanks! I'm surprised that systemd isn't the default.

On Thu, Apr 11, 2024 at 4:01 PM Nick Couchman  wrote:

> On Thu, Apr 11, 2024 at 4:53 PM Johnnie W Adams  wrote:
>
>> Hi, folks,
>>
>>  I'm comparing my installation to the one I inherited, and I noticed
>> that the one I inherited has guacd installed as a systemd unit file, but
>> the one I built does not. Did I do something wrong in the configuration?
>> Both installations are 1.5.4 to the best of my knowledge. (I'm not entirely
>> certain how to determine it on the one I inherited.)
>>
>>
> There's an option in the configure script for enabling systemd:
>
>   --with-systemd-dir=
>   install systemd units to the given directory
>
> You'll need to run that and provide a path to the directory you'd like to
> install the systemd unit files in (/etc/systemd/system is common).
>
> Also, depending on your system configuration, you may need to change the
> user that guacd runs under. The default one in the systemd file included
> with the distribution is "daemon", however, on many systems this user does
> not have a writable home directory (RHEL and variants use /sbin as the home
> directory), and RDP connections will likely fail due to the inability of
> the user to write out the FreeRDP known_hosts file. So, you may also want
> to create a user account and change the systemd file such that guacd runs
> under its own user account.
>
> -Nick
>
>>

-- 
John Adams
Senior Linux/Middleware Administrator  | Information Technology Services
+1-501-916-3010 | jxad...@ualr.edu | http://ualr.edu/itservices
*UA Little Rock*

Reminder:  IT Services will never ask for your password over the phone or
in an email. Always be suspicious of requests for personal information that
come via email, even from known contacts.  For more information or to
report suspicious email, visit IT Security
.

Re: Why did I not install guacd as systemd

[Nick Couchman]

On Thu, Apr 11, 2024 at 4:53 PM Johnnie W Adams  wrote:

> Hi, folks,
>
>  I'm comparing my installation to the one I inherited, and I noticed
> that the one I inherited has guacd installed as a systemd unit file, but
> the one I built does not. Did I do something wrong in the configuration?
> Both installations are 1.5.4 to the best of my knowledge. (I'm not entirely
> certain how to determine it on the one I inherited.)
>
>
There's an option in the configure script for enabling systemd:

  --with-systemd-dir=
  install systemd units to the given directory

You'll need to run that and provide a path to the directory you'd like to
install the systemd unit files in (/etc/systemd/system is common).

Also, depending on your system configuration, you may need to change the
user that guacd runs under. The default one in the systemd file included
with the distribution is "daemon", however, on many systems this user does
not have a writable home directory (RHEL and variants use /sbin as the home
directory), and RDP connections will likely fail due to the inability of
the user to write out the FreeRDP known_hosts file. So, you may also want
to create a user account and change the systemd file such that guacd runs
under its own user account.

-Nick

>

Why did I not install guacd as systemd

[Johnnie W Adams]

Hi, folks,

 I'm comparing my installation to the one I inherited, and I noticed
that the one I inherited has guacd installed as a systemd unit file, but
the one I built does not. Did I do something wrong in the configuration?
Both installations are 1.5.4 to the best of my knowledge. (I'm not entirely
certain how to determine it on the one I inherited.)

Thanks,

 John A

-- 
John Adams
Senior Linux/Middleware Administrator  | Information Technology Services
+1-501-916-3010 | jxad...@ualr.edu | http://ualr.edu/itservices
*UA Little Rock*

Reminder:  IT Services will never ask for your password over the phone or
in an email. Always be suspicious of requests for personal information that
come via email, even from known contacts.  For more information or to
report suspicious email, visit IT Security
.

SAML-related error I don't understand

[Johnnie W Adams]

Hi, folks,

 I'm trying to figure out why I got this error on startup for the new
server pair I'm building:

13:52:11.887 [http-nio-8080-exec-1] WARN  o.a.g.e.AuthenticationProviderFacade
- The "saml" authentication provider has encountered an internal error
which will halt the authentication process. If this is unexpected or you
are the developer of this authentication provider, you may wish to enable
debug-level logging. If this is expected and you wish to ignore such
failures in the future, please set "skip-if-unavailable: saml" within your
guacamole.properties.

13:52:11.887 [http-nio-8080-exec-1] ERROR o.a.g.rest.RESTExceptionMapper -
An internal error occurred, but did not contain an error message. Enable
debug-level logging for details.

 I did set skip-if-unavailable and got past it, but I don't quite get
what it means. Is it just complaining that I haven't set SAML up yet?

Thanks,

 John A

-- 
John Adams
Senior Linux/Middleware Administrator  | Information Technology Services
+1-501-916-3010 | jxad...@ualr.edu | http://ualr.edu/itservices
*UA Little Rock*

Reminder:  IT Services will never ask for your password over the phone or
in an email. Always be suspicious of requests for personal information that
come via email, even from known contacts.  For more information or to
report suspicious email, visit IT Security
.