Nick, I agree https://issues.apache.org/jira/browse/GUACAMOLE-1126 looks in the ballpark.
I have no personal investment in the implementation, I would simply like the endless server pings to stop so we can more easily monitor application logs, have less "errors" in our logs, and reduce the baseline load on the servers. We do somewhat inflict this problem on ourselves (I think), because we shut down the VMs people are using, but we do so because we reasonably believe the user is idle and wasting resources... I suppose if there was a "guacamole session time limit" that could be set when the user initially authenticates, and they get kicked out and forced to re-authenticate at that point (or at least click a button to extend their session).... that would resolve my issue too... as I understand the auth process now, once they have a guacamole-guacd session successfully established, that seems to be almost entirely independent of their user account or the connection's properties... I have not tried it, but I suspect you could delete either of them, and guacamole would still let the user continue their current session. -Lee On Wed, Jun 1, 2022 at 5:18 AM Jürgen Kuri <[email protected]> wrote: > Suggestion: > > 1) keep endless reconnect as default > > 2) have two connection specific and / or global parameter: > a. number of retries > b. retry interval > > 3) if we have these parameters as global and on connection level, global > is overwritten for specific connection if defined > > El 31.05.22 a las 22:44, Lee Doughty escribió: > > Hello Guacamole Community, > > > > I tried asking this a few weeks ago, but it looks like there was not a > lot of traction on this idea.. but I wanted to try one more time before I > gave up on it. > > > > I think it would be a great feature to stop auto-reconnect attempts that > are simply not connecting after several dozen attempts. I've seen in our > logs that some users hit the "Reconnect" button or otherwise get into a > reconnect loop, then leave the tab open for hours *or days*. This results > in our guacamole server getting a ping every minute or so from a user > trying to connect to a VM that is not available, and they just leave it > retrying over and over again. > > > > It would be nice to at least require user interaction to resume the > connection attempts... So users have to return to the tab every N attempts > to restart the countdown, instead of the current never-ending loop... I'm > not suggesting any value for N... because any reasonable value would be > nice over infinite. My record was somewhere in the ballpark of 7,000 > attempts (5 days) before the user was kind enough to close the tab and stop > poking our Guacamole server. > > > > Is this something that can make it into an upcoming Guacamole release? > > > > -Lee > > > -- > Jürgen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
