Logoff - not detaching AS or WV

[cyberfed2727]

We have an odd scenario. Running a fresh install of AV 2.11

Win7 VDI Linked clones w/Horizon View 6.2.2

Everything appears to work fine when a user logs off, however we discovered if a user disconnects and leaves a stale session things go sideways.

We configured Horizon View to logoff users (thus triggering a dismount of AS and WV) stale sessions after 5 minutes.

Horizon View appears to do its job, logging off the user and making the VDI available. However that logoff process triggered by View is not causing AV to dismount. A review of the AV agent log on the VDI at the time of dismount reveals what I believe is the issue:

User logout URL: /user-logout?name=svservice&uuid=423321d7-aae0-1cf1-650c-0c679f715bf8&status=0&osver=6.1.7601&sp=1.0&suite=256&product=1&arch=9&proc=1&agentver=2.11.0.83U&username=XXXX&domain=XXX&userdomain=XXX&workstation=XXXX&machinesid=S-1-5-21-457945878-1175663176-964313020

[2016-06-24 17:31:05.261 UTC] [svservice:P916:T4408] [0] Connecting to FQDN OF OUR AV MANAGERt:443 using HTTPS (attempt 1)

[2016-06-24 17:31:05.308 UTC] [svservice:4408] HttpInitializeRequest: WinHttpSendRequest failed (error 2148074273)

[2016-06-24 17:31:05.308 UTC] [svservice:P916:T4408] Message: "Connection Error (Manager "FQDN OF OUR AV MANAGER"):

Unable to contact App Volumes Manager." (hToken FFFFFFFFFFFFFFFF)

[2016-06-24 17:31:05.308 UTC] [svservice:P916:T4408] RunExecutableAsUser: Path "C:\Program Files (x86)\CloudVolumes\Agent\svservice.exe"

[2016-06-24 17:31:05.308 UTC] [svservice:P916:T4408] RunExecutableAsUser: CommandLine svservice.exe message "Connection Error (Manager "FQDN OF OUR AV MANAGER"):

Unable to contact App Volumes Manager."

[2016-06-24 17:31:05.323 UTC] [svservice:4408] RunExecutableAsUser failed: no session available

[2016-06-24 17:31:05.323 UTC] [svservice:4408] User logout over HTTP failed

[2016-06-24 17:31:05.323 UTC] [svservice:P916:T4408] HttpLogoutWorker: failed (user logout)

Before you ask yes ports 443 and 80 have been verified as open. After Horizon View shows the VDI as available after logging the user off AV manager still shows the stack and writable volume attached.

Thoughts?? Suggestions?

[hockeyguyin714]

Make sure ports 3001-3004 are also available and running.

The message is distinct that App Volumes Agent did not reach App Volumes Manager.  Are you using a load balancer for App Volumes Manager?

[Smoke14]

Try this and see if it helps. We have a similar problem with the web client, but when the user uses the Guest OS Logout, the view session stays in a disconnected state and the AS never release. But I enabled this in my AS templates and it seems to have worked as a workaround for me now, till I can get time to put a call into support.

RebootAfterDetach = 1 / REG_DWORD, automatically reboot the system after a user logs off. If it solves you problem, you will need to place an SR to get a real resolution.

[virtualdars]

Hi,

What kind of Settings have your pool, dedicated or Floating?

Where have dedicated pool with the sale problem. We opened a case in vmware, but not found solution.

[Ray_handels]

Hey CyberFed,

Have you ever find a solution to this issue?? We are seeing the exact same thing here.

After restarting the Appvolumes managers it works again. We are using an F5 in front of both of our Appvolumes managers.

[cyberfed2727]

No we never ended up finding a solution. We ran into other problems as well as stack not being mounted on login at random times. No reason we could pin down. Some days it would work great no issues other days it would completely choke on itself.

We were just doing a proof of concept in our lab. After all the issues in a small test we decided not to pursue it any further. We may revisit it again in the next 2 months or so when we deploy Horizon 7 on some fresh hardware and then maybe try again with App Volumes 3.x

FYI

No load balancers, using floating pools.