Oracle Auto Service Request (ASR) (MOSC)

MOSC Banner

ASR manager upgrade error to bind port 162

edited Jul 18, 2020 2:28AM in Oracle Auto Service Request (ASR) (MOSC) 4 commentsAnswered ✓

I have upgraded ASR manager from 5.2 to 19.4 and after upgrade I got this error.

Jul 02, 2020 18:44:50 PM [FelixStartLevel] INFO  asr-snmp-log::62(start) - Starting SNMP Receptor ...

Jul 02, 2020 18:44:50 PM [FelixStartLevel] ERROR asr-snmp-log::80(init) - Error to bind port 162: Permission denied (Bind failed)

Jul 02, 2020 18:44:50 PM [FelixStartLevel] INFO  asr-snmp-log::71(start) - Started SNMP Receptor ...

*****************************************************************************************

But the status is showing ASR SNMP listener is running on port 162

[root@lkedcoramgt01 log]#

[root@lkedcoramgt01 log]# /opt/asrmanager/util/check_asr_status.sh

Checking ASR Manager status ..

PASS: ASR Manager (pid 24202) is RUNNING.

PASS: ASR Manager bundles state is active.

PASS: ASR Manager SNMP listener is running (SNMP port 162).

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center