Hey Mark,
----- Original Message -----
> [...]
> # pcp --archive=/var/log/pcp/pmlogger/fletch/20150603.13.28 atop
> dies with a messed up screen and glibc heap issues
Hmm, can you send me that archive? taa. Are either qa/1079 or 1080
failing for you (esp 1079 - uses a canned qa/archives/pcp-atop.*)?
> # pcp -h somehost atop
> pcp-atop: task instances: No permission to perform requested operation
> Doesn't work as root either.
The error message is correct - you don't have permission to access
proc metrics without authentication. You need to use unix: domain
socket (and get automatically authenticated as a result), or setup
authentication for remote host proc metrics.
> I've more comments - but was expecting the above to work ..? Also, the
> man page says "pcp-atop -r" will replay todays archive from
> /var/log/pcp/pmlogger/<pmcd.hostname>/.... but I get a usage message.
>
> Also, are we intending to still support the native atop raw data format
> for recording and playback.
Heh, definitely not - its another sar-like format, and we cannot take on
maintenance of that sort of thing. We'll be switching in our own format
there, just like our earlier atop python code did.
> Or just switch to PCP archives and/or archive
> folios?
Yep - need that to be feature-compatible to our existing atop. WIP, not
too far off done now.
> How much back-compat with upstream will we be maintaining?
At this stage, its simply a replacement for our existing implementation
of atop (which is all about emulating the useful *display* capabilities).
No more than that, we certainly do not want to take on back-compat of the
ondisk formats for utilities like this (nor others from pcp-system-tools,
like collectl) for replay. We could do an archive converter - but, not
worth doing until someone asks for it IMO (then it'd be prioritised along
with everything else we're working on).
cheers.
--
Nathan
|