perfparse-users

[Perfparse-users] My serviceperf.log does not get truncated or deleted

[Jaap H. <jaa...@ma...>]

Hi,

If I run perfparse -r --delete , the logfile does not get
truncated at all. 
My nagios.lock file is owned by root , does perfparse (which runs under
the account of user nagios) need write access to the lock file ?

I also have a more generic question:
I get "Lines dropped" when I run perfparse every 5 minutes or so,
up to 1 ~ 2 % of lines are being dropped....
Is there a verbose setting on perfparse, so that I can see what 
is going on ?

BTW, I use Nagios 1.2 , with perfparse 0.99.01 (yeah I know, it's a bit
old allready) on around 40 hosts and 200 services.

TIA,
Jaap

Re: [Perfparse-users] My serviceperf.log does not get truncated or deleted

[Yves M. <yme...@li...>]

Speaking about 0.99.08 (otherwise, please upgrade)

> Hi,
>
> If I run perfparse -r --delete , the logfile does not get
> truncated at all.

--delete is not supported any more.
Use --delete-service-log instead

> My nagios.lock file is owned by root , does perfparse (which runs under
> the account of user nagios) need write access to the lock file ?

Read access only to get the PID of nagios, then kill -1.
And rw access to the directory that contain serviceperf.log

as the perfparse user, test this:
mv serviceperf.log serviceperf.log.test
kill -1 `cat nagios.lock`

A new serviceperf.log should be created. If not, some permissions are mis=
sing !




>
> I also have a more generic question:
> I get "Lines dropped" when I run perfparse every 5 minutes or so,
> up to 1 ~ 2 % of lines are being dropped....
> Is there a verbose setting on perfparse, so that I can see what
> is going on ?

With the report option (-r) enabled, maybe (need to check the code to be =
sure)
Otherwise, no.
But you can read the drop file and see the lines. Maybe that can help ?

> BTW, I use Nagios 1.2 , with perfparse 0.99.01 (yeah I know, it's a bit
> old allready) on around 40 hosts and 200 services.

Please upgrade to 0.99.08. We should not work on that one before mid-Augu=
st (except if
we find a serious bug of course). And it looks quite stable.
Some previous version contain serious bugs and we cannot support versions=
 that have
known bugs and that we have fixed in latest versions :)

Yves

>
> TIA,
> Jaap
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technolog=
y
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Perfparse-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-users
>
>


--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- GTKtalog    - http://www.nongnu.org/gtktalog/                    -

Re: [Perfparse-users] My serviceperf.log does not get truncated or deleted

[Jaap H. <jaa...@ma...>]

On Fri, 2004-07-30 at 14:13, Yves Mettier wrote:
> Speaking about 0.99.08 (otherwise, please upgrade)
> 
> > Hi,
> >
> > If I run perfparse -r --delete , the logfile does not get
> > truncated at all.
> 
> --delete is not supported any more.
> Use --delete-service-log instead
Does not look like that works either....


> > My nagios.lock file is owned by root , does perfparse (which runs under
> > the account of user nagios) need write access to the lock file ?
> 
> Read access only to get the PID of nagios, then kill -1.
> And rw access to the directory that contain serviceperf.log
Yup , got all that

> as the perfparse user, test this:
> mv serviceperf.log serviceperf.log.test
> kill -1 `cat nagios.lock`
> 
> A new serviceperf.log should be created. If not, some permissions are missing !

And so it does.

> >
> > I also have a more generic question:
> > I get "Lines dropped" when I run perfparse every 5 minutes or so,
> > up to 1 ~ 2 % of lines are being dropped....
> > Is there a verbose setting on perfparse, so that I can see what
> > is going on ?
> 
> With the report option (-r) enabled, maybe (need to check the code to be sure)
> Otherwise, no.
> But you can read the drop file and see the lines. Maybe that can help ?
But I can't find a drop file. I was allready using "-r"

> > BTW, I use Nagios 1.2 , with perfparse 0.99.01 (yeah I know, it's a bit
> > old allready) on around 40 hosts and 200 services.
> 
> Please upgrade to 0.99.08. We should not work on that one before mid-August (except if
> we find a serious bug of course). And it looks quite stable.
> Some previous version contain serious bugs and we cannot support versions that have
> known bugs and that we have fixed in latest versions :)
Yes, I understand that. I'll upgrade and see what gives...


BTW, this may also be relevant: I use a different approach for writing
the serviceperf.log file, because I used the default (command based)
method before I started using perfparse, and stuck with that.
I choose to go that route because I allready had written some custom
tools that I used to do some reporting, based on the performance data 
output files, and would lioke to keep that as well, so I ended up using
a command that will create both files for me.
This also means the nagios process is not actually locking the file,
so I'm now considering the following:
Rename the file to a temp file. A new file will be started
automatically, no kill signals required.
Read in the temp file, and delete it.

Anyway , seems like I might be on my own for this way of working,
but thanks anyway for the help.

Regards, 
Jaap




> Yves
> 
> >
> > TIA,
> > Jaap
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> > one more big change to announce. We are now OSTG- Open Source Technology
> > Group. Come see the changes on the new OSTG site. www.ostg.com
> > _______________________________________________
> > Perfparse-users mailing list
> > Per...@li...
> > https://lists.sourceforge.net/lists/listinfo/perfparse-users
> >
> >
> 

Re: [Perfparse-users] My serviceperf.log does not get truncated or deleted

[Yves M. <yme...@li...>]

> BTW, this may also be relevant: I use a different approach for writing
> the serviceperf.log file, because I used the default (command based)
> method before I started using perfparse, and stuck with that.
> I choose to go that route because I allready had written some custom
> tools that I used to do some reporting, based on the performance data
> output files, and would lioke to keep that as well, so I ended up using
> a command that will create both files for me.
> This also means the nagios process is not actually locking the file,
> so I'm now considering the following:
> Rename the file to a temp file. A new file will be started
> automatically, no kill signals required.
> Read in the temp file, and delete it.

perfparse already does this, except that it also sends the HUP signal.
This is necessary because without this, with the temp file renamed (no in=
ode change),
nagios would continue to write to the temp file instead of recreating a n=
ew file.

Yves

--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- GTKtalog    - http://www.nongnu.org/gtktalog/                    -