You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Adrian Owen <ad...@eesm.com> on 2020/01/10 17:49:22 UTC

Session recording behaviour

I set session to record to 'mysession'  file

If there is a break in session, Gucamole will attempt to reconnect and if successful a new streaming file is created mysession_1

And so on _2, _3 ...


I belive this is how it works.  Is there any documentation on this behahior?

And what is the easeist way to manually cause a session break to simulate the scenario?

Many thanks, Adrian

Re: Session recording behaviour

Posted by Mike Jumper <mj...@apache.org>.
On Fri, Jan 10, 2020, 10:19 Adrian Owen <ad...@eesm.com> wrote:

> Thanks Mike.
>
> 1 more. Customer said they want to run sessions for 30 days recording
> video.
>
> That will result is a massive file.
>

If the session has a lot of activity over that time, yes. If it's just
generally sitting idle, the recording may not be very large at all,
consisting mostly of empty or near-empty frames.

If you convert the recording to standard video, it will likely be enormous,
yes.

Is there a way for me to remotely bump the session by running something on
> guacamole server so:
>
>
>
> 1.       Cause Session reconnect
>
> 2.       It starts streaming again (but mysession file exists)
>
> 3.       So it starts writing mysession_1
>
> 4.       I can then process mysession with guacenc and delete it.
>
>
>
> 5.       This would run every … 2 hours …
>

No. You can remotely kill an active connection, but you cannot force it to
reconnect. Automatic reconnect will occur for cases where there is an
apparent transient issue that will likely be resolved by a reconnect. It
will not occur if the disconnect is due to admin intervention.

- Mike

RE: Session recording behaviour

Posted by Adrian Owen <ad...@eesm.com>.
Thanks Mike.

1 more. Customer said they want to run sessions for 30 days recording video.

That will result is a massive file.

Is there a way for me to remotely bump the session by running something on guacamole server so:


1.       Cause Session reconnect

2.       It starts streaming again (but mysession file exists)

3.       So it starts writing mysession_1

4.       I can then process mysession with guacenc and delete it.


5.       This would run every … 2 hours …

Adrian

From: Mike Jumper [mailto:mjumper@apache.org]
Sent: 10 January 2020 17:59
To: user@guacamole.apache.org
Subject: Re: Session recording behaviour

On Fri, Jan 10, 2020, 09:49 Adrian Owen <ad...@eesm.com>> wrote:
I set session to record to ‘mysession’  file
If there is a break in session, Gucamole will attempt to reconnect and if successful a new streaming file is created mysession_1
And so on _2, _3 …

Yes, but this has nothing to do with reconnecting. A sequential numeric suffix is added if a file with that name already exists.

The suffix will be .1, .2, etc.

I belive this is how it works.  Is there any documentation on this behahior?

https://guacamole.apache.org/doc/gug/configuring-guacamole.html#rdp-recording

"Guacamole will never overwrite an existing recording. If necessary, a numeric suffix like ".1", ".2", ".3", etc. will be appended to NAME to avoid overwriting an existing recording. If even appending a numeric suffix does not help, the session will simply not be recorded."

And what is the easeist way to manually cause a session break to simulate the scenario?

Manually disconnect and click "reconnect", or reload the page.

- Mike


Re: Session recording behaviour

Posted by Mike Jumper <mj...@apache.org>.
On Fri, Jan 10, 2020, 09:49 Adrian Owen <ad...@eesm.com> wrote:

> I set session to record to ‘mysession’  file
>
> If there is a break in session, Gucamole will attempt to reconnect and if
> successful a new streaming file is created mysession_1
>
> And so on _2, _3 …
>

Yes, but this has nothing to do with reconnecting. A sequential numeric
suffix is added if a file with that name already exists.

The suffix will be .1, .2, etc.

I belive this is how it works.  Is there any documentation on this behahior?
>

https://guacamole.apache.org/doc/gug/configuring-guacamole.html#rdp-recording

"Guacamole will never overwrite an existing recording. If necessary, a
numeric suffix like ".1", ".2", ".3", etc. will be appended to *NAME* to
avoid overwriting an existing recording. If even appending a numeric suffix
does not help, the session will simply not be recorded."

And what is the easeist way to manually cause a session break to simulate
> the scenario?
>

Manually disconnect and click "reconnect", or reload the page.

- Mike