For the program that I am writing, I want to be able to append an already existing archive, as the name is derived in a specific way, so I cannot name the archive something different if it is for the same host. However, I am taking the results for the previous x amount of hours, so I would like to be able to append to an existing archive. This would only be an issue if pmlogger is stopped and restarted. Currently, pmlogger is being started from a bash script file. Is there an option when starting pmlogger from the terminal to have it append to file "x" if it exists, else create it?
Thanks, Rohan
Also, I see that in the pmSetMode() documentation, to read an archive in reverse order you use pmSetMode(PM_MODE_BACK, timeval, delta). The example gave the valueÂ0x7fffffff for timeval.tv_sec, but I was wondering, is that guaranteed to read from the end of the archive? In my case, I always just want to read the last x entries in the log.
Thanks, Rohan
Hi, Sorry I still haven't had a chance to really look at the issue with connecting pmlogger to a remote host yet, but in a previous e-mail, Nathan mentioned result->timestamp, which I'm assuming is the result you get from calling context.pmFetch(metric_ids), correct? How do I access this timestamp from Python? I want to put the timestamp for when a metric was fetched into a list of timestamps.
Thanks, Rohan
On 02/07/15 02:07, Rohan Arora wrote:
> I tried following the directions on that page, the telnet error that I
> get is "Connect failed" rather than "Connection refused". I have
> verified that pmcd is running on the host I am trying to connect to as
> it is shown as running as a service, and I am able to use pminfo as
> well. Does it matter that the host is protected using a putty private
> key when using ssh? I am not sure where to go from here really.
Are you able to use pminfo on the same system connecting to the remote pmcd (i.e. the same client-server arrangement where pmlogger is not working)? That would be odd.
In any event the following output would help diagnose ...
On the client system
$ pminfo -v -Dcontext -h <remotehost> disk.all
$ echo "log mandatory on once { disk.dev }" | pmlogger -Dcontext -h <remotehost> -l /dev/tty foobar
^C
$ pminfo -a foobar
And on the remote system, the contents of:
/etc/pcp/pmcd/pmcd.conf
/var/log/pcp/pmcd/pmcd.log
_______________________________________________
pcp mailing list
pcp@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/pcp
|