Oracle数据库数据恢复、性能优化

找回密码
注册
搜索
热搜: 活动 交友 discuz
Oracle数据库数据恢复、性能优化»论坛 › Oracle › Oracle数据库管理 › grid control 获取不到agent信息
发新帖
xteitxu

62

积分

0

好友

3

主题

grid control 获取不到agent信息

1#
发表于 2012-3-14 17:24:56 | 查看: 7279| 回复: 5
场景描述：公司内网一台服务器A安装agent，被一台gc服务器监控。因需该A服务器要承载生产业务，搬到电信机房。搬走后，agent重装后却无法与内网的gc服务器通信，得不到监控。（公司在电信机房内有防火墙，A服务器与gc服务器已做vpn，并且相关4889、1521、1159端口都通。）报错看附件图。帮忙分析下，问题出在那里。是不是什么端口没有打开

代理重新同步error.png (25.05 KB, 下载次数: 387)

代理重新同步error.png

emagent.trc.txt

135.76 KB, 下载次数: 880
学海无涯，技术至上！
2#
发表于 2012-3-14 17:58:28
ODM Finding:
  1. 2012-03-14 17:02:19,247 Thread-4264 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1
  2. 2012-03-14 17:02:21,852 Thread-4264 ERROR http: nmehl_connect_internal: failed to get host info. Could not resolve name
  3. 2012-03-14 17:02:21,852 Thread-4264 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1
  4. 2012-03-14 17:02:46,641 Thread-5064 WARN  http: 1536 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  5. 2012-03-14 17:02:46,641 Thread-5064 WARN  http: 1536: invalid method in http request: "276"
  6. 2012-03-14 17:02:47,077 Thread-4948 WARN  http: 1636 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  7. 2012-03-14 17:02:47,077 Thread-4948 WARN  http: 1636: invalid method in http request: "276"
  8. 2012-03-14 17:02:47,499 Thread-4100 WARN  http: 1652 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  9. 2012-03-14 17:02:47,499 Thread-4100 WARN  http: 1652: invalid method in http request: "276"
  10. 2012-03-14 17:02:47,826 Thread-4492 ERROR http: nmehl_connect_internal: failed to get host info. Could not resolve name
  11. 2012-03-14 17:02:47,826 Thread-4492 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1
  12. 2012-03-14 17:02:48,435 Thread-4240 WARN  http: 1664 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  13. 2012-03-14 17:02:48,435 Thread-4240 WARN  http: 1664: invalid method in http request: "276"
  14. 2012-03-14 17:02:48,871 Thread-3684 WARN  http: 1724 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  15. 2012-03-14 17:02:48,871 Thread-3684 WARN  http: 1724: invalid method in http request: "276"
  16. 2012-03-14 17:02:49,308 Thread-300 WARN  http: 1612 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  17. 2012-03-14 17:02:49,308 Thread-300 WARN  http: 1612: invalid method in http request: "276"
  18. 2012-03-14 17:02:49,729 Thread-4960 WARN  http: 1664 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  19. 2012-03-14 17:02:49,729 Thread-4960 WARN  http: 1664: invalid method in http request: "276"
  20. 2012-03-14 17:02:54,487 Thread-3652 ERROR http: nmehl_connect_internal: failed to get host info. Could not resolve name
  21. 2012-03-14 17:02:54,487 Thread-3652 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1
  22. 2012-03-14 17:02:57,093 Thread-3652 ERROR http: nmehl_connect_internal: failed to get host info. Could not resolve name
  23. 2012-03-14 17:02:57,093 Thread-3652 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1
  24. 2012-03-14 17:03:12,599 Thread-2232 WARN  http: 1704 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  25. 2012-03-14 17:03:12,599 Thread-2232 WARN  http: 1704: invalid method in http request: "109"
  26. 2012-03-14 17:03:13,036 Thread-2108 WARN  http: 1504 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  27. 2012-03-14 17:03:13,036 Thread-2108 WARN  http: 1504: invalid method in http request: "109"
  28. 2012-03-14 17:03:13,519 Thread-2136 WARN  http: 1588 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  29. 2012-03-14 17:03:13,519 Thread-2136 WARN  http: 1588: invalid method in http request: "71"
  30. 2012-03-14 17:03:13,941 Thread-4092 WARN  http: 1704 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  31. 2012-03-14 17:03:13,941 Thread-4092 WARN  http: 1704: invalid method in http request: "71"
  32. 2012-03-14 17:03:14,487 Thread-4980 WARN  http: 1504 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  33. 2012-03-14 17:03:14,487 Thread-4980 WARN  http: 1504: invalid method in http request: "72"
  34. 2012-03-14 17:03:14,923 Thread-4516 WARN  http: 1588 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  35. 2012-03-14 17:03:14,923 Thread-4516 WARN  http: 1588: invalid method in http request: "72"
  36. 2012-03-14 17:03:29,712 Thread-3884 ERROR http: nmehl_connect_internal: failed to get host info. Could not resolve name
  37. 2012-03-14 17:03:29,712 Thread-3884 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1
  38. 2012-03-14 17:03:32,317 Thread-3884 ERROR http: nmehl_connect_internal: failed to get host info. Could not resolve name
  39. 2012-03-14 17:03:32,317 Thread-3884 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1
  40. 2012-03-14 17:03:48,448 Thread-4052 WARN  http: 1688 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  41. 2012-03-14 17:03:48,448 Thread-4052 WARN  http: 1688: invalid method in http request: "276"
  42. 2012-03-14 17:03:48,869 Thread-2324 WARN  http: 1704 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  43. 2012-03-14 17:03:48,869 Thread-2324 WARN  http: 1704: invalid method in http request: "276"
  44. 2012-03-14 17:03:49,290 Thread-5048 WARN  http: 1588 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  45. 2012-03-14 17:03:49,290 Thread-5048 WARN  http: 1588: invalid method in http request: "276"
  46. 2012-03-14 17:03:49,711 Thread-1056 WARN  http: 1688 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
  47. 2012-03-14 17:03:49,711 Thread-1056 WARN  http: 1688: invalid method in http request: "276"
