RE: Guacamole issue 1.5.4

[Niranjan A <ni...@codincity.com>]

HI Nick,

I am receiving the segfault every three days. Currently I have scheduled the OS restart for every third days due to this for past three month we don’t face the segfault but if I change the schedule restart to 4th day getting the segfault. Is there any cache or any problem in guacamole.

Kindly suggest.

Regards,
Niranjan Ananthan

From: Niranjan A <ni...@codincity.com>
Sent: 27 May 2024 21:38
To: user@guacamole.apache.org
Subject: Re: Guacamole issue 1.5.4

Currently Guacd is running on root account.


Regards,

Niranjan Ananthan

________________________________
From: Niranjan A <ni...@codincity.com>>
Sent: Monday, May 27, 2024 9:36 PM
To: user@guacamole.apache.org<ma...@guacamole.apache.org> <us...@guacamole.apache.org>>
Subject: Re: Guacamole issue 1.5.4

Hi Nick,

How to enable the coredump. Also, whether running the Guacamole in AMD VM (D2as_V5) will create a problem. I am getting this error once in two days.


Regards,

Niranjan Ananthan

________________________________
From: Nick Couchman <vn...@apache.org>>
Sent: Sunday, May 12, 2024 6:15 PM
To: user@guacamole.apache.org<ma...@guacamole.apache.org> <us...@guacamole.apache.org>>
Subject: Re: Guacamole issue 1.5.4

On Sun, May 12, 2024 at 4:52 AM Niranjan A <ni...@codincity.com>> wrote:
Hi Team,

I am getting the below error on the guacamole server and please find the current configuration details

Ubuntu 22
AMD Processor
Guacamole 1.5.4[Manual Installation]


Have you tried 1.5.5?


Error:

May 10 12:01:07  kernel: [180410.400804] guacd[3499490]: segfault at 18 ip 00007089baa9a64c sp 0000708989ffaaa0 error 4 in libc.so.6[7089baa28000+195000] likely on CPU 1 (core 0, socket 0)
May 10 12:47:48 kernel: [ 2745.489801] guacd[117195]: segfault at 7006fa406a70 ip 0000700aa97fe317 sp 0000700a61ffaae0 error 6 in libguac-client-ssh.so.0.0.0[700aa97f7000+b000] likely on CPU 0 (core 0, socket 0)


If you can locate the coredump files that are left from the segfault, it would be nice to have a stack trace (backtrace, bt from gdb) on those core files to figure out why the segfault is happening.




 guacd[1550069]: File open refused (-2): "\desktop.ini"
File open refused (-2): "\FromDelivery66244\desktop.ini"
File open refused (-2): "\FromDelivery65878\desktop.ini"
File open refused (-2): "\FromDelivery65701\desktop.ini"


Two things, here - first, make sure that the Linux account under which guacd is running has access to the files/folders that you're sharing. Aside from that, desktop.ini may not exist and these may actually be harmless messages unrelated to your segfault issue.

-Nick

Re: Guacamole issue 1.5.4

[Nick Couchman <vn...@apache.org>]

On Tue, Oct 8, 2024 at 2:07 AM Niranjan A <ni...@codincity.com>
wrote:

> HI Nick,
>
>
>
> I am receiving the segfault every three days. Currently I have scheduled
> the OS restart for every third days due to this for past three month we
> don’t face the segfault but if I change the schedule restart to 4th day
> getting the segfault. Is there any cache or any problem in guacamole.
>
>
>
> Kindly suggest.
>
>
>

I already suggested:
* Gather the coredump files and get the full stack trace of the segfault so
that we can figure out why it is occurring. How you enable and gather the
coredump file and stack trace depends on your Linux distribution and how it
manages core dumps, so you will have to consult the documentation for the
version of Linux you're running on in order to grab that. Alternatively,
you can launch guacd with gdb, and then tell gdb to follow the child forks
and evaluate the stack trace in real-time.
* Upgrade from 1.5.4 to 1.5.5 and see if the issue still exists. If it does
not, the problem is solved. If it continues, you'll need to gather the
coredump and get the stack trace.

Until you're able to send a stack trace we cannot help you any further.

-Nick

>