Forum Discussion
error 503 and
Hi
I have three IIS node in my F5 LTM pool. One of the node working perfectly without any issue. Meanwhile my other node2 and node3 always throw an exception at peak hour. We have member portal which allow member to login at 11AM everyday for signup. 11AM consider peak hour since all the members will rush to login at this time.
Im getting following error on my LTM for two other nodes.
Mar 1 11:00:21 f501 notice mcpd[8964]: 01070638:5: Pool /Common/Member-Portal member /Common/CRM-WEB-02:443 monitor status down. [ /Common/http_monitor_return_code: down; last error: /Common/http_monitor_return_code: Response Code: 301 (Moved Permanently); Unable to connect; No successful responses received before deadline.; Response Code: 503 (Service Unavailable); Response Code: 404 (Not Found) @2018/03/01 11:00:21. ] [ was up for 12hrs:19mins:53sec ]
Mar 1 11:00:32 f501 notice mcpd[8964]: 01070638:5: Pool /Common/Member-Portal member /Common/CRM-WEB-05:443 monitor status down. [ /Common/http_monitor_return_code: down; last error: /Common/http_monitor_return_code: Response Code: 301 (Moved Permanently); Unable to connect; No successful responses received before deadline.; Response Code: 302 (Found) @2018/03/01 11:00:32. ] [ was up for 9hrs:55mins:31sec ]
Mar 1 11:00:38 f501 notice mcpd[8964]: 01070727:5: Pool /Common/Member-Portal member /Common/CRM-WEB-02:443 monitor status up. [ /Common/http_monitor_return_code: up ] [ was down for 0hr:0min:17sec ]
Mar 1 11:00:47 f501 notice mcpd[8964]: 01070727:5: Pool /Common/Member-Portal member /Common/CRM-WEB-05:443 monitor status up. [ /Common/http_monitor_return_code: up ] [ was down for 0hr:0min:15sec ]
Can anyone put some light why I'm getting this error for only two nodes and not for all node? Same IIS setup and windows. I cant find any different. Do i miss anything here?
Thanks
2 Replies
- Anesh
Cirrostratus
- Can your provide the Virtual, Pool and Monitor configuration from the cli?
- JG
Cumulonimbus
The server response to the URL in the "send string" should normally be a single HTTP status, e.g. "OK 200". With this url ("/") in the send string it is hard to imagine that the status changes and the service remains normal/healthy.
However, the problem you experience is likely due to the back-end servers. Were they overloaded at around 11am?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com