HP 3PAR System Reporter Software - Manual (Page 216)

When reporting a problem with sampling, please provide the entire log directory.
CAUTION: If you get an error in a sampling component that causes the service or daemon to
stop, save the entire log directory before restarting the service or daemon so that you do not lose
the error information in the logs.
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:
nl
# winserv.exe showconfig "3PAR System Reporter sampler"
Configuration of 3PAR System Reporter sampler:
nl
-displayname 3PAR System Reporter sampler (managed by WinServ)
-noninteractive
-binary C:\Program Files\3PAR\System Reporter\winserv.exe
-start auto
-errorcontrol normal
-depends
-loadordergroup
-user LocalSystem
-ipcmethod blind
*CommandLine sampleloop.exe -dbtype sqlite -db E:/inservstats/inservstats
-noexpand
*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.
Sampling Errors
When the inservsample process for a particular HP 3PAR Storage System encounters
an error it logs the error in its inservsample_.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 . This new inservsample process will roll the
inservsample_.log
file.
Since there is a separate inservsample process for each system, errors that occur while sampling
one HP 3PAR Storage System do not generally impact sampling of other 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.
Errors incurred by the inservsample process
Errors incurred by the inservsample process are typically database errors including:
•
Loss of network connectivity to the database server.
•
Database server errors. One example when using MySQL as the database is if the
max_allowed_packet parameter is not sufficiently large (see
“Setting the max_allowed_packet
parameter” (page 40) ) and the inservsample process gets the error “MySQL server has gone
away”.
216 Troubleshooting