Physical host collecting stops after 7 days

Article Number: 502895Article Version: 3 Article Type: Break Fix



ViPR SRM 4.0.2

Physical hosts collected on by the Generic-RSC service are no longer collecting data after 7days of the service being up. After seven days the service still shows as running and the logs still show only issues as seen at startup, yet data is no longer being updated for those hosts.

Customer had to restart the service to begin active collection again.

No issues with Memory, File Space, Task Failure, Server Connection Failure, etc…

Overall health of the environment looked good.

Health report did not show any heap issues.

Upon Inspection we see that the time for completing collection goes up gradually during the course of the week after startup.

Completed collecting configuration GENERIC-SCRIPTS for context <hostname> in 298432 msec

.

.

.

Completed collecting configuration GENERIC-SCRIPTS for context <hostname> in 1520425 msec

Completed collecting configuration GENERIC-SCRIPTS for context <hostname> in 1624644 msec

Completed collecting configuration GENERIC-SCRIPTS for context <hostname> in 1701052 msec

Inspection of the SP setup for Generic-RSC revealed that there were 270 hosts discovered on one generic-rsc instance. The Java Heap was set to Default of 2GB and had the default 5 Threads.

According to Performance and Scalability guidelines the Generic Host Guidelines.

User-added image

Customer set the Java Heap to 4GB and set the Threads to 20 on the collector.

To change the thread count:

In centralized management, click on SolutionPacks on the left side of the screen.

Under Other components find the Generic-RSC SP for CollectorX Click the edit symbol and open the last section as pictured below and change the threads then hit reconfigure.

User-added image

To change the Java Heap

To increase the Java Heap for the Generic-RSC collector manager.

In centralized management, click on collector SV65515 under physical overview.

Under services click on Generic-RSC

Then click the configure service button as illustrated below.

User-added image

After performing these configuration changes the collection stabilized. Further review noted that there was no day to day increase in collecting times.

.p

Related:

Leave a Reply