复制代码
<=================================================================================================

确保在 AGENT所在服务器上 能正常访问： https://WIN-1WPTHCMPJYT:1159/em/upload 这个URL ， 可以尝试用 浏览器访问该地址 以测试。

回复 只看该作者 道具 举报

3#
发表于 2012-3-14 18:37:09
诊断Grid Control  Agent 问题的一些思路：

   - emctl status agent
   - emctl upload
   - emctl status agent scheduler
   - emctl status agent memory
   - emctl status agent jobs
   - emctl config agent getTZ
   - emctl status agent secure
   - emctl secure status agent
   - ping OMS服务器ip的结果

回复 只看该作者 道具 举报

4#
发表于 2012-3-15 10:15:41
maclean,下面是关于我的agent的一些相关信息。

https://WIN-1WPTHCMPJYT:1159/em/upload

Http XML File receiver
Http Receiver Servlet active!
Product version is: 11g
Product release version is: 11.1.0.1.0
Core release version is: 11.1.0.1.0

C:\app\agent_home\agent11g\BIN>emctl.bat status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 11.1.0.1.0
OMS Version       : 11.1.0.1.0
Protocol Version  : 11.1.0.0.0
Agent Home        : C:\app\agent_home\agent11g
Agent binaries    : C:\app\agent_home\agent11g
Agent Process ID  : 2288
Agent URL         : https://MDDBSVR01:3872/emd/main/
Repository URL    : https://WIN-1WPTHCMPJYT:1159/em/upload
Started at        : 2012-03-14 15:50:50
Started by user   : SYSTEM
Last Reload       : 2012-03-14 15:50:50
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far :     0.00
Number of XML files pending upload           :      100
Size of XML files pending upload(MB)         :    11.42
Available disk space on upload filesystem    :    76.64%
Last attempted heartbeat to OMS              : 2012-03-15 09:58:43
Last successful heartbeat to OMS             : unknown
---------------------------------------------------------------
Agent is Running and Ready



C:\app\agent_home\agent11g\BIN>emctl.bat status agent scheduler
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Scheduler status Summary at 2012-03-15 09:22:02
Schedule Attempts Delay Percentage :: 0.00
Number of currently running scheduled items :: 0
Number of currently ready scheduled items :: 0
Number of scheduled items :: 14
Running entries::
Ready entries::
Scheduled entries::
2012-03-15 09:22:04 : Ping Manager
2012-03-15 09:22:51 : host:MDDBSVR01:LogFileMonitoring
2012-03-15 09:22:55 : host:MDDBSVR01:Network
2012-03-15 09:23:50 : Compute Metric Delay Ratio
2012-03-15 09:26:11 : host:MDDBSVR01:Load
2012-03-15 09:26:49 : Upload Manager
2012-03-15 09:28:17 : host:MDDBSVR01:Filesystems+TotalDiskUsage+DiskActivity+PagingActivity+CPUUsage
2012-03-15 09:37:23 : oracle_emd:MDDBSVR01:3872:ProcessInfo
2012-03-15 09:50:52 : Upload Files Recount
2012-03-15 09:52:27 : oracle_emd:MDDBSVR01:3872:EMDUploadStats
2012-03-15 10:10:24 : oracle_emd:MDDBSVR01:3872:ThreadCPUUsageSummary
2012-03-15 15:51:01 : host:MDDBSVR01:Inventory
2012-03-15 15:51:21 : host:MDDBSVR01:oracle_security
2012-03-21 16:02:46 : oracle_emd:MDDBSVR01:3872:EMDIdentity+EMDUserLimits
---------------------------------------------------------------
Agent is Running and Ready

还有就是，现在从agent与OMS服务器之间互ping是不通的。网络部出于安全考虑ping被禁掉，严格要求ping不能打开。是不是跟ping有关系呢？

回复 只看该作者 道具 举报

5#
发表于 2012-3-15 18:45:14
2012-03-14 17:02:57,093 Thread-3652 ERROR http: nmehl_connect_internal: failed to get host info. Could not resolve name
2012-03-14 17:02:57,093 Thread-3652 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1

nmehl_connect_internal Could not resolve name ， 存在HOSTNAME 无法解析的情况
pingManager: nmepm_pingReposURL: Cannot connect to https://WIN-1WPTHCMPJYT:1159/em/upload: retStatus=-1

AGENT 连接OMS 失败


确保  AGENT 上可以解析 WIN-1WPTHCMPJYT这个HOSTNAME 而不是 IP ，确保 OMD 和  AGENT之间可以连通PING 。


如果还有问题， 继续上传最新的emagent.trc

回复 只看该作者 道具 举报

6#
发表于 2012-3-16 12:03:03
非常感谢Maclean，问题基本定位。防火墙上给OMS开的端口太少，oms会用一个随机端口与agent3872收集信息。以上 为个人分析。

回复 只看该作者 道具 举报

返回列表
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

QQ|手机版|Archiver|Oracle数据库数据恢复、性能优化

GMT+8, 2024-11-15 07:35 , Processed in 0.051528 second(s), 24 queries .

Powered by Discuz! X2.5

© 2001-2012 Comsenz Inc.

回顶部
TEL/電話+86 13764045638
Email service@parnassusdata.com
QQ 47079569