Hello Gabriel, hello Nick & Mike,
I'm also one the users which had problems with disconnects in an earlier
release (guacd 1.4.0). There were also core dumps with earlier releases
(1.2.0) in a different connection which I can't remember anymore (as far
as I recall for that I also created a ticket). At that time I opened a
detailed ticket and provided core dumps and backtraces.
I don't know if got this already but for generating core dumps you have
to prepare your system. Normally, per default, writing core dumps to
disk is disabled (RLIMIT_CORE). Before you start a process, here guacd,
you have to enable it. So type ulimit -a (for all limits or -c, just
seeing the core dump limit) in your shell:
$ ulimit -a
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 126355
max locked memory (kbytes, -l) 4070536
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 126355
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
As you can see "0" meaning max. allowed core file size is 0 bytes. Type:
$ ulimit -c unlimited
for unlimited core file size. Start here in this updated environment guacd.
You can also, before you start guacd, define - globally - the path where
the dumps are written to and with macros the specification of the file
name. Type
$ man core
for details.
I'm really keen on hearing if the core dump problems are solved somewhen
since I experienced core dumps of guacd in different connections not
only what is discussed here. There were also some on weak connections
with small bandwidth in connection with audio (microphone).
Also intresting to hear to rebuild the FreeRDP library - did it help?
I hope, I could help you a little bit.
Hasta la próxima.
Jorge
On 07.06.23 19:25, Gabriel Huerta Araujo wrote:
I found this log information (syslog)
Jun 7 11:14:50 tmxqrocnsG5 guacd[156163]: RDP server closed/refused
connection: Manually logged off.
Jun 7 11:14:50 tmxqrocnsG5 guacd[156163]: guacd[156163]:INFO:#011RDP server
closed/refused connection: Manually logged off.
Jun 7 11:14:50 tmxqrocnsG5 guacd[156163]: Internal RDP client disconnected
Jun 7 11:14:50 tmxqrocnsG5 guacd[156163]: guacd[156163]:INFO:#011Internal RDP
client disconnected
Jun 7 11:14:50 tmxqrocnsG5 kernel: [205223.091624] guacd[156169]: segfault at
10 ip 00007fa1fc3e3622 sp 00007f9f92573c80 error 4 in
libguac-client-rdp.so.0.0.0[7fa1fc3d1000+1a000]
Jun 7 11:14:50 tmxqrocnsG5 kernel: [205223.091653] Code: 00 be 03 00 00 00 48 89 ef
e8 8a e9 fe ff b8 01 00 00 00 e9 7a ff ff ff 53 48 8b 07 48 89 fb 48 89 de 48 8b 40
10 48 8b 40 20 <48> 8b 78 10 e8 25 e9 fe ff 8b 43 18 85 c0 74 0e 31 c0 5b c3 66
2e
Jun 7 11:14:50 tmxqrocnsG5 guacd[568]: Connection
"$fcf2766d-53e1-40da-9874-8fb9cd08e2e1" removed.
Jun 7 11:14:50 tmxqrocnsG5 guacd[568]: guacd[568]:INFO:#011Connection
"$fcf2766d-53e1-40da-9874-8fb9cd08e2e1" removed.
Jun 7 11:15:00 tmxqrocnsG5 guacd[568]: Creating new client for protocol "rdp"
Jun 7 11:15:00 tmxqrocnsG5 guacd[568]: guacd[568]:INFO:#011Creating new client for
protocol "rdp"
Jun 7 11:15:00 tmxqrocnsG5 guacd[568]: Connection ID is
"$205fff34-792b-43b1-9d4c-c5a53af7edc3"
Jun 7 11:15:00 tmxqrocnsG5 guacd[568]: guacd[568]:INFO:#011Connection ID is
"$205fff34-792b-43b1-9d4c-c5a53af7edc3"
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: FreeRDP initialization may fail: The current
user's home directory ("/usr/sbin") is not writable, but FreeRDP generally
requires a writable home directory for storage of configuration files and certificates.
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: guacd[157660]: WARNING:#011FreeRDP
initialization may fail: The current user's home directory ("/usr/sbin") is not
writable, but FreeRDP generally requires a writable home directory for storage of
configuration files and certificates.
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: guacd[157660]:INFO:#011No security
mode specified. Defaulting to security mode negotiation with server.
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: guacd[157660]:INFO:#011Resize
method: none
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: guacd[157660]:INFO:#011No clipboard
line-ending normalization specified. Defaulting to preserving the format of all
line endings.
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: guacd[157660]:INFO:#011User
"@36c63a3c-96eb-452d-bef9-c8490c5cb12f" joined connection
"$205fff34-792b-43b1-9d4c-c5a53af7edc3" (1 users now present)
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: No security mode specified.
Defaulting to security mode negotiation with server.
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: Resize method: none
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: No clipboard line-ending
normalization specified. Defaulting to preserving the format of all line
endings.
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: User "@36c63a3c-96eb-452d-bef9-c8490c5cb12f"
joined connection "$205fff34-792b-43b1-9d4c-c5a53af7edc3" (1 users now present)
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: Loading keymap "base"
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: Loading keymap "en-us-qwerty"
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: guacd[157660]:INFO:#011Loading keymap
"base"
Jun 7 11:15:00 tmxqrocnsG5 guacd[157660]: guacd[157660]:INFO:#011Loading keymap
"en-us-qwerty"
Jun 7 11:15:02 tmxqrocnsG5 guacd[157660]: Connected to RDPDR 1.12 as client
0x0009
-Gabriel
-----Mensaje original-----
De: Gabriel Huerta Araujo
Enviado el: miércoles, 7 de junio de 2023 10:51 a. m.
Para:user@guacamole.apache.org
Asunto: RE: guacd error segfault in libguac-client-rdp.so.0.0.0
If you can find the coredump file and do the backtrace on that file, that would
be helpful, so we can see where the segfault is actually happening.
These files which are their file extensión?
I tried to identify segfault (core files) and I did not find them
for i in `find / -name core -print 2>/dev/null` do
file $i | grep "core file" >/dev/null
if [ $? -eq 0 ]; then
file $i
fi
done
/root/core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style,
from '/usr/lib/vmware-tools/sbin64/vmtoolsd -n vmusr', real uid: 0, effective
uid: 0, real gid: 0, effective gid: 0, execfn:
'/usr/lib/vmware-tools/sbin64/vmtoolsd', platform: 'x86_64'
Is there any another way to identify these segfaults which are mentioned in
/var/log/message file? To check which is their problema cause.
Jun 7 10:33:30 tmxqrocnsG5 kernel: [202742.808204] guacd[146842]: segfault at
10 ip 00007fa1fc3e3622 sp 00007fa00f66dc80 error 4 in
libguac-client-rdp.so.0.0.0[7fa1fc3d1000+1a000]
Jun 7 10:33:30 tmxqrocnsG5 kernel: [202742.808310] Code: 00 be 03 00 00 00 48 89 ef
e8 8a e9 fe ff b8 01 00 00 00 e9 7a ff ff ff 53 48 8b 07 48 89 fb 48 89 de 48 8b 40
10 48 8b 40 20 <48> 8b 78 10 e8 25 e9 fe ff 8b 43 18 85 c0 74 0e 31 c0 5b c3 66
2e
-Gabriel
---------------------------------------------------------------------
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
