topic Re: Unable to access PA via Web GUI-0 ERROR: websrvr: Exited 4 times, waiting 360 seconds to retry in General Topics

Unable to access PA via Web GUI-0 ERROR: websrvr: Exited 4 times, waiting 360 seconds to retry

MP18 — Mon, 20 May 2019 14:59:42 GMT

Unable to access PA via Webgui

System log shows

2019-05-19 22:43:35.301 -0600 INFO: l3svc: exited, Core: False, Exit code: 1
2019-05-19 22:43:35.570 -0600 ERROR: l3svc: Exited 4 times, waiting 330 seconds to retry
2019-05-19 22:43:35.787 -0600 INFO: websrvr: exited, Core: False, Exit code: 1
2019-05-19 22:43:36.060 -0600 ERROR: websrvr: Exited 4 times, waiting 360 seconds to retry

SSH works fine

show system software status shows

Process l3svc stopped (pid: -1) - Exit Code: 1

Process websrvr stopped (pid: -1) - Exit Code: 1

restarting these deamons do not help.

rebooting PA does not help

Re: Unable to access PA via Web GUI-0 ERROR: websrvr: Exited 4 times, waiting 360 seconds to retry

reaper — Mon, 20 May 2019 15:18:05 GMT

is this a firewall? was it updated recently, or was something changed recently?

Re: Unable to access PA via Web GUI-0 ERROR: websrvr: Exited 4 times, waiting 360 seconds to retry

MP18 — Mon, 20 May 2019 15:20:23 GMT

Yes it is firewall

Only change I made was to import the SSL Cert on the PA and did the commit

This cert is for PA web GUI and is from External Vendor

Re: Unable to access PA via Web GUI-0 ERROR: websrvr: Exited 4 times, waiting 360 seconds to retry

reaper — Mon, 20 May 2019 17:06:06 GMT

Then something in the certificate is making the webserver crash
See if there are any core files and extract a thechsupport file, then load the previous config version and commit
That should fix your issue and then you can check the logs in the TSF to find what sort of error was reported when you loaded the new cert

Re: Unable to access PA via Web GUI-0 ERROR: websrvr: Exited 4 times, waiting 360 seconds to retry

MP18 — Mon, 20 May 2019 17:51:13 GMT

There are no crashinfo files.

Loaded the previous config version and that fixed the issue.

Seema I was importing cert bundle instead of single cert.

Importing Right Cert fixed the issue