You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Guilherme Carvalho <gc...@gmail.com> on 2020/06/17 17:45:42 UTC

Kernel Panic guacd Segfault

Hello, guys, i´m using Guacamole 1.1.0 on a Ubuntu 18.04, i have one
installation on my company working perfectly, but the another installation
on my client i have a Kernel Panic 2 a 3 times per day, that last line
before the server crash is this:

Jun 17 11:33:37 srv-ckg-app-16 kernel: [   15.349251] NET: Registered
protocol family 40
Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.424554] vmxnet3 0000:03:00.0
ens160: intr type 3, mode 0, 9 vectors allocated
Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.425990] vmxnet3 0000:03:00.0
ens160: NIC Link is Up 10000 Mbps
Jun 17 11:33:37 srv-ckg-app-16 kernel: [   24.337831] new mount options do
not match the existing superblock, will be ignored
Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
callbacks suppressed
Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]: segfault
at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
guacd[55eda1436000+7000]
Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
callbacks suppressed
Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]: segfault
at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
guacd[55eda1436000+7000]
Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]: segfault
at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
guacd[55eda1436000+7000]
Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]: segfault
at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
guacd[55eda1436000+7000]
Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]: segfault
at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
guacd[55eda1436000+7000]
Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]: segfault
at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
guacd[55eda1436000+7000]

i saw the server is offline on 12:00:00 than, it return on 12:11.

Anybody know what could be this segfaults?? How fix this?

Thanks
Guilherme Carvalho

Re: Kernel Panic guacd Segfault

Posted by Charaoui, Jérôme <jc...@cmaisonneuve.qc.ca>.
Le 20-06-17 à 14 h 19, Nick Couchman a écrit :
On Wed, Jun 17, 2020 at 1:59 PM Guilherme Carvalho <gc...@gmail.com>> wrote:
i saw that, I also found it strange, it´s a VmWare Server, like as mine and i don´t receive this messages.


I don't think that NIC message is related.  If you look at the uptime stamps on the log messages, you'll see that the NIC comes up 20 seconds after the kernel boots, which is about right (maybe a little slow...probably depends on the disk backing it).  The first segfault doesn't happen until 447 seconds into the system uptime, almost 8 minutes after boot time.

You're right of course, my bad. I didn't read the timestamps correctly.

That said I would suspect something going wrong at the hypervisor level, if you can analyse the ESX logs it might give you a hint.

-- Jerome



Re: Kernel Panic guacd Segfault

Posted by Nick Couchman <vn...@apache.org>.
On Wed, Jun 17, 2020 at 1:59 PM Guilherme Carvalho <gc...@gmail.com>
wrote:

> i saw that, I also found it strange, it´s a VmWare Server, like as mine
> and i don´t receive this messages.
>
>
I don't think that NIC message is related.  If you look at the uptime
stamps on the log messages, you'll see that the NIC comes up 20 seconds
after the kernel boots, which is about right (maybe a little
slow...probably depends on the disk backing it).  The first segfault
doesn't happen until 447 seconds into the system uptime, almost 8 minutes
after boot time.

-Nick

Re: Kernel Panic guacd Segfault

Posted by Guilherme Carvalho <gc...@gmail.com>.
i saw that, I also found it strange, it´s a VmWare Server, like as mine and
i don´t receive this messages.

Em qua., 17 de jun. de 2020 às 14:54, Charaoui, Jérôme <
jcharaoui@cmaisonneuve.qc.ca> escreveu:

> Hi,
>
> Le 20-06-17 à 13 h 46, Guilherme Carvalho a écrit :
> > NIC Link is Up 10000 Mbps
>
> To me that looks like the server is losing network connectivity right
> before guacd crashes.
>
> -- Jerome
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
> For additional commands, e-mail: user-help@guacamole.apache.org
>
>

Re: Kernel Panic guacd Segfault

Posted by Charaoui, Jérôme <jc...@cmaisonneuve.qc.ca>.
Hi,

Le 20-06-17 à 13 h 46, Guilherme Carvalho a écrit :
> NIC Link is Up 10000 Mbps

To me that looks like the server is losing network connectivity right
before guacd crashes.

-- Jerome


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


Re: Kernel Panic guacd Segfault

Posted by Guilherme Carvalho <gc...@gmail.com>.
Nick, i am only using RDP.

Em qua., 17 de jun. de 2020 às 14:50, Nick Couchman <vn...@apache.org>
escreveu:

