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

Reply
L4 Transporter

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

 

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

Tags (1)
Community Manager

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

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


Help the community: Like helpful comments and mark solutions
Reaper out
L4 Transporter

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

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

Community Manager

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

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

Help the community: Like helpful comments and mark solutions
Reaper out
L4 Transporter

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

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

 

 

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 Live Community as a whole!

The Live Community thanks you for your participation!