- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
10-25-2023 01:19 PM
Anyone know what could be going on here:
> /opt/paloaltonetworks/globalprotect/globalprotect launch-ui --recover
Quit the application by signal(15).
Issued terminate to UI but still running.
Either try terminating UI again or continue to launch.
Do you want to continue(y/n)?
Using --recover because without it, the launch-ui command returns nothing on stdout and presents no GUI or notification icon.
On that "Issued terminate to UI but still running": I've noticed that before that hitting Ctrl-C or Ctrl-\ prompts the application to print "Quit the application by signal(3)" (or "signal(2)") but not actually quit. It's only possible to "kill -9" it.
How best to just restart everything to do with GlobalProtect? Tried "systemctl restart gpd" and then "/opt/paloaltonetworks/globalprotect/globalprotect launch-ui" but making no progress. "journalctl -u gpd" shows nothing beyond "Started GlobalProtect VPN client daemon."
Also "systemctl stop gpd" yields this in this in its logs:
Oct 25 14:18:00 hostname systemd[1]: Stopping GlobalProtect VPN client daemon...
Oct 25 14:18:11 hostname systemd[1]: gpd.service: Main process exited, code=dumped, status=11/SEGV
Oct 25 14:18:11 hostname systemd[1]: gpd.service: Failed with result 'core-dump'.
Oct 25 14:18:11 hostname systemd[1]: Stopped GlobalProtect VPN client daemon.
10-31-2023 08:53 PM
Hi @flemingr ,
Can you try uninstalling GP from your box and reinstalling it?
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!