On Premises: Frequently getting 503 error after every 2-3 hours

Hi ,

We are working on dev environment that is configured on premises server. We are getting 503 on frequently basis. So every time we need to restart the dev server.

So is there any permanent solutions of this as this is taking a lot of our productive time to restart the server again and again.


Thanks

Dileep

Hi Dileep,

Are you able to publish an application at that point? If not, it could be that the OutSystems Deployment Service is down. Also check that it is configured to start automatically after server reboot.

If the above is not the case, check your Event Viewer logs for more details and report back here please.

Regards,

Nordin

Nordin Ahdi wrote:

Hi Dileep,

Are you able to publish an application at that point? If not, it could be that the OutSystems Deployment Service is down. Also check that it is configured to start automatically after server reboot.

If the above is not the case, check your Event Viewer logs for more details and report back here please.

Regards,

Nordin

 Hi Nordin, thanks for the reply. We are able to publish the application. Deployment was up. But when running application on browser or mobile then getting 503 on frequently. We have checked everything all servers are up and running. Increase server configurations size also. Nothing helps we are getting this issue everyday multiple times.


Thanks,

Dileep Verma.

 

Hi Dileep,

As explained in Service Unavailable - HTTP Error 503, You have to Free up the resources

Cause

  1. Your application has at some point reached the allowed memory limit for your (personal) environment;
  2. You have created an application that was using too much CPU for a long time;
  3. You have created a pattern (an infinite loop or wrong code pattern in an integration) that is causing your environment to crash repeatedly;
  4. You have too many complex applications running.

Resolution

Free up the resources

Regards,

Swatantra

Ah, I send the link for the Personal environment, but the cause and resolution stays same. In stead you have to perform these manually on your on-prem environment.