cancel
Showing results for 
Search instead for 
Did you mean: 

PulseSecure client not working on kernel 4.18

Occasional Contributor

PulseSecure client not working on kernel 4.18

Hi, I would inform you that PulseSecure client no more works on kernel 4.18 (I have downgraded to 4.17).

 

Regards,

Antonio

Tags (2)
18 REPLIES 18
Occasional Visitor

Re: PulseSecure client not working on kernel 4.18

Hello,

 

Exact same issue. With 4.18 kernel, I got system trace like:

 

[ 7637.700663] do_general_protection: 28 callbacks suppressed
[ 7637.700667] traps: pulsesvc[7098] general protection ip:7f56293ba7e7 sp:7ffedce1d5d8 error:0 in libc-2.27.so[7f562925e000+1b5000]
[ 7638.462685] pulsesvc[7141]: segfault at 7ffc37007360 ip 00007f89a8f5d7e7 sp 00007ffc374af928 error 4 in libc-2.27.so[7f89a8e01000+1b5000]
[ 7638.462688] Code: f9 20 77 1f c5 fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1 1f 48 83 e7 e0 eb 36 66 90 83 e1 1f 48 83 e7 e0 <c5> fd 74 0f c5 fd d7 c1 d3 f8 85 c0 74 1b f3 0f bc c0 48 01 f8 48
[ 7639.155253] traps: pulsesvc[7180] general protection ip:7f889f8c87e7 sp:7ffe99eb8238 error:0 in libc-2.27.so[7f889f76c000+1b5000]
[ 7639.959350] traps: pulsesvc[7187] general protection ip:7f4b41e017e7 sp:7ffd7b209f08 error:0 in libc-2.27.so[7f4b41ca5000+1b5000]

 

I had to downgrade kernel to fix that.

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

I had to downgrade to 4.17!

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

On 4.19-RC6 and latest Pulse Client I get this error:

 

[  227.941466] traps: pulsesvc[5479] general protection ip:7f956dcf95c7 sp:7ffe700e7f68 error:0 in libc-2.27.so[7f956db6b000+1e7000]

Tags (1)
Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

Any news about the fix?!

 

Thank you!

A.

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

Not working on 4.20 too!

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

Here is the stacktrace:

 

Thread 18 "pulseUi" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff953fa700 (LWP 2448)]
0x00007fff550002b4 in ?? ()
(gdb) Segmentation fault (core dumped)
bt
#0  0x00007fff550002b4 in  ()
#1  0x0000000000000246 in  ()
#2  0x00007fff55000160 in  ()
#3  0x00007fff7ddf26e4 in Abstract_VM_Version::_L1_data_cache_line_size () at /usr/lib/jvm/java-8-oracle/jre/lib/amd64/server/libjvm.so
#4  0x00007fff953f3460 in  ()
#5  0x00007fff7d8e9e85 in VM_Version::get_processor_features() () at /usr/lib/jvm/java-8-oracle/jre/lib/amd64/server/libjvm.so
Highlighted
Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

Not working on kernel 4.19

 

$ uname -r
4.19.10-300.fc29.x86_64

$ /usr/local/pulse/pulsesvc -h vpn-host.com -u user -U https://vpn-gw.com/ -r "RSA Token"VPN Password:
Segmentation fault (core dumped)

 

Part of stacktrace:

openat(AT_FDCWD, "/proc/47/stat", O_RDONLY) = 6
read(6, "47 (kworker/0:2-events) I 2 0 0 "..., 1023) = 163
close(6) = 0
openat(AT_FDCWD, "/proc/48/stat", O_RDONLY) = 6
read(6, "48 (watchdogd) S 2 0 0 0 -1 2129"..., 1023) = 156
close(6) = 0
openat(AT_FDCWD, "/proc/49/stat", O_RDONLY) = 6
read(6, "49 (kworker/3:1-events_power_eff"..., 1023) = 179
close(6) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x6564d69c} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped

 

Occasional Contributor

Re: PulseSecure client not working on kernel 4.18

it connects 1 time from ~50 tries

Community Manager

Re: PulseSecure client not working on kernel 4.18

Thank you for the feedback.  We are aware of the problem and working an a fix as quickly as possible. Once the fix is available, we will post information on the following thread.