System Reporter 2.8 | 3PAR System Reporter User’s Guide |
11.2.2 Installation Configuration
On Windows, you can see the parameters with which the sampler was installed by typing the following command in that directory (which should contain the winserv.exe file) as follows:
#winserv.exe showconfig "3PAR System Reporter sampler"
Configuration of 3PAR System Reporter sampler:
*CommandLine sampleloop.exe
*Description: Periodically collects statistics from 3PAR InServ Storage Servers and inserts the data into the 3PAR System Reporter database.
On Linux, the parameters for the sampleloop daemon are all in the /etc/sampleloop.conf file.
11.2.3 InServ Sampling Errors
When the inservsample process for a particular InServ system <ip_name> encounters an error it logs the error in its inservsample_<ip_name>.log file and exits. The main sampleloop
process will detect that the inservsample process has exited and log the error in its sampleloop.log file. For the next sample, the sampleloop process will create a new
inservsample process to sample data from InServ <ip_name>. This new inservsample process will roll the inservsample_<ipname>.log file.
Since there is a separate inservsample process for each InServ system, errors that occur while sampling one InServ do not generally impact sampling of other InServ systems. However, in the case of timeout errors, the sampling interval for all the arrays will be stretched to the timeout limit since the sampleloop process waits until the timeout limit before it continues to the next sample.
There are two main types of errors incurred by either the inservsample process or the CLI sampler process as described in the following sections.
Troubleshooting the Sampling Components | 11.3 |