IBM Support

webMethods Knowlegebase : Load balancer component failed to start with port 80 (1798925)

Troubleshooting


Problem

Internal load balancer component of API Portal (loadbalancer_s) failed to start after it was reconfigured to use http port 80.

The CloudAgent.log shows the following:

"INFO | jvm 1 | 2019/07/10 14:47:04 | 2019-07-10 14:47:04,887|INFO |qtp225487701-38| com.aris.prov.agent.RUNNABLE.HISTORY - loadbalancer_s - State change: STARTING -> FAILED.

:

INFO | jvm 1 | 2019/07/10 14:47:04 | 2019-07-10 14:47:04,892|ERROR|qtp225487701-38| com.aris.prov.agent.rest.resources.RunnableLifecycleResource - StartErrorAnt start exited with 1"

At the same time, the following error is logged in <SAG>/API_Portal/server/bin/work/work_loadbalancer_s/httpd/logs/system.out:

"(13)Permission denied: AH00072: make_sock: could not bind to address [::]:80

(13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80

no listening sockets available, shutting down"

Document Location

Worldwide

[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSQKXP","label":"IBM webMethods API Management"},"ARM Category":[{"code":"a8mKe00000000AQIAY","label":"webMethods API Portal (YAP)"}],"ARM Case Number":"","Platform":[{"code":"PF061","label":"Unix"}],"Version":"All Version(s)"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
20 March 2025

UID

ibm17195205

Page Feedback