On Thu, Jun 26, 2025 at 10:12 AM Horváth Csaba <[email protected]> wrote:
> Hi, > > Sry, i didn't know :) > > root@homeserver:~# /usr/local/sbin/guacd -f -b 127.0.0.1 -L debug -l > 4822 -p /tmp/guacd.pid & > [2] 1959395 > root@homeserver:~# guacd[1959395]: INFO: Guacamole proxy daemon > (guacd) version 1.6.0 started > guacd[1959395]: DEBUG: Unable to bind AF_INET socket to host > 127.0.0.1, port 4822: Address already in use > guacd[1959395]: ERROR: Unable to bind socket to any addresses. > Can you make sure that there isn't another guacd process running? This indicates that something is already listening on that address. > guacd[1958670]: INFO: User "@7c605e60-dc61-4555-95bf-8fafa54c7552" > disconnected (0 users remain) > guacd[1958670]: INFO: Last user of connection "�qt�#" disconnected > guacd[1958670]: DEBUG: Requesting termination of client... > double free or corruption (out) > guacd[1958558]: INFO: Connection > "$a0e6b794-e039-4b49-9801-99e9e85f1b20" removed. > guacd[1958558]: DEBUG: Unable to request termination of client > process: No such process > Can you also look for any sign of segmentation faults or other signs the guacd process is dying? > guacd[1958558]: DEBUG: All child processes for connection > "$a0e6b794-e039-4b49-9801-99e9e85f1b20" have been terminated. > guacd[1958558]: INFO: Creating new client for protocol "ssh" > guacd[1958558]: INFO: Connection ID is > "$f87a8342-b776-46aa-8525-4cde6684096d" > guacd[1959507]: DEBUG: Processing instruction: size > guacd[1959507]: DEBUG: Processing instruction: audio > guacd[1959507]: DEBUG: Processing instruction: video > guacd[1959507]: DEBUG: Processing instruction: image > guacd[1959507]: DEBUG: Processing instruction: timezone > guacd[1959507]: DEBUG: Processing instruction: name > guacd[1959507]: INFO: User "@b2c71d6a-af9d-4a12-8e28-a035bdfee8cb" > joined connection "�Qt�#" (1 users now present) > guacd[1959507]: DEBUG: Client is using protocol version "VERSION_1_5_0" > > Something odd is definitely going on in your environment. Please start by making sure your environment is "clean" - stop all existing guacd processes and containers, remove any old versions of guacd, and build and start 1.6.0, making sure you're not getting any error messages like the ones above. Then try the SSH connection, again, and see what happens - if it's still failing, report that back, and look for segfaults, core dumps, etc., and get the stack trace for those. -Nick
