Impossible to startup the sap manager

Document ID : KB000086901
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
============================================================================================================================
| 2014-09-29 08:34:07 |ERROR|X|SAP|pid=12453.140704484996896| u_ouv_serv | failed in u_listen: Errno syserror 98: Address already in use
| 2014-09-29 08:34:07 |ERROR|X|SAP|pid=12453.140704484996896| uxsap_thread_main | Error opening service: Errno syserror 98: Address already in use 

Patch level detected:Dollar Universe 6.2.00
Product Version: Dollar.Universe 6.2.0

Description :After a restart of the server, it is impossible to restart the SAP Manager
Environment:
OS: All Unix
Cause:
Cause type:
Configuration
Root Cause: The problem can come from a thrid party application that blocks the SAP Manager dedicated port at start-up. This will prevent the SAP Manager from starting
Resolution:
As explained in the post below. You should always verify this points when such a problem occurs. After the changing used by the third party application SAP Manager will start.

===============================================================================================================
After a scheduled unix system maintenance the sap agent could not start up again.
As it turns out, the unix NFS-service grabbed the sap agent port (10609), preventing the sap agent from starting.

After restarting the NFS-service on another port the sap agent could be started correctly.

We have advised our unix technicians to prevent further access on the $Universe ports.

As a improvement proposal, could an appropriate error message be displayed during $Universe startup?
Right now, only a generic "Could not start agent" message is displayed.
It would be nice to have "Could not start agent because port 10609 is already in use".
===============================================================================================================

Fix Status: No Fix
 
Additional Information:
Workaround :
N/A