PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes
2016-03-11 15:08
2779 查看
In this Document
Oracle Server - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
The note explains what to look for when experiencing the following error:
PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes: racnode1
Cluster Verification (cluvfy or CVU) detects whether DNS is configured properly by looking up an unknown host and expecting the command to finish in less than 15 seconds.
$ nslookup unknown-not-reachable-node
Case 1: nslookup takes too long time
In below example, it takes over 18 seconds thus the error is generated:
$ time nslookup unknown-not-reachable-node
;; connection timed out; no servers could be reached
.
real 0m18.020s
user 0m0.001s
sys 0m0.005s
As nslookup is OS tool, please engage System/Network Administrator to find out why it takes so long and fix it.
BUG:11775332 - CLUVFY FAILS WITH PRVF-5636 WITH DNS RESPONSE TIMEOUT ERROR
NOTE:1480242.1 - PRVF-5637 : DNS response time could not be checked on following
nodes
Purpose |
Details |
References |
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
APPLIES TO:
Oracle Server - Enterprise Edition - Version 11.2.0.1 and laterInformation in this document applies to any platform.
PURPOSE
The note explains what to look for when experiencing the following error:PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes: racnode1
DETAILS
Cluster Verification (cluvfy or CVU) detects whether DNS is configured properly by looking up an unknown host and expecting the command to finish in less than 15 seconds.$ nslookup unknown-not-reachable-node
Case 1: nslookup takes too long time
In below example, it takes over 18 seconds thus the error is generated:
$ time nslookup unknown-not-reachable-node
;; connection timed out; no servers could be reached
.
real 0m18.020s
user 0m0.001s
sys 0m0.005s
As nslookup is OS tool, please engage System/Network Administrator to find out why it takes so long and fix it.
REFERENCES
BUG:11775332 - CLUVFY FAILS WITH PRVF-5636 WITH DNS RESPONSE TIMEOUT ERRORNOTE:1480242.1 - PRVF-5637 : DNS response time could not be checked on following
nodes
相关文章推荐
- nodejs学习笔记1
- nodejs 读取文件中的几行
- NodeJs实用工具util
- NodeJs之global,process
- asp.net WebAPI 问题 iisnode默认不支持PUT和DELETE的解决
- [LwwtCode]24. Swap Nodes in Pairs
- Node.js 博客实例(六)留言功能
- leetcode 116. Populating Next Right Pointers in Each Node
- js, lambada? 在chrome和node下可以使用
- 使用nodejs爬取拉勾苏州和上海的.NET职位信息
- Node.js项目中调用JavaScript的EJS模板库的方法
- 自制node.js + npm绿色版
- Node.js基础-express的安装
- leetcode:Remove Nth Node From End of List 【Java】
- hadoop 完全分布式 下 datanode无法启动解决办法
- windows下搭建绿色nodejs运行环境
- LeetCode 237. Delete Node in a Linked List
- nodejs与C++交互(二)
- nodejs,node原生服务器搭建实例
- Hadoop 解除 "Name node is in safe mode"