1PMLOGCHECK(1) General Commands Manual PMLOGCHECK(1)
2
6 pmlogcheck - checks for invalid data in a PCP archive
7
9 pmlogcheck [-lz] [-n pmnsfile] [-S start] [-T finish] [-Z timezone] ar‐
10 chive
11
13 pmlogcheck prints information about the nature of any invalid data
14 which it detects in the files of a PCP archive.
15 The archive has the base name archive and must have been previously
17 created using pmlogger(1).
18 Normally pmlogcheck operates on the default Performance Metrics Name
20 Space (pmns(5)), however if the -n option is specified an alternative
21 namespace is loaded from the file pmnsfile.
22 The command line options -S and -T can be used to specify a time window
24 over which metrics should be checked in Pass 3 (see below). These
25 options are common to many Performance Co-Pilot tools and are fully
26 described in PCPIntro(1).
27 The -l option prints the archive label, showing the log format version,
29 the time and date for the start and (current) end of the archive, and
30 the host from which the performance metrics values were collected.
31 By default, pmlogcheck reports the time of day according to the local
33 timezone on the system where pmlogcheck is run. The -Z option changes
34 the timezone to timezone in the format of the environment variable TZ
35 as described in environ(7). The -z option changes the timezone to the
36 local timezone at the host that is the source of the performance met‐
37 rics, as specified in the label record of the archive log.
38 The checking proceeds in a number of passes, each designed to validate
40 progressively more complex semantic relationships between the informa‐
41 tion in a PCP archive.
42
44 Each physical file of the PCP archive is processed to ensure the label
45 records are valid and consistent, and that each file contains an inte‐
46 gral number of physical records with correct header and trailer fields.
47 Any errors at this stage are usually fatal. The PCP archive is proba‐
49 bly damaged beyond repair, and no more passes of pmlogcheck are
50 attempted.
51
53 Validates the integrity of the temporal index, usually archive.index.
54 As the temporal index is (strictly speaking) optional, errors at this
56 stage are handled by marking the index as bad and ignoring it for the
57 remainder of the pmlogcheck passes.
58 Permanent repair can be achieved by removing the temporal index file
60 and then making a copy of the PCP archive using pmlogrewrite(1) or
61 pmlogextract(1). This will create a new temporal index for the copied
62 archive as a side-effect.
63
65 Validates the integrity of the metadata file, usually archive.meta.
66
68 Validates the integrity of each of the log volumes of the PCP archive,
69 usually archive.0, archive.1, etc.
70 There is some basic integrity checks to ensure the encoding of values
72 for each metric remains consistent and the values are well formed
73 across all the observations in the archive.
74 Also the timestamps for the observations are expected to be monotoni‐
76 cally increasing as the archive is tranversed.
77 Additional attention is given to counter metrics (type from
79 pmLookupDesc(3) is PM_SEM_COUNTER) which are expected to have monotoni‐
80 cally increasing values. If the values are not monotonic increasing
81 this may suggest a counter wrap has happened or there has been some
82 interruption or reset to the underlying source of the performance data
83 that is no captured in the archive.
84 For each counter metric which has been detected as having wrapped at
86 some point in the archive, pmlogcheck produces output describing the
87 metric name (with instance identifiers where appropriate), the internal
88 storage type for the metric, the value of the metric before the counter
89 wrap (with its associated timestamp), and the value of the metric after
90 the wrap (also with a timestamp).
91 pmlogcheck produces two different timestamp formats, depending on the
93 interval over which it is run. For an interval greater than 24 hours,
94 the date is displayed in addition to the time at which the counter wrap
95 occurred. If the extent of the data being checked is less than 24
96 hours, a more precise format is used (time is displayed with millisec‐
97 ond precision, but without the date).
98
100 $PCP_VAR_DIR/pmns/*
101 default PMNS specification files
102 $PCP_LOG_DIR/pmlogger/hostname
103 default directory for PCP archives containing performance
104 data collected from the host hostname.
105
107 Environment variables with the prefix PCP_ are used to parameterize the
108 file and directory names used by PCP. On each installation, the file
109 /etc/pcp.conf contains the local values for these variables. The
110 $PCP_CONF variable may be used to specify an alternative configuration
111 file, as described in pcp.conf(5).
112
114 PCPIntro(1), pmdumplog(1), pmlogextract(1), pmlogger(1), pmlo‐
115 grewrite(1), pmlogsummary(1), pmval(1), pmLookupDesc(3), pcp.conf(5),
116 pcp.env(5) and pmns(5).
117
119 All are generated on standard error and are intended to be self-
120 explanatory.
121Performance Co-Pilot PCP PMLOGCHECK(1)