Are other users experiencing this same issue? Should I open a bug report? Michael Barkdoll
On Fri, May 3, 2019 at 4:32 PM Michael Barkdoll <[email protected]> wrote: > Here is one more scenario that I thought was interesting: > > machines: m1, m2, m3 > vms: s1, s2 (in balancing connection group) > > m1 => user test => connectgrp => s1 > m2 => user test2 => connectgrp => s2 > m2 => user test2 => logoff s2 > m3 => user test3 => connectgrp => s2 > m3 => user test3 => logoff s2 > m2 => user test2 => connectgrp => s2 > > # Logoff s1, (s2 is still active on m2) > m1 => user test1 => logoff s1 > m3 => user test3 => connectgrp => > Connection Error: This connection is currently in use, and concurrent > access to this connection is not allowed. Please try again later. > > Ok, that was expected from my previous experience, but now logoff the last > active session on m2: > m2 => user test2 => logoff s2 > > Now attempt to reconnect with m3, you'd think you'd get s1 with least > number of connection balancing, but no its s2 when it works. > Wait 15 second (for api sync?) > m3 => user test3 => connectgrp => s2 > > Now attempt to connect m2, > m2 => user test2 => connectgrp => > Connection Error: This connection is currently in use, and concurrent > access to this connection is not allowed. Please try again later. > > Attempt to connect m1, > m1 => user test => connectgrp => s1 (works) > > I have stickiness enabled on the nginx could that be related? > > https://github.com/michaelbarkdoll/guacamole-reverse-proxy-nginx/blob/master/nginx.conf > > Michael Barkdoll > > > On Fri, May 3, 2019 at 4:13 PM Michael Barkdoll <[email protected]> > wrote: > >> m1 => user test => connectgrp => s1 >> m2 => user test2 => connectgrp => s2 >> m3 => user test3 => connectiongrp => Expectedly fails (all vms are used) >> m2 => user test2 => logoff s2 >> m3 => user test3 => connectgrp => s2 >> m3 => user test3 => logoff s2 >> m2 => user test2 => connectgrp => s2 >> >> Everything looks good right? But, now if I disconnect from s1 on m1's >> user test things get wanky. >> >> m1 => user test1 => logoff s1 >> m3 => user test3 => connectgrp => >> Connection Error: This connection is currently in use, and concurrent >> access to this connection is not allowed. Please try again later. >> m3 => user test3 => connectgrp => Reconnect link (nothing, wait 15sec, >> nothing) >> m3 => user test3 => connectgrp => Click Home, Wait 15sec >> m3 => user test3 => connectgrp => >> Connection Error: This connection is currently in use, and concurrent >> access to this connection is not allowed. Please try again later. >> >> [Optionally, I should note: If I try here to reconnect with >> m1 => user test => connectgrp => s1 (that user connection still works for >> that particular machine) >> m1 => user test => loggoff s1] >> >> m3 => user test3 => logoff >> m3 => user test3 => login >> m3 => user test3 => connectgrp => s1 (now works) >> >> Also, I'm using an nginx reverse proxy with ip_hash load balancing >> against two different guacamole tomcat frontends, but all the machines have >> a separate unique ip address, so I don't think it would interfere. >> >> Michael Barkdoll >> >> >> On Fri, May 3, 2019 at 3:47 PM Michael Barkdoll <[email protected]> >> wrote: >> >>> Thanks so much for all the feedback, such a great community here. >>> >>> > If you wait ~15 seconds, does it allow you to connect? >>> No >>> >>> > On the Guacamole server index.html page I added a delete session >>> cookies on >>> refresh or browser close forcing connections to re-authenticate, this >>> works >>> like a charm for our ondemand environment. >>> >>> Yes, if I log out and back in things suddenly work, so something appears >>> to be related to the index.html page. >>> >>> Here is what concerns me: >>> >>> I have a balancing connection group with 2 VM's inside of it s1 and s2. >>> I'm now using three different machines (m1, m2, m3), one uses chrome with >>> that stupid shared profile stuff. The other two are firefox no profile >>> sharing, separate machines, etc... >>> >>> m1 => user test => connectgrp => s1 >>> m2 => user test2 => connectgrp => s2 >>> m3 => user test3 => connectiongrp => Expectedly fails (all vms are used) >>> m2 => user test2 => logoff s2 >>> m3 => user test3 => connectgrp => s2 >>> m3 => user test3 => logoff s2 >>> m2 => user test2 => connectgrp => s2 >>> >>> Everything looks good right? But, now if I disconnect from s1 on m1's >>> user test things get wanky. >>> >>> m1 => user test1 => logoff s1 >>> m3 => user test3 => connectgrp => >>> Connection Error: This connection is currently in use, and concurrent >>> access to this connection is not allowed. Please try again later. >>> m3 => user test3 => connectgrp => Reconnect link (nothing, wait 15sec, >>> nothing) >>> m3 => user test3 => connectgrp => Click Home, Wait 15sec >>> m3 => user test3 => connectgrp => >>> Connection Error: This connection is currently in use, and concurrent >>> access to this connection is not allowed. Please try again later. >>> >>> m3 => user test3 => connectgrp => logoff >>> m3 => user test3 => connectgrp => login >>> m3 => user test3 => connectgrp => connectgrp => s1 (now works) >>> >>> Michael Barkdoll >>> >>> >>> On Fri, May 3, 2019 at 3:23 PM sciUser <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> In order to understand whats happening here, one will need to >>>> understand how >>>> incognito mode works v.s. normal browser operations. >>>> >>>> Chrome incognito: Will not save any cookies, credentials, links or >>>> history >>>> and deactivates extensions. So when you close the incognito browser all >>>> logged in session are gone. >>>> >>>> Chrome guest mode: Will give you a blank profile to anyone who is >>>> temporarily using Chrome. This to is like incognito mode but you can not >>>> change Chrome settings. >>>> >>>> Chrome normal mode: Will cache cookies, retain login credentials, >>>> session >>>> information and remember history. >>>> >>>> I am betting dollars to donuts that your sessions are conflicting in >>>> both >>>> chrome and guacamole server.. >>>> >>>> You should test this with Firefox and Chrome so the sessions are truly >>>> isolated. >>>> >>>> On the Guacamole server index.html page I added a delete session >>>> cookies on >>>> refresh or browser close forcing connections to re-authenticate, this >>>> works >>>> like a charm for our ondemand environment. >>>> >>>> Hope this helps >>>> >>>> Thank You >>>> >>>> >>>> >>>> -- >>>> Sent from: >>>> http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ >>>> >>>
