SystemEDGE on Solaris doesn't start with Error -1 (125) in bind ( 13)

book

Article ID: 192023

calendar_today

Updated On:

Products

CA Virtual Assurance for IM

Issue/Introduction

We have SystemEDGE 5.9 running on a Solaris 10 server and the agent doesn't appear to start. 

Here is an excerpt in the log file:

0000082 2020-05-27 14:58:33.82 [C]-001- AWM_SocketCreateServer     : Error -1 (125) in bind ( 13).
0000083 2020-05-27 14:58:33.82 [C]-001- AWM_SocketCreateServer     : Socket was not created.
0000084 2020-05-27 14:58:33.82 [F]-001- se/sysedge.c[329]          : main(): Could not initialize SNMP listening
0000085 2020-05-27 14:58:33.82 [F]-001- se/sysedge.c[330]          : main(): Socket UDP/1691 may be used by another process, make sure no other SNMP service is active!

Environment

Release : 12.9

Component : VPM GENERAL

Resolution

1. Run ps -ef | grep -i sysedge to see if any sysedge.exe processes are running\hung.
2. kill -9 <pid> for any sysedge instances which are running.
3. Within the sysedge.cf file located under /opt/CA/SystemEDGE/config/port# folder define the bind_address parameter with the Ip Address you would like SystemEDGE to use.




4. Start SystemEDGE and it should start normally.

Attachments