Re: 503 Server Unavailable for API call

Jun_Liang_Seow · ‎2017-12-19

Hi,

I am having some issues doing a login api call. Previously, I was able to do it. I have checked the Management API Settings and found that it is still enabled for 'Automatic Start' and allowing all IP Addresses.

Below is the error.

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html>
<head>
<title>503 Service Unavailable</title>
</head>
<body>
<h1>Service Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
</body>
</html>

PhoneBoy · ‎2017-12-19

What version/jumbo are you using?

Confirm using the command api status to see what it thinks the status is.

I have a feeling this may be the issue, which should be fixed by a recent R80.10 Jumbo: R80.10 API bug: fallback to "SmartCenter Only" after reboot

Jun_Liang_Seow · ‎2017-12-20

Hi Dameon,

We are using Take 42. Doing an API Status shows that the Overall API Status is not running. The management server has been up for the past 82 days. The last time I did an API call was 6 days ago. From looking at the bug fix in Take 37, it might not be the same issue.

Robert_Decker · ‎2017-12-20

What is your server's configuration - MDM or SMS?

How much RAM is installed on your machine?

Jonathan_Horne · ‎2018-04-02

I am getting same Error Message, when trying to Retrieve Configs after adding Check Point R80.10 JHF 91 CMA's to Firemon version 8.19.4.

Last Updated: 4/2/2018 4:24 PM
Status: Failure
Description: Manual Retrieval
Retrieval Error: Error: Error Summary:
Exception: http status=503 content=<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>503 Service Unavailable</title>
</head><body>
<h1>Service Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
</body></html>

[Expert@XXXXXXX1:0]# api status

API Settings:
---------------------
Accessibility: Require all granted
Automatic Start: Enabled

Processes:

Name State PID More Information
-------------------------------------------------
API Started 5551
CPM Started 876 Check Point Security Management Server is running and ready
FWM Started 7500

Port Details:
-------------------
JETTY Internal Port: 50276
APACHE Gaia Port: 443

--------------------------------------------
Overall API Status: Started
--------------------------------------------

API readiness test SUCCESSFUL. The server is up and ready to receive connections

Notes:
------------
To collect troubleshooting data, please run 'api status -s <comment>'

Robert_Decker · ‎2018-04-08

Hi Jonathan,

Are you running the API through the Firemon scripts?

The "API readiness test SUCCESSFUL" status means that our API server is running.

It seems that there is a problem with your Firemon interfaces.

Robert.

Are you a member of CheckMates?

503 Server Unavailable for API call