Re: Just built and installed guacamole, but no guacamole.properties found

[Nick Couchman]

On Fri, Mar 15, 2024 at 3:33 PM Johnnie W Adams  wrote:

> Hi, folks,
>
>  I've built guacamole on Red Hat 9 and cannot find a
> guacamole.properties file anywhere.
>
>
You have to create it and populate it yourself - there is no
default/template that gets generated or installed.

-Nick

>

Just built and installed guacamole, but no guacamole.properties found

[Johnnie W Adams]

Hi, folks,

 I've built guacamole on Red Hat 9 and cannot find a
guacamole.properties file anywhere.

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
.

Re: Unexpected error in REST endpoint

[Michael Jumper]

On 3/15/24 07:07, Vieri wrote:



On Friday, March 15, 2024 at 02:59:01 PM GMT+1, Nick Couchman 
 wrote:


2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] DEBUG 
o.a.g.rest.RESTExceptionMapper - Unexpected error in REST endpoint.
java.lang.NullPointerException: null
     at java.io.Reader.(Reader.java:78)
     at java.io.InputStreamReader.(InputStreamReader.java:97)
     at 
org.apache.guacamole.rest.patch.PatchRESTService.readResourceAsString(PatchRESTService.java:69)
     at 
org.apache.guacamole.rest.patch.PatchRESTService.getPatches(PatchRESTService.java:113)
     at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
     at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:498)


.Sorry about that, didn't go back and look at the original. It looks like the 
expected data isn't making it to the input stream, which seems to indicate that
the data is getting dropped before it hits the Tomcat server. This seems to me 
to be something outside of the Guacamole stack itself - something
system-related, or perhaps a firewall or Web Application Firewall (WAF) that 
might be blocking the traffic?


No problem. Thanks for looking into it.

If it were a WAF or FW issue I'm guessing a Tomcat restart wouldn't solve the 
problem immediately... but it does.

As of the system I don't know where to look. Still, isn't it odd that 
restarting the Tomcat service solves the problem? Could it have anything to do 
with open file descriptors?



The location where that exception is occurring is within the part of 
Guacamole that reads the .jar files of extensions, specifically related 
to reading HTML patch files. The error shown in the stacktrace indicates 
that some extension has an HTML patch declared in its guac-manifest.json 
that does not actually exist in the extension.


Do you have a custom extension present that might have a 
guac-manifest.json containing one or more incorrect paths to HTML patches?


If not, the only other possible cause would be modification of the 
extension .jar while the webapp is running, which could cause cached 
portions of the .jar to no longer align with the actual contents on disk.


- Mike

-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org

Re: Unexpected error in REST endpoint

[Vieri]

On Friday, March 15, 2024 at 02:59:01 PM GMT+1, Nick Couchman 
 wrote: 

>> 2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] DEBUG 
>> o.a.g.rest.RESTExceptionMapper - Unexpected error in REST endpoint.
>> java.lang.NullPointerException: null
>>     at java.io.Reader.(Reader.java:78)
>>     at java.io.InputStreamReader.(InputStreamReader.java:97)
>>     at 
>> org.apache.guacamole.rest.patch.PatchRESTService.readResourceAsString(PatchRESTService.java:69)
>>     at 
>> org.apache.guacamole.rest.patch.PatchRESTService.getPatches(PatchRESTService.java:113)
>>     at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
>>     at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>     at java.lang.reflect.Method.invoke(Method.java:498)
>
>.Sorry about that, didn't go back and look at the original. It looks like the 
>expected data isn't making it to the input stream, which seems to indicate 
>that 
> the data is getting dropped before it hits the Tomcat server. This seems to 
> me to be something outside of the Guacamole stack itself - something 
> system-related, or perhaps a firewall or Web Application Firewall (WAF) that 
> might be blocking the traffic?

No problem. Thanks for looking into it.

If it were a WAF or FW issue I'm guessing a Tomcat restart wouldn't solve the 
problem immediately... but it does.

As of the system I don't know where to look. Still, isn't it odd that 
restarting the Tomcat service solves the problem? Could it have anything to do 
with open file descriptors?

Vieri

-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org

Re: Unexpected error in REST endpoint

[Nick Couchman]

On Fri, Mar 15, 2024 at 9:20 AM Vieri  wrote:

>
>
> On Friday, March 15, 2024 at 11:48:26 AM GMT+1, Nick Couchman <
> vn...@apache.org> wrote:
>
> > Can you get the full trace of this NullPointerExecption?
>
> It's the same as in my previous post:
>
> 2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] DEBUG
> o.a.g.rest.RESTExceptionMapper - Unexpected error in REST endpoint.
> java.lang.NullPointerException: null
> at java.io.Reader.(Reader.java:78)
> at java.io.InputStreamReader.(InputStreamReader.java:97)
> at
> org.apache.guacamole.rest.patch.PatchRESTService.readResourceAsString(PatchRESTService.java:69)
> at
> org.apache.guacamole.rest.patch.PatchRESTService.getPatches(PatchRESTService.java:113)
> at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
>

...
Sorry about that, didn't go back and look at the original. It looks like
the expected data isn't making it to the input stream, which seems to
indicate that the data is getting dropped before it hits the Tomcat server.
This seems to me to be something outside of the Guacamole stack itself -
something system-related, or perhaps a firewall or Web Application Firewall
(WAF) that might be blocking the traffic?

