cancel
Showing results for 
Search instead for 
Did you mean: 

[SRX Connection] 9.0r4-b1731 Service exited due to SIGSERV.

Occasional Contributor

[SRX Connection] 9.0r4-b1731 Service exited due to SIGSERV.

Running MacOS 10.14

Connecting to SRX

Can successfully connect on Pulse Secure 5.0.3

Can't connect on any installer I can find past that.
After connecting, the service restarts itself indefinetly. 

 

Successfull connection:

00139,09 2019/06/18 16:10:46.266 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1672 - 'TM' policyName=p_x.x.x.x_1_7f891553d520
00111,09 2019/06/18 16:10:46.266 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1673 - 'TM' policyType=1
00125,09 2019/06/18 16:10:46.266 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1681 - 'TM' ipsec phase1UID=dynvpn
00126,09 2019/06/18 16:10:46.266 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1683 - 'TM' ipsec phase1Password exists
00124,09 2019/06/18 16:10:46.266 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1688 - 'TM' ipsec ieAddr=x.x.x.x
00108,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1689 - 'TM' ikePort=0
00114,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1690 - 'TM' phase1UIDType=2
00109,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1691 - 'TM' dnsorder=1
00127,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1692 - 'TM' ipsec remoteAddr=192.168.0.0
00127,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1693 - 'TM' ipsec remoteMask=255.255.0.0
00112,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1694 - 'TM' ike dhGroup=2
00109,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1695 - 'TM' ike auth=2
00115,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1696 - 'TM' ike encr=8388620
00118,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1697 - 'TM' rekeyIpsecSaCount=0
00117,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1698 - 'TM' rekeySeconds=28800
00114,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1699 - 'TM' ipsec natmode=2
00115,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1700 - 'TM' ipsec pfsGroup=2
00111,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1701 - 'TM' ipsec auth=2
00117,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1702 - 'TM' ipsec encr=8388620
00118,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1703 - 'TM' ipsec idleTimeout=0
00124,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1704 - 'TM' ipsec rekeyKOctets=500000
00122,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1705 - 'TM' ipsec rekeySeconds=3600
00121,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1706 - 'TM' ipsec sessionTimeout=0
00118,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1707 - 'TM' persistent tunnel=1
00130,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1712 - 'TM' clientVendorID=JNPR IPSec Clien
00110,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1714 - 'TM' clientID=33
00147,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1665 - 'TM' AddPolicy(p_x.x.x.x_1_7f891553d520) success
00139,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1672 - 'TM' policyName=p_x.x.x.x_2_7f891553d610
00111,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1673 - 'TM' policyType=1
00125,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1681 - 'TM' ipsec phase1UID=dynvpn
00126,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1683 - 'TM' ipsec phase1Password exists
00124,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1688 - 'TM' ipsec ieAddr=x.x.x.x
00108,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1689 - 'TM' ikePort=0
00114,09 2019/06/18 16:10:46.267 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1690 - 'TM' phase1UIDType=2
00109,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1691 - 'TM' dnsorder=1
00124,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1692 - 'TM' ipsec remoteAddr=10.0.0.0
00125,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1693 - 'TM' ipsec remoteMask=255.0.0.0
00112,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1694 - 'TM' ike dhGroup=2
00109,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1695 - 'TM' ike auth=2
00115,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1696 - 'TM' ike encr=8388620
00118,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1697 - 'TM' rekeyIpsecSaCount=0
00117,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1698 - 'TM' rekeySeconds=28800
00114,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1699 - 'TM' ipsec natmode=2
00115,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1700 - 'TM' ipsec pfsGroup=2
00111,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1701 - 'TM' ipsec auth=2
00117,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1702 - 'TM' ipsec encr=8388620
00118,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1703 - 'TM' ipsec idleTimeout=0
00124,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1704 - 'TM' ipsec rekeyKOctets=500000
00122,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1705 - 'TM' ipsec rekeySeconds=3600
00121,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1706 - 'TM' ipsec sessionTimeout=0
00118,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1707 - 'TM' persistent tunnel=1
00130,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1712 - 'TM' clientVendorID=JNPR IPSec Clien
00110,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1714 - 'TM' clientID=33
00147,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1665 - 'TM' AddPolicy(p_x.x.x.x_2_7f891553d610) success
00139,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1672 - 'TM' policyName=p_x.x.x.x_3_7f891553d700
00111,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1673 - 'TM' policyType=2
00129,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1675 - 'TM' passthrough remoteAddr=0.0.0.0
00129,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1676 - 'TM' passthrough remoteMask=0.0.0.0
00147,09 2019/06/18 16:10:46.268 3 root dsAccessService dsTMService p1373 t7803 addpolicy.cpp:1665 - 'TM' AddPolicy(p_x.x.x.x_3_7f891553d700) success

 

 

3 REPLIES 3
Moderator

Re: [SRX Connection] 9.0r4-b1731 Service exited due to SIGSERV.

SRX connections are not supported on 9.0R4
It looks like you are trying to use split tunneling disabled on the SRX connection; if that is true, that is not supported on the macOS client.
Occasional Contributor

Re: [SRX Connection] 9.0r4-b1731 Service exited due to SIGSERV.

Ok that seems odd to me.  Why do I have the option to set up an SRX connection if it is not supported?

So what can I do in this situation?  5.0.3 works but whenever I my computer sleeps or I restart my computer with the program running, I lose my connections and I have to reinstall the program in order to get it working again.



Moderator

Re: [SRX Connection] 9.0r4-b1731 Service exited due to SIGSERV.

unfortunately, i am not sure why that decision was made. i agree it is odd.
have you had a chance to try the 5.1R9 client? that was the last version to support SRX connections.
if that also shows the same behavior, i would recommend reaching out to Juniper to work with them; they will reach out to the Pulse Secure support team as-needed from there