GlobalProtect for Linux cannot connect to local gpd service

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

GlobalProtect for Linux cannot connect to local gpd service

L1 Bithead

After installing the rpm (latest version as of today: 4.1.7, running on Fedora 28) the cli client cannot communicate with the service (although it is started):


$ systemctl status gpd
● gpd.service - GlobalProtect VPN client daemon
Loaded: loaded (/usr/lib/systemd/system/gpd.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2018-12-27 13:19:03 CET; 40s ago
Process: 435 ExecStartPre=/opt/paloaltonetworks/globalprotect/pre_exec_gps.sh (code=exited, status=0/SUCCESS)
Main PID: 507 (PanGPS)
Tasks: 10 (limit: 4671)
Memory: 20.9M
CGroup: /system.slice/gpd.service
└─507 /opt/paloaltonetworks/globalprotect/PanGPS

 

 


$ globalprotect
Cannot connect to local gpd service.

 


PanGPI.log says:
P1816-T-1080174784 Dec 27 13:25:37:591453 Error( 119): Run GPI into promptDec 27 13:25:37:591454 Info ( 676): debug thread starts
P1816-T-1080174784 Dec 27 13:25:37:591489 Error( 80): CPanMsgQueue::create - failed to open message queue. error = 2
P1816-T-1080174784 Dec 27 13:25:37:591508 Error( 51): ConnectToGPA fail with error 2.
P1816-T-1100282112 Dec 27 13:25:38:591699 Info ( 682): debug thread ends

 

 

Does anyone have an idea what's going on here before I open a support case?

1 accepted solution

Accepted Solutions

L1 Bithead
I switched to the latest (head) version of OpenConnect which also supports PaloAlto portal and gateway connection (without the need to enable xauth).

View solution in original post

5 REPLIES 5

Cyber Elite
Cyber Elite

@ctr_ts,

What if you try launching it with sudo? 

Same result

@ctr_ts,

I'd probably chock this up to Fedora not being a supported Linux distrobution. Currently the only supported is CenOS 7, RHEL 7, Ubuntu 14.04 and later, Ubuntu 16, and Ubuntu 18 works but not officially. 

Also getting this error on RHEL 7 btw

L1 Bithead
I switched to the latest (head) version of OpenConnect which also supports PaloAlto portal and gateway connection (without the need to enable xauth).
  • 1 accepted solution
  • 22638 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!