Ah, okay, I left RECORDING NAME empty per the screenshot in this section:
https://guacamole.apache.org/doc/gug/recording-playback.html#option-1-using-a-subdirectory-named-with-the-history-uuid-recommended

It now works.

On Tue, May 21, 2024 at 2:31 PM Aaron Newsome <[email protected]>
wrote:

> Not sure what's going wrong with your setup, but here's mine.
>
> In my guacd container, you see the mount:
> root@guacd:~# mount | grep guac
> 192.168.112.65:/mnt/data/k8s/guacamole-guacamole-recordings-pvc-bc32b003-0e88-485b-90bc-3cd62184d5a0
> on /var/lib/guacamole/recordings type nfs4
> (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.112.233,local_lock=none,addr=192.168.112.65)
>
> In my connection profile, I have the parameters:
> RECORDING PATH: ${HISTORY_PATH}/${HISTORY_UUID}
> RECORDING NAME: 172_Alma 92_${GUAC_DATE}_${GUAC_TIME}
> Automatically create recording path: CHECKED
>
> When connecting, you see the "Recording of session ..." in the guacd log:
> guacd[1]: INFO: Creating new client for protocol "rdp"
> guacd[1]: INFO: Connection ID is "$7356cb70-a6c4-40c6-8115-9e57f4139b50"
> guacd[9127]: INFO:      Security mode: Negotiate (ANY)
> guacd[9127]: INFO:      Resize method: none
> guacd[9127]: INFO:      No clipboard line-ending normalization specified.
> Defaulting to preserving the format of all line endings.
> guacd[9127]: INFO:      User "@e7535600-a26e-43e8-9ebd-7febf2dc7582"
> joined connection "$7356cb70-a6c4-40c6-8115-9e57f4139b50" (1 users now
> present)
> *guacd[9127]: INFO:      Recording of session will be saved to
> "/var/lib/guacamole/recordings/962d8ac7-07c9-381c-afb8-5887b8a939f2/172_Alma
> 92_20240521_212122".*
> guacd[9127]: INFO:      Loading keymap "base"
> guacd[9127]: INFO:      Loading keymap "en-us-qwerty"
> guacd[9127]: INFO:      Accepted format: 16-bit PCM with 2 channels at
> 44100 Hz
> guacd[9127]: INFO:      Accepted format: 16-bit PCM with 2 channels at
> 22050 Hz
> guacd[9127]: INFO:      Connected to RDPDR 1.12 as client 0xf6dd9734
> guacd[9127]: INFO:      RDPDR user logged on
>
> After the RDP session completes, I see the screen recording in Settings ->
> History. The session recording can be played back in the browser. I also
> use ffmpeg scripts to export the recordings to mp4 when needed.
>
> If you exec into your docker container and go to the recordings directory,
> what do you see? While exec'd into the container, can you write to the
> recordings directory? Can you show a guacd log entry when you connect to a
> profile with the parameters configured?
>
> Hopefully something here will help.
>
> Thanks, Aaron
>
>
> On Tue, May 21, 2024 at 3:58 PM Johnny Lee <[email protected]>
> wrote:
>
>> /var/lib/guacamole/recordings is mounted in both the guacamole and guacd
>> container, it is set up as a shared volume between the containers.
>>
>>
>>
>> On Tue, May 21, 2024 at 1:55 PM Aaron Newsome <[email protected]>
>> wrote:
>>
>>> Did you mount the volume in the guacd container or the guacamole
>>> container?
>>>
>>> On Tue, May 21, 2024 at 3:36 PM Johnny Lee <[email protected]>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I'm working on exploring Guacamole for a recording of remote devices
>>>> use case.
>>>>
>>>> I've setup Guacamole following these instructions:
>>>> https://guacamole.apache.org/doc/1.5.0/gug/guacamole-docker.html
>>>>
>>>> I've installed the recording extension per these instructions. I see an
>>>> affirmative log from the server saying the extension is loaded. I've added
>>>> a shared mounted volume for the recording path
>>>> /var/lib/guacamole/recordings and tested r/w manually via docker exec.
>>>>
>>>> 20:08:51.598 [localhost-startStop-1] INFO
>>>>  o.a.g.extension.ExtensionModule - Extension "Session Recording Storage"
>>>> (recording-storage) loaded.
>>>>
>>>> However, I still do not see recordings appear for historical sessions,
>>>> I do not find files in the recording path. In my guacd logs, there are also
>>>> no logs indicating recording saving permissions issues.
>>>>
>>>> What's the best path to debug further?
>>>>
>>>> Best,
>>>> Johnny
>>>>
>>>

Reply via email to