Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Check listening and reporting errors: how to solve the problem with WARNING:Subscription for node down event still pending

2025-01-15 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

Error report: how to solve WARNING:Subscription for node down event still pending, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Problem description: after listening is restarted, wait a moment (about one minute later) to check the monitoring status. The monitoring has reported an error:

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

Linux Error: 111: Connection refused

-in fact, the above error is that the monitor did not start-- as for the reason why the program did not start, it may be that the program did not start or the process was KILL, suspended and other reasons.

Check the log and find a message: WARNING: Subscription for node down event still pending

To search for this error information, the online answer is roughly two situations:

Case 1: Oracle shows that the problem is bug and fixed in 10.2.0.3, but still exists in 11.1.0.6.

Case 2: the monitor cannot be started on the specified port-maybe the previous monitor did not exit normally or some other program occupied the port

But recall that the listener has been running normally, but also checked that the port is not abnormal. With the mentality that there are mistakes and start with yourself, I recalled all the recent changes to the system.

The registrations of modified listening configuration files listener.ora, tnsnames.ora, and dynamic monitoring have been checked many times. Multiple rebuilds of monitoring failed to resolve this failure.

Finally remembering the modified information in / etc/hosts, I modified the file again to restore the 127.0.0.1 entry to the system default: 127.0.0.1 localhost.localdomain localhost.

Restart monitoring is normal.

Let's reproduce the generation and resolution of this error.

The experimental idea shows that some meaningless outputs are omitted from being posted. You can view the required sections directly in the article directory on the top left of the article.

Experiment 1 is to configure / etc/hosts correctly and monitor the state of normal operation.

In experiment 2, the simulation error scenario is to modify 127.0.0.1 bys3.bys.com bys3, add 192.168.1.211 bys3.bys.com, and modify the three small steps of listener.ora respectively.

In experiment 3, the simulation error scenario is to modify 127.0.0.1 bys3.bys.com bys3, but delete the 192.168.1.211 bys3.bys.com bys3 entry. Use the listener.ora created by default by DBCA

#

Lab 1: set the 127.0.0.1 entry in / etc/hosts to the default:

The 127.0.0.1 localhost.localdomain localhost;192.168.1.211 bys3.bys.com bys3 entry remains.

Restarting the monitoring is fine.

[root@bys3 ~] # cat / etc/hosts

127.0.0.1 localhost.localdomain localhost

:: 1 localhost6.localdomain6 localhost6

192.168.1.211 bys3.bys.com bys3

[root@bys3 ~] # ping bys3

PING bys3.bys.com (192.168.1.211) 56 (84) bytes of data.

64 bytes from bys3.bys.com (192.168.1.211): icmp_seq=1 ttl=64 time=0.232 ms

^ C

-bys3.bys.com ping statistics

1 packets transmitted, 1 received, 0 packet loss, time 0ms

Rtt min/avg/max/mdev = 0.232 ms 0.232 ms

[root@bys3 ~] # ping bys3.bys.com

PING bys3.bys.com (192.168.1.211) 56 (84) bytes of data.

64 bytes from bys3.bys.com (192.168.1.211): icmp_seq=1 ttl=64 time=0.125 ms

^ C

[oracle@bys3 admin] $cat listener.ora

# listener.ora Network Configuration File: / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

# Generated by Oracle configuration tools.

LISTENER =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = bys3.bys.com) (PORT = 1521))

(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC1521))

)

)

ADR_BASE_LISTENER = / U01

[oracle@bys3 admin] $lsnrctl start

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 10:56:55

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Starting / u01/app/oracle/product/11.2.0/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 11.2.0.4.0-Production

System parameter file is / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Log messages written to / u01/diag/tnslsnr/bys3/listener/alert/log.xml

Listening on: (DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=bys3.bys.com) (PORT=1521)

Listening on: (DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=EXTPROC1521)

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=bys3.bys.com) (PORT=1521)

STATUS of the LISTENER

-

Alias LISTENER

Version TNSLSNR for Linux: Version 11.2.0.4.0-Production

Start Date 18-NOV-2013 10:56:57

Uptime 0 days 0 hr. 0 min. 0 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Listener Log File / u01/diag/tnslsnr/bys3/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=bys3.bys.com) (PORT=1521))

(DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=EXTPROC1521)

The listener supports no services

The command completed successfully

[oracle@bys3 admin] $lsnrctl status-the listener is running normally and the instance has been registered. -- dynamic registration

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 10:59:10

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=bys3.bys.com) (PORT=1521)

STATUS of the LISTENER

-

Alias LISTENER

Version TNSLSNR for Linux: Version 11.2.0.4.0-Production

Start Date 18-NOV-2013 10:56:57

Uptime 0 days 0 hr. 2 min. 12 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Listener Log File / u01/diag/tnslsnr/bys3/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=bys3.bys.com) (PORT=1521))

(DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=EXTPROC1521)

Services Summary...

Service "bys3" has 1 instance (s).

Instance "bys3", status READY, has 1 handler (s) for this service...

The command completed successfully

#

Experiment 2: modify the 127.0.0.1 entry in / etc/hosts, and modify the three small steps of listener.ora respectively

After changing the 127.0.0.1 localhost.localdomain localhost entry to 127.0.0.1 bys3.bys.com bys3

Add another IP corresponding to the domain name: 192.168.1.211 bys3.bys.com

As follows:

[root@bys3 ~] # cat / etc/hosts

# Do not remove the following line, or various programs

# that require network functionality will fail.

# 127.0.0.1 localhost.localdomain localhost

127.0.0.1 bys3.bys.com bys3

:: 1 localhost6.localdomain6 localhost6

192.168.1.211 bys3.bys.com bys3

[root@bys3 ~] # ping bys3

PING bys3.bys.com (127.0.0.1) 56 (84) bytes of data.

64 bytes from bys3.bys.com (127.0.0.1): icmp_seq=1 ttl=64 time=0.122 ms

[root@bys3 ~] # ping bys3.bys.com

PING bys3.bys.com (127.0.0.1) 56 (84) bytes of data.

64 bytes from bys3.bys.com (127.0.0.1): icmp_seq=1 ttl=64 time=0.118 ms

After modifying the 127.0.0.1 entry in / etc/hosts, the following three situations are tested (all are modified listener.ora files)

The error messages in the monitoring log are all: WARNING: Subscription for node down event still pending

Monitoring configuration 1: use NETCA to create the default listener.ora file for monitoring

Restart the monitoring at this time, and then wait (about a minute later) to check the listening status. The monitoring has reported an error, and the error in the monitoring log is WARNING: Subscription for node down event still pending.

Monitoring profile:

[oracle@bys3 admin] $cat listener.ora

LISTENER =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = bys3.bys.com) (PORT = 1521))

(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC1521))

)

)

ADR_BASE_LISTENER = / U01

Start the monitoring and check the status-check the status to wait a moment after the monitoring starts, and an error will be reported. It was normal when it was first started and finished.

[oracle@bys3 admin] $lsnrctl start-start snooping

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 10:26:44

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Starting / u01/app/oracle/product/11.2.0/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 11.2.0.4.0-Production

System parameter file is / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Log messages written to / u01/diag/tnslsnr/bys3/listener/alert/log.xml

Listening on: (DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=bys3.bys.com) (PORT=1521)

Listening on: (DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=EXTPROC1521)

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=bys3.bys.com) (PORT=1521)

STATUS of the LISTENER

-

Alias LISTENER

Version TNSLSNR for Linux: Version 11.2.0.4.0-Production

Start Date 18-NOV-2013 10:26:45

Uptime 0 days 0 hr. 0 min. 0 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

Listener Log File / u01/diag/tnslsnr/bys3/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=bys3.bys.com) (PORT=1521))

(DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=EXTPROC1521)

The listener supports no services

The command completed successfully

[oracle@bys3 admin] $lsnrctl status-after the listener starts, wait a moment to check the status. The listener is dead.

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 10:27:09

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=bys3.bys.com) (PORT=1521)

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

Linux Error: 111: Connection refused

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521)

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

Linux Error: 111: Connection refused

#

Snooping configuration 2: delete this line from the default snooping configuration file (ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC1521))

Restart the monitoring at this time, and then wait (about a minute later) to check the listening status. The monitoring has reported an error, and the error in the monitoring log is WARNING: Subscription for node down event still pending.

Monitoring profile:

