Data may appear to be old when it is not, Setting the time or time zone – HP Matrix Operating Environment Software User Manual
Page 167
that they are hung, (because all the above situations are fine, but still no data), first try restarting
the individual services:
•
For a Windows CMS, restart:
— HP Agentless Data Collector Service (the agentless collector service for Windows
systems)
— HP Agentless Collection for Linux Systems (the agentless collector service for Linux
systems)
— HP Insight Control virtual machine management (the VMM service)
•
For an HP–UX CMS, type from the command line:
# /sbin/init.d/hp_capad_service stop
Stopping HP Agentless Collection for Linux Systems...
Waiting for HP Agentless Collection for Linux Systems to exit...
Stopped HP Agentless Collection for Linux Systems.
# /sbin/init.d/hp_capad_service start
Starting HP Agentless Collection for Linux Systems...
Started HP Agentless Collection for Linux Systems.
If restarting the service(s) does not work, try rebooting the CMS.
Other possibilities
For suspected WMI issues on Microsoft Windows nodes (applies to agentless
collection on Windows and virtual machine management/Hyper-V data collection), if nothing
else works, try running the following command on the managed system to re-register WMI
performance classes that may have become un-registered, causing data collection errors:
wmiadap /f
For agentless collection on Linux, make sure that SSH (sshd) is running on the managed system.
Data may appear to be old when it is not
When time or time zone on a managed node is set incorrectly (that is, it is not synchronized with
the clock time on the CMS), the user may collect data and see only old dates for data collected.
Suggested action: You must complete the following tasks (the process is different for each
operating system):
1.
Correct the time or time zone on your managed node.
2.
Stop and restart the Utilization Provider daemon where the UP is in use.
Brief instructions for these tasks are provided here.
Setting the time or time zone
On an HP-UX or Linux managed node, use the date(1) command to set the correct time. On
an HP-UX system, the source of the time zone varies depending on the local configuration. See
the setting for the TZ variable in the files /etc/profile or /etc/TIMEZONE or the file /etc/
defaults/tz
, if the TZ variable is not set. (For more information, see the manual pages for
ctime(3C)
and environ(5). On SuSE Linux, see the file /etc/sysconf/clock. For other
versions of Linux, consult the operating system documentation.
On Microsoft Windows, right-click on the time displayed at the right end of the task bar and
select Adjust Data/Time. Select the Time Zone tab on the dialog box and select the correct time
zone from the drop-down list at the top. Click OK to close the dialog box and use the new time
zone.
Stopping and restarting the Utilization Provider daemon
On HP-UX and Linux, use the following command:
kill `ps -ef | grep utild | grep -v grep | awk '{ print $2 }'`
On Windows 2003 Server: Start
→Manage Your Server→Tools and Updates→Administrative
Tools
→Services. Look for HP UtilProvider Data Collector in the Name column. Right click
on the row and select Stop. Wait for it to stop and then right-click on it again and select Start.
Close the Services window, the Administrative Tools window and the Manage Your Server
window.
Data may appear to be old when it is not
167