-Nick

Re: Unexpected error in REST endpoint

[Vieri]

On Friday, March 15, 2024 at 11:48:26 AM GMT+1, Nick Couchman 
 wrote: 

> Can you get the full trace of this NullPointerExecption?

It's the same as in my previous post:

2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] DEBUG 
o.a.g.rest.RESTExceptionMapper - Unexpected error in REST endpoint.
java.lang.NullPointerException: null
    at java.io.Reader.(Reader.java:78)
    at java.io.InputStreamReader.(InputStreamReader.java:97)
    at 
org.apache.guacamole.rest.patch.PatchRESTService.readResourceAsString(PatchRESTService.java:69)
    at 
org.apache.guacamole.rest.patch.PatchRESTService.getPatches(PatchRESTService.java:113)
    at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at 
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52)
    at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:146)
    at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:189)
    at 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:219)
    at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:93)
    at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:478)
    at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:400)
    at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:81)
    at 
org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:256)
    at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
    at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
    at 
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265)
    at 
org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:235)
    at 
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:684)
    at 
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
    at 
org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
    at 
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:358)
    at 
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:311)
    at 
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
    at 
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:290)
    at 
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:280)
    at 
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:184)
    at 
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:89)
    at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
    at 
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:121)
    at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:133)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown Source)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown 
Source)
    at org.apache.catalina.core.StandardWrapperValve.invoke(Unknown Source)
    at org.apache.catalina.core.StandardContextValve.invoke(Unknown Source)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Unknown 
Source)
    at org.apache.catalina.core.StandardHostValve.invoke(Unknown Source)
    at org.apache.catalina.valves.ErrorReportValve.invoke(Unknown Source)
    at org.apache.catalina.valves.RemoteIpValve.invoke(Unknown Source)
    at org.apache.catalina.valves.AbstractAccessLogValve.invoke(Unknown 
Source)
    at org.apache.catalina.core.StandardEngineValve.invoke(Unknown Source)
    at org.apache.catalina.connector.CoyoteAdapter.service(Unknown Source)
    at org.apache.coyote.http11.Http11Processor.service(Unknown Source)
    at org.apache.coyote.AbstractProcessorLight.process(Unknown Source)
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(Unknown 
Source)
    at 

Re: Unexpected error in REST endpoint

[Nick Couchman]

On Fri, Mar 15, 2024 at 5:44 AM Vieri  wrote:

> Hi,
>
> After quite a while without any problems I am now hitting this issue again
> (no tampering with extensions or anything at all -- system untouched):
>
> 2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] ERROR
> o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not
> contain an error message. Enable debug-level logging for details.
> 2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] DEBUG
> o.a.g.rest.RESTExceptionMapper - Unexpected error in REST endpoint.
> java.lang.NullPointerException: null
>
>
Can you get the full trace of this NullPointerExecption? You may have to
bump up the logging level of the web application, as documented, here:

https://guacamole.apache.org/doc/gug/configuring-guacamole.html#logging-within-the-web-application

This should give you more details on where the error is actually happening
and we can troubleshoot further from there.

-Nick

Re: Unexpected error in REST endpoint

[Vieri]

Hi,

After quite a while without any problems I am now hitting this issue again (no 
tampering with extensions or anything at all -- system untouched):

2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] ERROR 
o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not 
contain an error message. Enable debug-level logging for details.
2024-03-15 07:34:08,879 [https-openssl-apr-8543-exec-8] DEBUG 
o.a.g.rest.RESTExceptionMapper - Unexpected error in REST endpoint.
java.lang.NullPointerException: null

Restarting Apache Tomcat and that alone solves the problem.

Any ideas?

Tomcat 8.5
Guacamole client 1.5.4

Vieri




On Wednesday, February 14, 2024 at 01:08:19 PM GMT+1, Vieri 
 wrote: 






On Monday, February 12, 2024 at 08:10:23 PM GMT+1, Michael Jumper 
 wrote: 


On 2/12/24 10:18, Vieri wrote:
>> ...
>> [https-openssl-apr-8543-exec-10] DEBUG o.a.g.rest.RESTExceptionMapper - 
>> Unexpected error in REST endpoint.
>> java.lang.NullPointerException: null
>>      at java.io.Reader.(Reader.java:78)
>>      at java.io.InputStreamReader.(InputStreamReader.java:97)
>>      at 
>>org.apache.guacamole.rest.patch.PatchRESTService.readResourceAsString(PatchRESTService.java:69)
>>      at 
>>org.apache.guacamole.rest.patch.PatchRESTService.getPatches(PatchRESTService.java:113)
>>      at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)
>>      ...
>> 
>> Restarting Tomcat and guacd solves the issue (although I think restarting 
>> guacd is not necessary).
>> My setup uses SAML auth.
>> 
>> What can I try if the problem were to come up again?
>> 
>
> Are you perchance replacing or changing the .jar file of an extension 
> while the web application is still running?

Hi,

No, I'm the only admin with access to the Guacamole system, and nothing has 
been moved around. In fact, I haven't even logged into the system for a month, 
and it has been working fine until recently users could open a "blank" page 
from the Guacamole URL but not log in via SAML IdP. In other words, the web app 
would immediately fail as the user couldn't load the remote IdP auth page.

Regards


-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org