После добавления нового узла в Oracle Grid Control 10g, в логах агента я заметила такие ошибки в emagent.trc:
2008-04-25 15:32:17,560 Thread-14019 WARN collector: Error exit. Error message: No username specified for WBEM fetchlet.
2008-04-25 15:37:34,865 Thread-14064 ERROR fetchlets.wbem: No username specified for WBEM fetchlet.
2008-04-25 15:37:34,865 Thread-14064 ERROR engine: [host,eccisdb,ProjectResourceUsage] : nmeegd_GetMetricData failed : No username specified for WBEM fetchlet.
2008-04-25 15:37:34,865 Thread-14064 WARN collector: Error exit. Error message: No username specified for WBEM fetchlet. Такая же ошибка была в веб-интерфейсе Oracle Grid Control:Host: agenthost55 > Metric Collection Errors >
Error Details
Target: agenthost55
Type: Host
Metric: Aggregate Resource Usage Statistics (By Project)
Collection Timestamp: 09-Apr-2008 12:24:18
Error Type: Collection Failure
Message: No username specified for WBEM fetchlet.
Ниже описание причины ошибки и ее решение из Металинка Note:271632.1:
Cause:
Beginning with EM 10g, certain OS vendors have enhanced their systems to include a new metric - Aggregate resource usage statistics, gathered by User and by Project. These metrics are collected by using the "CIM Object Manager" on the Solaris 9 host. In order to get this information, the CIM Object Manager needs to be supplied with Username and Password of a user on that host so that authentication can successfully happen
Solution:
From within the EM 10g Grid Control UI,
1. Click on Targets -> Host tab
2. Select your Solaris 9 host and go to the Hosts Home page (repeat these steps for each Solaris 9 host)
3. Click on the Monitoring Configuration link at the bottom right side of the page
4. Enter your OS username/password. It's best to enter a user that has DBA privileges.
5. Click save.
This will update the central Management Agent's targets.xml file on the Solaris 9 host and force a reload of the configuration files. The error above should stop.
0 коммент.:
Отправить комментарий