Junos Pulse broken in MacOS Sierra

App & System Services Core OS Beta macOS

Created Jul ’16

Replies 47

Boosts 0

Views 63k

Participants 37

Looks like MacOS Sierra broke Junos Pulse (VPN client). I launch a connection and it wipes out my save connections. Does not connect. I tried to add a new connection and it's not able to connect to the service. Anyone seeing this?

I see this in the pulse log:

**************************************************************************************

00132,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:420 - '***' Access Service

00115,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:421 - '***'

00146,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:422 - '***' Thu Jul/07/2016 09:30:08 PDT

00136,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:423 - '***' Build Version: 0

00136,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:424 - '***' Product Version: 2

00149,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:425 - '***' Operating System: Darwin 16.0.0

00133,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:426 - '***' User Name: root

00200,09 2016/07/07 09:30:08.743 0 root dsAccessService dsAccessService p6812 tA07 dsMacLogserviceApiLib.cpp:427 - '***' **************************************************************************************

00186,09 2016/07/07 09:30:08.743 3 root dsAccessService dsAccessService p6812 tA07 service.mm:79 - 'AccessService' CmdLine: /Applications/Pulse Secure.app/Contents/Plugins/JUNS/dsAccessService

00132,09 2016/07/07 09:30:08.743 3 root dsAccessService dsAccessService p6812 tA07 service.mm:115 - 'AccessService' initializing service...

00132,09 2016/07/07 09:30:08.743 3 root dsAccessService dsAccessService p6812 tA07 service.mm:141 - 'AccessService' initializing service...

00180,09 2016/07/07 09:30:08.744 3 root dsAccessService dsAccessService p6812 tA07 accessService.cpp:83 - 'AccessService' service did not shutdown gracefully, performing recovery tasks...

00155,09 2016/07/07 09:30:08.795 3 root dsAccessService dsAccessService p6812 tA07 accessService.cpp:646 - 'AccessService' performing recovery on plugin TMService

00141,09 2016/07/07 09:30:08.898 3 root dsAccessService dsTMService p6812 tA07 dsTMService.cpp:13 - 'DSTMService' DSTMService::DSTMService() started

00130,09 2016/07/07 09:30:08.898 3 root dsAccessService dsTMService p6812 tA07 dsTMService.cpp:57 - 'DSTMService' onTMRecovery(): started

00139,09 2016/07/07 09:30:09.102 1 MyUser PulseTray Pulse p6464 t1407 DSAccessDoIpc.mm:115 - 'AccessService' Failure to get server port AccessService

00168,09 2016/07/07 09:30:09.102 3 MyUser PulseTray Pulse p6464 t1407 JamConnectionModel.cpp:286 - 'JamUI' Connection to UIModelService plugin failed - service may not be running

00139,09 2016/07/07 09:30:09.103 1 MyUser PulseTray Pulse p6464 t1407 DSAccessDoIpc.mm:115 - 'AccessService' Failure to get server port AccessService

00130,09 2016/07/07 09:30:09.103 3 MyUser PulseTray Pulse p6464 t1407 DialogManager.cpp:191 - 'JamUI' No plugin interface available - rc = 2

And, this is from the System Log

ul 7 09:29:14 MyUser-MacBook-Pro-3 VTDecoderXPCService[6792]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked

Jul 7 09:29:14 MyUser-MacBook-Pro-3 spindump[5342]: Saved memory_resource.diag report for Finder version (null) to /Library/Logs/DiagnosticReports/Finder_2016-07-07-092914_MyUser-MacBook-Pro-3.memory_resource.diag

