Pulse suck in Connecting.. state

[zyz101z]

I recently upgraded pulse to 5.0R11.0. Users keep running into an issue when they connect through Pulse where it sits at Connecting and never connects. On the appliance I see the user connected and I show an IP address. If the user tries several times occasionally it will get past "Connecting" and onto Secure connection and then it connects fine. However, most of time time it gets stuck. If the user connects via a browser and not through the Pulse client they seem to get better results. Any ideas? Below is all i see in the debug.log.



00136,09 2015/10/13 16:12:10.484 3 ub53005 Pulse.exe Pulse p5864 t2C0 JamConnectionModel.cpp:689 - 'JamUI' Connection Status: Connecting
00228,09 2015/10/13 16:12:10.484 3 ub53005 Pulse.exe Pulse p5864 t2C0 JamConnectionModel.cpp:718 - 'JamUI' TNC data received from status ID:5, bRemediation:0, bAutoremediation 0, Policysize:0 (ive:fca48e79-3bf8-42e8-8c6b-2e89c44b09f2)
00381,09 2015/10/13 16:12:10.484 3 SYSTEM dsAccessService.exe ConnectionManager p5312 t25E8 ConnectionEntry.cpp:1079 - 'ConnectionManager' onNetworkChange(ive:fca48e79-3bf8-42e8-8c6b-2e89c44b09f2), policy result: -1, manual connect state: 1, hasIp: 1, can connect: 0, can disconnect: 1, machineSuspended: 0, connSuspended: 0, correct context: 1, connIdentity: user, state kStateConnecting
00204,09 2015/10/13 16:12:10.562 3 ub53005 Pulse.exe Pulse p5864 t2C0 JamConnectionModel.cpp:582 - 'JamUI' Notification of updated or new connection from store: '' (userdata:fca48e79-3bf8-42e8-8c6b-2e89c44b09f2)
00204,09 2015/10/13 16:12:10.625 3 ub53005 Pulse.exe Pulse p5864 t2C0 JamConnectionModel.cpp:582 - 'JamUI' Notification of updated or new connection from store: '' (userdata:fca48e79-3bf8-42e8-8c6b-2e89c44b09f2)
00164,09 2015/10/13 16:12:11.717 3 SYSTEM dsAccessService.exe dsAccessService p5312 t104C accessPluginLoader.cpp:617 - 'AccessService' plugin eapService, unloading(0x0)...
00161,09 2015/10/13 16:12:11.717 3 SYSTEM dsAccessService.exe dsAccessService p5312 t104C accessPluginLoader.cpp:335 - 'AccessService' plugin eapService, stopping(0)...
00157,09 2015/10/13 16:12:11.717 3 SYSTEM dsAccessService.exe dsAccessService p5312 t104C accessPluginLoader.cpp:388 - 'AccessService' plugin eapService has stopped
00161,09 2015/10/13 16:12:11.717 3 SYSTEM dsAccessService.exe dsAccessService p5312 t104C accessPluginLoader.cpp:291 - 'AccessService' plugin eapService, cleaning up...
00165,09 2015/10/13 16:12:11.717 3 SYSTEM dsAccessService.exe dsAccessService p5312 t104C accessPluginLoader.cpp:322 - 'AccessService' plugin eapService has been cleaned up
00156,09 2015/10/13 16:12:11.717 3 SYSTEM dsAccessService.exe dsAccessService p5312 t104C accessService.cpp:415 - 'AccessService' notify plugin eapService unloaded
00209,09 2015/10/13 16:12:46.777 3 SYSTEM dsAccessService.exe dsAccessService p5312 t104C ResourceLogger.cpp:42 - 'AccessService' Memory usage: WSS=12.9 MB, Paged=148.0 KB, Nonpaged=33.7 KB, pagefile=9.9 MB, TLS=0x28

[kita]

It is hard to say, but this may be related to a bug we found in 8.0R11. To root cause the issue, we would need some logging from the PCS device itself. Please reach out to your PCS administrator to open a tech support case to further help root cause the issue.

[PulseUser]

Can you please help us determine the bug. We've reported this for a couple of months, and have had 2 different support cases open, and have gotten zero help. We've sent in soooo may logs that it isn't even funny.

We are attempting to upgrade to the latest version of 8.1. Do you know if that fixes the issue?

Thank you.

[flipPipe]

Hi PulseUser,

We use the 8.1R4 and we also have the same problem.

[zyz101z]

We worked with Support and it appeared to be a bug in the 8.0R11 version we were running. We upgraded to 8.0R13 and the issue went away.

[PulseUser]

Ugh. I hope 8.1R4 doesn't have the issue. We are in the middle of piloting it and need Windows 10 support too.

Any details you can provide kita?

Thank you.

[flipPipe]

Hi zyz101z,

Do you know the PR number?

[zyz101z]

I don't have a PR#. They never provided me one. This was the detailed information provided.

"The cause of the issue was in the setup of the data channel for the connection between the dsagentd and web socket processes. If the message to send file descriptor from dsagentd to web was queued it would send the message without a NULL terminator. The server side fix is available in 8.0R13."

[PulseUser]

Would you mind sharing your case number so that we can provide to support? We are trying to see if this is resolved in 8.1R6, but they still haven't been able toe determine the cause in our case.

[zyz101z]

2015-1013-5111