> On Wed, Jun 17, 2020 at 1:46 PM Guilherme Carvalho <gc...@gmail.com>
> wrote:
>
>> Hello, guys, i´m using Guacamole 1.1.0 on a Ubuntu 18.04, i have one
>> installation on my company working perfectly, but the another installation
>> on my client i have a Kernel Panic 2 a 3 times per day, that last line
>> before the server crash is this:
>>
>> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   15.349251] NET: Registered
>> protocol family 40
>> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.424554] vmxnet3
>> 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
>> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.425990] vmxnet3
>> 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
>> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   24.337831] new mount options
>> do not match the existing superblock, will be ignored
>> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
>> callbacks suppressed
>> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]:
>> segfault at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
>> guacd[55eda1436000+7000]
>> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
>> callbacks suppressed
>> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]:
>> segfault at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
>> guacd[55eda1436000+7000]
>> Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]:
>> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
>> guacd[55eda1436000+7000]
>> Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]:
>> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
>> guacd[55eda1436000+7000]
>> Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]:
>> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
>> guacd[55eda1436000+7000]
>> Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]:
>> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
>> guacd[55eda1436000+7000]
>>
>> i saw the server is offline on 12:00:00 than, it return on 12:11.
>>
>> Anybody know what could be this segfaults?? How fix this?
>>
>>
> It would be good to see the syslog output for the messages from guacd
> prior to the segfault.  Also, what protocol is being used?
>
> -Nick
>

Re: Kernel Panic guacd Segfault

Posted by Nick Couchman <vn...@apache.org>.
On Wed, Jun 17, 2020 at 1:46 PM Guilherme Carvalho <gc...@gmail.com>
wrote:

> Hello, guys, i´m using Guacamole 1.1.0 on a Ubuntu 18.04, i have one
> installation on my company working perfectly, but the another installation
> on my client i have a Kernel Panic 2 a 3 times per day, that last line
> before the server crash is this:
>
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   15.349251] NET: Registered
> protocol family 40
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.424554] vmxnet3 0000:03:00.0
> ens160: intr type 3, mode 0, 9 vectors allocated
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.425990] vmxnet3 0000:03:00.0
> ens160: NIC Link is Up 10000 Mbps
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   24.337831] new mount options do
> not match the existing superblock, will be ignored
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
> callbacks suppressed
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]:
> segfault at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
> callbacks suppressed
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]:
> segfault at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
>
> i saw the server is offline on 12:00:00 than, it return on 12:11.
>
> Anybody know what could be this segfaults?? How fix this?
>
>
It would be good to see the syslog output for the messages from guacd prior
to the segfault.  Also, what protocol is being used?

-Nick

Re: Kernel Panic guacd Segfault

Posted by Mike Jumper <mj...@apache.org>.
On Wed, Jun 17, 2020 at 10:46 AM Guilherme Carvalho <gc...@gmail.com>
wrote:

> Hello, guys, i´m using Guacamole 1.1.0 on a Ubuntu 18.04, i have one
> installation on my company working perfectly, but the another installation
> on my client i have a Kernel Panic 2 a 3 times per day, that last line
> before the server crash is this:
>
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   15.349251] NET: Registered
> protocol family 40
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.424554] vmxnet3 0000:03:00.0
> ens160: intr type 3, mode 0, 9 vectors allocated
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   20.425990] vmxnet3 0000:03:00.0
> ens160: NIC Link is Up 10000 Mbps
> Jun 17 11:33:37 srv-ckg-app-16 kernel: [   24.337831] new mount options do
> not match the existing superblock, will be ignored
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
> callbacks suppressed
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]:
> segfault at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312963] show_signal_msg: 10
> callbacks suppressed
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [  447.312968] guacd[2835]:
> segfault at 0 ip 0000000000000000 sp 00007fe622ffcb18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:52:24 srv-ckg-app-16 kernel: [ 1152.479584] guacd[6386]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:58:35 srv-ckg-app-16 kernel: [ 1523.979631] guacd[7643]:
> segfault at 0 ip 0000000000000000 sp 00007fe5adffab18 error 14 in
> guacd[55eda1436000+7000]
>
> i saw the server is offline on 12:00:00 than, it return on 12:11.
>
> Anybody know what could be this segfaults?? How fix this?
>

To determine where the segfault is occurring, you will need to run things
under gdb and obtain a backtrace. That said, if you are also seeing a
kernel panic, I think it's more likely that the problem causing the kernel
panic is resulting in the segfault and not the other way around. I would
not expect a segfault within *any* userspace process to cause a kernel
panic.

- Mike