[oracle@bys3 admin] $cat listener.ora

LISTENER =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = bys3.bys.com) (PORT = 1521))

)

)

ADR_BASE_LISTENER = / U01

[oracle@bys3 admin] $lsnrctl start-start listening-the output information is the same as in the previous step monitoring configuration, and the less important information will not be posted.

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 10:37:24

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=bys3.bys.com) (PORT=1521))

The listener supports no services

The command completed successfully

[oracle@bys3 admin] $lsnrctl status-after the listener starts, wait a moment to check the status. The listener is dead.

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 10:39:12

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=bys3.bys.com) (PORT=1521)

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

Linux Error: 111: Connection refused

#

Snooping configuration 3: change the domain name in HOST in the default snooping configuration file (ADDRESS = (PROTOCOL = TCP) (HOST = bys3.bys.com) (PORT = 1521)) to IP

Restart the monitoring at this time, and then wait (about a minute later) to check the listening status. The monitoring has reported an error, and the error in the monitoring log is WARNING: Subscription for node down event still pending.

Monitoring profile:

[oracle@bys3 admin] $cat listener.ora

LISTENER =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.1.211) (PORT = 1521))

)

)

ADR_BASE_LISTENER = / U01

[oracle@bys3 admin] $ping 192.168.1.211

PING 192.168.1.211 (192.168.1.211) 56 (84) bytes of data.

64 bytes from 192.168.1.211: icmp_seq=1 ttl=64 time=1.04 ms

[oracle@bys3 admin] $lsnrctl start-start listening-the output information is the same as in the listening configuration, and the less important information will not be posted.

Listening Endpoints Summary...

(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=192.168.1.211) (PORT=1521))

The listener supports no services

The command completed successfully

[oracle@bys3 admin] $lsnrctl status-after the listener starts, wait a moment to check the status. The listener is dead.

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 10:42:27

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=192.168.1.211) (PORT=1521)

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

Linux Error: 111: Connection refused

#

Experiment 3: the simulation error scenario is to modify 127.0.0.1 bys3.bys.com bys3, but delete the 192.168.1.211 bys3.bys.com bys3 entry. Use the listener.ora created by default by DBCA

Restart the monitoring at this time, and then wait (about a minute later) to check the listening status. The monitoring has reported an error, and the error in the monitoring log is WARNING: Subscription for node down event still pending.

Monitoring profile:

[root@bys3 ~] # cat / etc/hosts

# Do not remove the following line, or various programs

# that require network functionality will fail.

# 127.0.0.1 localhost.localdomain localhost

:: 1 localhost6.localdomain6 localhost6

# 192.168.1.211 bys3.bys.com bys3

127.0.0.1 bys3.bys.com bys3

[root@bys3 ~] # ping bys3.bys.com

PING bys3.bys.com (127.0.0.1) 56 (84) bytes of data.

64 bytes from bys3.bys.com (127.0.0.1): icmp_seq=1 ttl=64 time=0.305 ms

^ C

[root@bys3 ~] # ping bys3

PING bys3.bys.com (127.0.0.1) 56 (84) bytes of data.

64 bytes from bys3.bys.com (127.0.0.1): icmp_seq=1 ttl=64 time=0.114 ms

^ C

[oracle@bys3 admin] $cat listener.ora

# listener.ora Network Configuration File: / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora

# Generated by Oracle configuration tools.

LISTENER =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = bys3.bys.com) (PORT = 1521))

(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC1521))

)

)

ADR_BASE_LISTENER = / U01

[oracle@bys3 admin] $lsnrctl start-start listening-the output information is the same as in the previous step monitoring configuration, and the less important information will not be posted.

The listener supports no services

The command completed successfully

[oracle@bys3 admin] $lsnrctl status-after the listener starts, wait a moment to check the status. The listener is dead.

LSNRCTL for Linux: Version 11.2.0.4.0-Production on 18-NOV-2013 11:13:48

Copyright (c) 1991, 2013, Oracle. All rights reserved.

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=bys3.bys.com) (PORT=1521)

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

Linux Error: 111: Connection refused

Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521)

TNS-12541: TNS:no listener

TNS-12560: TNS:protocol adapter error

TNS-00511: No listener

Linux Error: 111: Connection refused

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report