Data Collection Retry Timeout

[Peter Palsherm]

Hello after Updating HP SIM to Version 5.2 with SP1 - Windows I get about 300 of this messages:

Event Name: Data Collection Retry Timeout
URL: http://ntrhe7.toennies.net:280/mxportal/MxContextLaunch.jsp?systems=lxrhe35_rib&tool=System%20Page
Event originator: lxrhe35_rib
Event Severity: Minor
Event received: 21-May-2008, 10:44:28
Event description: Data Collection retry was abandoned for this system at the end of the timeout period


Where can I turn off this messages?

Regards,

Peter

[Jason Menear_1]

Good question - I saw the same thing. Did you find a resolution?

Jason

[Jimmy Rueedi]

same here.
It looks like there is a message for each system, which is monitored by SIM.
On the other hand, there is no task or task result within the task list (even "Task & Logs" - "View Task Results" or "View all scheduled Tasks") visible...

Did it occured only once, or have I to expect more "Spam- Storms" like this?

Regards
Jimmy

[YVERNEAU]

I've had the same problem when I've upgrading Hp SIM 5.1 vers 5.2
After the upgrade, you have to disabled the WBEM protocol in options, protocols settings, global protocol settings.

[Dhanesh Amirthalingam]

Hi

I did the same but the issue is not resolved

any new updates

[Peter Palsherm]

Hello,

now I have updated to:

Systems Insight Manager 5.3 with SP1 - Windows

but the same old 300 "Data Collection Retry Timeout" Messages appear.

Regards,

Peter

[sdb_2]

Peter,

Try this:

Go to options -> protocol settings -> global protocol settings and disable the checkboxes for WBEM, WS-MAN and DMI (suppose you're not using them).
This solved the problem for me.

HPSIM tries to collect data from all your servers with the protocols you enabled in options -> protocol settings -> global protocol settings, so if WS-MAN is enabled here, he will try to collect data with it. If your servers doesn't support this protocol, it generates this timeout message for each one of them.

Hope this helps.

[Peter Palsherm]

Thanks,

for the Info!
I have disabled the Protocols.
Lets wait and see if the Timeout appears

Regrads,

Peter

[Adam Snow]

We have been having the same issue for along time. I tried the steps mentioned above and it didn't fix it.

[Alp Konakkuran]

We also have this issue, we have over 5000 servers we monitor on 2 SIM boxes and ever since the monitored servers went to win2k3 with PSP 8.30 we get this issue.
HP SIM version did not change and neither did the hw on the monitored systems.
I also get this error when I try to login to some of the servers SMH. It show limited info on SMH. When I hit F5 it connects fine without any errors.

"A timeout occured while loading data from the HP System Management Homepage which may result in missing or incomplete information. See the HP System Management Homepage log for additional information."
Here is the error in SMH log.

"WARNING 3/29/2011 9:18:04 AM
UI Webapps Loading Timeout -- Nav Load Time: 20s [Webapp-List: hmanics || hmaserv || hmastor || HP]"

[davidmcmurray]

Error: Data Collection retry was abandoned for this system at the end of the timeout
period

HP SIM v7.3

I have three v7.3 servers, just one does it currently.

Global Protocol Settings:

WBEM unchecked

WS-MAN unchecked

SSH unchecked

Intermittent times of day.   One to Two per day.

Thoughts welcome.

Thank you,

Dave McMurray

[Pootch]

This happens on network timeouts / or agents problems when the SIM Server tries to pull the data..

There is a weekly task for Data collection... this should be enough..

This system failed to respond to SNMP in the timeout interval.
Root Cause: The system is no longer running SNMP, or the agent is responding more slowly than the timeout value set for the system.
Corrective Action: Check network and configuration of target system.  Try adjusting the SNMP timeout value for the system in the System Protocol Settings page.  Verify the SNMP read community has not changed.  Rerun Data Collection.

Data collection on this system was aborted due to a timeout or it was abruptly stopped.  Data may be incomplete.
Root Cause: Data collection on the target system has taken longer than allowed.  This can be due to network connectivity issues, a busy target system, or timeout values set too low.
Corrective Action: Check network and configuration of target system.  Check the following settings (and adjust values as needed) using mxglobalsettings: Detached_DC_Timeout, Storage_DC_Timeout, DC_Abandon_Latency (all in seconds)



                        

[zarulzakuan]

If the server is ESXi machine and using WBEM protocol, restart the CIM server. Works most of the time for us