Jul 7 09:29:18 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (net.pulsesecure.AccessService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jul 7 09:29:18 MyUser-MacBook-Pro-3 ReportCrash[6785]: Saved crash report for dsAccessService[6796] version ??? to /Library/Logs/DiagnosticReports/dsAccessService_2016-07-07-092918_MyUser-MacBook-Pro-3.crash

Jul 7 09:29:28 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (net.pulsesecure.AccessService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jul 7 09:29:28 MyUser-MacBook-Pro-3 ReportCrash[6785]: Saved crash report for dsAccessService[6797] version ??? to /Library/Logs/DiagnosticReports/dsAccessService_2016-07-07-092928_MyUser-MacBook-Pro-3.crash

Jul 7 09:29:37 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.quicklook[6800]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook

Jul 7 09:29:38 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (net.pulsesecure.AccessService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jul 7 09:29:38 MyUser-MacBook-Pro-3 ReportCrash[6785]: Saved crash report for dsAccessService[6801] version ??? to /Library/Logs/DiagnosticReports/dsAccessService_2016-07-07-092938_MyUser-MacBook-Pro-3.crash

Jul 7 09:29:48 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (net.pulsesecure.AccessService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jul 7 09:29:48 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (com.apple.ReportCrash.Root[6803]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash.DirectoryService

Jul 7 09:29:48 MyUser-MacBook-Pro-3 ReportCrash[6803]: Saved crash report for dsAccessService[6802] version ??? to /Library/Logs/DiagnosticReports/dsAccessService_2016-07-07-092948_MyUser-MacBook-Pro-3.crash

Jul 7 09:29:58 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (net.pulsesecure.AccessService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jul 7 09:29:58 MyUser-MacBook-Pro-3 ReportCrash[6803]: Saved crash report for dsAccessService[6804] version ??? to /Library/Logs/DiagnosticReports/dsAccessService_2016-07-07-092958_MyUser-MacBook-Pro-3.crash

Jul 7 09:30:07 MyUser-MacBook-Pro-3 VTDecoderXPCService[6811]: BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked

Jul 7 09:30:08 MyUser-MacBook-Pro-3 com.apple.xpc.launchd[1] (net.pulsesecure.AccessService): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Jul 7 09:30:09 MyUser-MacBook-Pro-3 ReportCrash[6803]: Saved crash report for dsAccessService[6812] version ??? to /Library/Logs/DiagnosticReports/dsAccessService_2016-07-07-093009_MyUser-MacBook-Pro-3.crash

Boost

cvillalta OP

Sep ’16

That version isn't available yet.

CableShark OP

Sep ’16

Same issue with me,

I have upgraded to version 5.2.5(869) and everything works.

Thanks

dtanner OP

Sep ’16

confirmed new version of the pulse client works with Seirra

dtanner OP

Sep ’16

New Version of Pulse works with Seirra.

Version 5.2.5 (869) and above my company is currently using this works fine with Seirra

sksamani OP

Sep ’16

Where can I get the link for download?

wynshaft OP

Sep ’16

I've confirmed that version 5.0.3 works with MacOS Sierra (10.12). The .dmg can be downloaded here: https://www.net.usf.edu/vpn/MacOS/JunosPulse.dmg

krishnithya OP

Sep ’16

Install 5.2.5 and it should work again. You can get it here: https://admin.kuleuven.be/icts/services/extranet/ps-pulse-mac-5-2r5-0-b869-installer.dmg

sulivan22 OP

Sep ’16

Hello all

To solve the problem you have to install the version 5.2.5 (869). I am working with this version.

Regards

esandusky OP

Oct ’16

Pulse 5.2.5 (869) does indeed work, ONLY the first time you connect to a VPN. When you try to Disconnect, the status stays at "Disconnecting" and never completes. If you then try to Connect again, the status stays at "Connect requested" and never completes. My connection entry is not lost like 5.1.x, however, I can't reconnect with Pulse until I Restart my Macbook. Exit from Pulse and re-opening again without a Restart does not fix the issue.

Is anyone else seeing this behavior?

NvrEngh OP

Oct ’16

I just troubleshot this for an end user, a restart is not neccesary. In there case at least, user disconnected her wifi as directed then reconnected to the network this fully closed the tunnel and allowed her to reconnect to the VPN without a restart. Guessing when disconnecting the tunnel isn't fully severed or the bridge isn't fully closed out and disconnecting and reconnecting resolves that issue.

KGaudineer OP

Nov ’16

I am using two different MAC's One IMAC and one MAC Book Pro... Both have been update to OSX Sierra (10.12.1) and Pulse Secure for the most part is not operational on either one. You can connect once with Pulse Secure but once you disconnect any other network access is disrupted until the machine is restarted. Sometimes the wireless can be turned off and then back on but that only works hit or miss. What I have found is that reinstalling the JUNOS Pulse 5.0.3 works consistentantly everytime. Both when starting the VPN and disconnecting the VPN and making other internet connections. Since reinstalling the JUNOS Pulse 5.0.3 I have never had to restart my MAC or Turn off the wireless controller. I have also started rolling with this solution for a few customers who also can't get the Pulse Secure to work on their MACS which have upgraded to Sierra. The only 'gotcha' here is that you need to make sure that you 'CANCEL' out of the nag dialog box telling you there is an upgrade available...

Just out of curosity has anyone been able to get the latest release of Secure Pulse 5.2.5(869) to work on a MAC (more than once) after upgrading to Sierra?

lvanoel OP

Dec ’16

This helped me a lot. Thx. 🙂

tdahbura OP

Dec ’16

I have the Pulse client 5.2.5 (869) installed with Sierra 10.12.2 and it connects fine. However when disconnecting all local TCP services seemed to be non-functional. This includes any normal internet access. This seems similar to KGaudineer problem as well.

TooSquare OP

Jan ’17

I installed an older version and the problem went away. It does continually ask to upgrade though.

Joe Murphy

Chandre OP

Jan ’17

Happened also on El Capitan, after installation of https://support.apple.com/en-us/HT201222. No reinstallation helped: it always work once, after reboot or reinstallation.

"Solved" by killing dangling processes called "dsAccessService": no reinstallation/reboot needed after that (for now 🙂 ).