perfparse-devel — Development Issues

[Perfparse-devel] Patch to compile 0.105.3 on Solaris

[Yves <yme...@pe...>]

Hi all,

Perfparse does not compile on Solaris. Reason : when you link, you have t=
o begin with
the more specific libraries first (eg libpp_mysql) and finish with the le=
ss specific
ones (eg libpp_common, then glib...)
On some systems, including my solaris, when you put a library first, and =
then another
that use the first one, the linker does not find the functions of the fir=
st one.

So the order is always:
libpp_mysql libpp_common libmysqlclient gd glib
or
libpp_mysql libmysqlclient libpp_common gd glib
(gd and glib don't depend on the other one so you can switch them and wri=
te glib gd or
gd lib)

I also removed the dependancy of perfparse.cgi to gd : perfparse.cgi does=
 not need gd :)

I have tested neither 0.105.3 with my patch nor 0.105.3 without. It just =
compiles for me
with the patch.

Enjoy :)

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/                 -
- Perfparse   - http://www.perfparse.org/                          -

[Perfparse-devel] New version, 0.105.4

[Ben C. <bcl...@pe...>]

Dear contributers,

In my rush to get everything out, several bugs were left in the new code 
for displaying Tim's raw summary data.  I've released 0.105.4 with these 
fixed.

Regards,

Ben


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php

[Perfparse-devel] introducing and need councils ....

[Marcilly, B. <Bru...@lo...>]

Hello everybody ,

I made a point of introducing and to me of explaining you my step among
you... 
I'am a totaly newbies in C , and in environment system and networks !
I worked for a long time in "grands systemes IBM" (I don't know the
translation to English), in COBOL, and i have a statute of leader junior
project and today , i want to reorientate myself towards new technologies .
So , I wish to invest myself near you in the perfparse project in order to
acquire these new competences, with my modest means. 

Yves having less time for this project, it proposed to me thus that with
Remi, to join you and to take part the evolution of perfparse has.  ... as I
subject my profile and my level to you and hopes as you will be able to
switch me and to advise me .
Which work can you give me to begin and who could help you, going in this
direction?? 

thank you for your answers and your councils .

bests regards

Bruno  

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

Re: [Perfparse-devel] subscription

[Ben C. <bcl...@pe...>]

You may complete this your self from the URI:

http://sourceforge.net/mail/?group_id=109355

Regards, Ben :)

dew...@fr... wrote:

> 
> hello,
> 
> is it possible to add me to these mailing lists please?
> 
> thank you
> 
> rémi dewynter
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Perfparse-devel mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-devel
> 


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php

[Perfparse-devel] subscription

[<dew...@fr...>]

hello,

is it possible to add me to these mailing lists please?

thank you

r=E9mi dewynter

Re: [Perfparse-devel] EXITs

[Yves <yme...@pe...>]

>> 1/ Implement a basic pp_exit() function :
>> void pp_exit(void) {
>>   exit();
>> }
>
> void pp_exit(int status)
> preferably.

Yes of course. In the future, it could become pp_exit(int status, int par=
am) where param
is an int or can be something else (like what to close and what not to cl=
ose). Depends
on what we need.

>> 2/ Replace *all* calls to exit() with pp_exit(). Don't make a macro fo=
r that. It has
>> to
>> be a real replacement.
>
> there are around 50 exit calls :)

OK. Much work, but can be done.


>> 4/ work on pp_exit() in order to make it do what we want. Also remove =
the calls to
>> atexit() and do something else.
>
> In the case of this problem: if the main process finishes, you should
> call close_all_log_sources, but any subproces that exits should not do
> this. perhaps pp_exit can do different things depending on the status
> flag. So I have a feeling this will not be trivial.

With pp_exit, it can become trivial, with the use of additionnal paramete=
rs to pp_exit.
You can think of a binary OR of options to say what pp_exit should do and=
 should not do.
For example :
pp_exit(EXIT_FAILURE, CLOSE_ALL | WRITE_A_NICE_MESSAGE_IN_THE_LOG |
DO_NOT_REMOVE_THE_PIPE);


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/                 -
- Perfparse   - http://perfparse.sf.net/                           -

Re: [Perfparse-devel] EXITs

[Tim W. <tim...@gm...>]

On Thu, 20 Jan 2005 14:22:03 +0100 (CET), Yves <yme...@pe...> wrote:
> The registered atexit() functions are inherited by subprocesses. I found that problem
> when I coded periodic cleanup procedures.
> Now you find that problem too.
> Maybe it's time to think of a smarter way to exit ?
> Reimplement exit() with a way to remove atexit() handlers ? I found no way to remove a
> handler that was registered with atexit. If you know one, maybe all what I say below is
> N/A ? :)
> 
> Here is what I suggest (I hope Remi and Bruno have had time to subscribe to this list)
> 1/ Implement a basic pp_exit() function :
> void pp_exit(void) {
>   exit();
> }

void pp_exit(int status)
preferably.

> 
> 2/ Replace *all* calls to exit() with pp_exit(). Don't make a macro for that. It has to
> be a real replacement.

there are around 50 exit calls :)

> 
> 3/ Make a macro for exit() for security :
> void unexpected_exit(void) {
>   pp_log(..., "This is a bug : this function should not have been called");
>   exit()
> }
> #define exit unexpected_exit
> 
> Any programmer who would then use exit() (because they don't necessarily know about
> pp_exit) would generate this message.
> 
> 4/ work on pp_exit() in order to make it do what we want. Also remove the calls to
> atexit() and do something else.

In the case of this problem: if the main process finishes, you should
call close_all_log_sources, but any subproces that exits should not do
this. perhaps pp_exit can do different things depending on the status
flag. So I have a feeling this will not be trivial.

> 
> Tim, I don't have an idea for a shorter way for you to test. And I think this change is
> necessary, at least for perfparsed.

I agree.

Tim.

> 
> 
> > FYI:
> > I tried to register my own atexit function in perfparsed, that calls
> > storage_atexit & close_all_log_sources.
> > Unfortunately, this function gets called serveral times (each time a
> > forked subprocess exits), and hence it does not do what you'd want.
> > I'm not experienced enough in this matter to figure out how to get the
> > exit handler to run only when the main process exits. If you have an
> > idea how to do this, let me know, and I'll try it to see if it fixes
> > this problem.
> >
> > Tim
> 
> 
> --
> - Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
> - GPG key     - http://ymettier.free.fr/gpg.txt                    -
> - Maitretarot - http://www.nongnu.org/maitretarot/                 -
> - Perfparse   - http://perfparse.sf.net/                           -
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Perfparse-devel mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-devel
>

Re: [Perfparse-devel] EXITs

[Yves <yme...@pe...>]

The registered atexit() functions are inherited by subprocesses. I found =
that problem
when I coded periodic cleanup procedures.
Now you find that problem too.
Maybe it's time to think of a smarter way to exit ?
Reimplement exit() with a way to remove atexit() handlers ? I found no wa=
y to remove a
handler that was registered with atexit. If you know one, maybe all what =
I say below is
N/A ? :)

Here is what I suggest (I hope Remi and Bruno have had time to subscribe =
to this list)
1/ Implement a basic pp_exit() function :
void pp_exit(void) {
  exit();
}

2/ Replace *all* calls to exit() with pp_exit(). Don't make a macro for t=
hat. It has to
be a real replacement.

3/ Make a macro for exit() for security :
void unexpected_exit(void) {
  pp_log(..., "This is a bug : this function should not have been called"=
);
  exit()
}
#define exit unexpected_exit

Any programmer who would then use exit() (because they don't necessarily =
know about
pp_exit) would generate this message.

4/ work on pp_exit() in order to make it do what we want. Also remove the=
 calls to
atexit() and do something else.

Tim, I don't have an idea for a shorter way for you to test. And I think =
this change is
necessary, at least for perfparsed.



> FYI:
> I tried to register my own atexit function in perfparsed, that calls
> storage_atexit & close_all_log_sources.
> Unfortunately, this function gets called serveral times (each time a
> forked subprocess exits), and hence it does not do what you'd want.
> I'm not experienced enough in this matter to figure out how to get the
> exit handler to run only when the main process exits. If you have an
> idea how to do this, let me know, and I'll try it to see if it fixes
> this problem.
>
> Tim


--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

Re: [Perfparse-devel] EXITs

[Tim W. <tim...@gm...>]

FYI:
I tried to register my own atexit function in perfparsed, that calls
storage_atexit & close_all_log_sources.
Unfortunately, this function gets called serveral times (each time a
forked subprocess exits), and hence it does not do what you'd want.
I'm not experienced enough in this matter to figure out how to get the
exit handler to run only when the main process exits. If you have an
idea how to do this, let me know, and I'll try it to see if it fixes
this problem.

Tim

On Thu, 20 Jan 2005 11:36:16 +0100 (CET), Yves <yme...@pe...> wrote:
> > In an attempt to figure out why the 'kill' does not induce the same
> > effect on Nagios, I concluded that the reason is that kill sends a
> > SIGTERM to perfparsed, which is nicely handled in log_reader.c. The
> > sighandler _closes all log sources_.
> > A simple exit somewehere in the application does not, and subsequent
> > write attempts to the pipe are hanging (blocked).
> >
> > Question 1: is my conclusion correct?
> 
> I am not sure, but I would say yes.
> 
> > Question 2: if so, is there any way you can catch an exit call with a
> > signal handler? Or should you use something like raise(SIGxxx) instead
> > of exit?
> 
> Yes, and it is already implemented.
> We use atexit() to catch the exit call.
> 
> When you kill the application, there is a signal handling, that only wait for the end of
> critical operations before the normal behaviour that is leaving graciously.
> 
> When perfparsed exit, there are places where we cannot work with the atexit() registered
> functions. So it does not exits with exit() but with _exit(). Maybe this is where to
> change things ?
> But I have a better idea : what about creating our own exit() function, that call the
> functions we register with atexit() ? And don't use exit(), _exit() and atexit() at all
> ?
> This is some big development.
> 
> Tim and Ben (and others) could you check if what I say is correct ? How much work it
> represents ? If this is not too hard, maybe Bruno and Remi can do it ?
> (they have not been introduced yet, but I'm waiting that they manage to install nagios
> and perfparse : they began 2 days ago).
> 
> > (Q3: has anyone else experienced this problem?)
> 
> Maybe you should ask nagios mailing-list about this, to know if somebody had this
> problem and how they solved it ? However, the bug is in perfparse, not in nagios, and it
> has to be fixed in perfparse.
> 
> Yves
> --
> - Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
> - GPG key     - http://ymettier.free.fr/gpg.txt                    -
> - Maitretarot - http://www.nongnu.org/maitretarot/                 -
> - Perfparse   - http://perfparse.sf.net/                           -
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Perfparse-devel mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-devel
>

Re: [Perfparse-devel] EXITs

[Yves <yme...@pe...>]

> In an attempt to figure out why the 'kill' does not induce the same
> effect on Nagios, I concluded that the reason is that kill sends a
> SIGTERM to perfparsed, which is nicely handled in log_reader.c. The
> sighandler _closes all log sources_.
> A simple exit somewehere in the application does not, and subsequent
> write attempts to the pipe are hanging (blocked).
>
> Question 1: is my conclusion correct?

I am not sure, but I would say yes.

> Question 2: if so, is there any way you can catch an exit call with a
> signal handler? Or should you use something like raise(SIGxxx) instead
> of exit?

Yes, and it is already implemented.
We use atexit() to catch the exit call.

When you kill the application, there is a signal handling, that only wait=
 for the end of
critical operations before the normal behaviour that is leaving graciousl=
y.

When perfparsed exit, there are places where we cannot work with the atex=
it() registered
functions. So it does not exits with exit() but with _exit(). Maybe this =
is where to
change things ?
But I have a better idea : what about creating our own exit() function, t=
hat call the
functions we register with atexit() ? And don't use exit(), _exit() and a=
texit() at all
?
This is some big development.

Tim and Ben (and others) could you check if what I say is correct ? How m=
uch work it
represents ? If this is not too hard, maybe Bruno and Remi can do it ?
(they have not been introduced yet, but I'm waiting that they manage to i=
nstall nagios
and perfparse : they began 2 days ago).

> (Q3: has anyone else experienced this problem?)

Maybe you should ask nagios mailing-list about this, to know if somebody =
had this
problem and how they solved it ? However, the bug is in perfparse, not in=
 nagios, and it
has to be fixed in perfparse.

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/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-devel] EXITs

[Tim W. <tim...@gm...>]

All,

I'd like to have your input on the following problem:
whenever things go wrong in perfparsed (usually a problem with the
database), the application will exit immediately. In the case of
perfparsed using the pipe method as input, this has a very nasty
side-effect on Nagios: every process sending data to the pipe never 
ends, and Nagios's check latency times start to skyrocket.

This behaviour is not seen when you manually kill perfparsed.

In an attempt to figure out why the 'kill' does not induce the same
effect on Nagios, I concluded that the reason is that kill sends a
SIGTERM to perfparsed, which is nicely handled in log_reader.c. The
sighandler _closes all log sources_.
A simple exit somewehere in the application does not, and subsequent
write attempts to the pipe are hanging (blocked).

Question 1: is my conclusion correct? 
Question 2: if so, is there any way you can catch an exit call with a
signal handler? Or should you use something like raise(SIGxxx) instead
of exit?

(Q3: has anyone else experienced this problem?)

Regards,
Tim

[Perfparse-devel] check_perfparse_version

[Tim W. <tim...@gm...>]

All,
a small remark about the wording used in check_perfparse_version.
This is what I get when the database version is incorrect:
 
ERROR Database schema version is not correct. Current version 0.18
Required version 0.15 | pp_ver=0.15 true_ver=0.18

It says: required version 0.15 ?? I guess this should be the other way
around, no?

Tim

Re: [Perfparse-devel] PostgreSQL Storage

[Ben C. <bcl...@pe...>]

Priewasser,

I have been talking to my partner Yves and we believe the best way to 
convert the product is as follows:


1.  Convert the database schema:

	contrib/postgresql_create.sql
	contrib/postgresql_delete.sql

Try to keep to ANSI-SQL.  Eg, use BOOL, TRUE and FALSE which MySQL does 
not support.  Rather than copying MySQL including it's short fallings :)

This stage will give you a good idea of the challange to complete the work.


2.  Two bits of work here, storage module and DBMS library.

(i) Copy modules/storage_mysql.* to modules/storage_postgresql.*

Edit where required.  Keep the .h the same in all cases.

(ii) Copy directory libpp_mysql to libpp_postgresql.

Edit all parts, starting with dbms.c.  Please keep .h files the same.


3. The non-graph CGI code.

In the CGI code, check the SQL commands and replace where needed using 
syntax similar to:

#ifdef MYSQL
	"SELECT * WHERE boolean_field = 1"
#elseif POSTGRESQL
	"SELECT * WHERE boolean_field = TRUE"
#endif

These definitions do not work yet.  If you continue this work, these 
will be added.


4.  The graph module.

Yves is re-writing this to access many data sources.  At this stage 
probably best to wait until this work is a little more mature.  I will 
be writing a MYSQL module at this point, so we can do this together.



A lot has been said in response to your original email in a short time. 
  I hope we haven't confused you.  We are excited about what your work 
will do for our product!

Please let us know your feelings and what you think of the challange.

Regards,

Ben & Yves.








Priewasser, Friedrich wrote:

> Hello,
> 
> We aim to use PostgreeSQL for some database purposes. We are using perfparse and we'd like to use a PostgreSQL storage intead of the MySQL storage for it.
> My question is: Is there any focus on creating a PostgreSQL storage at the moment?
> If yes, how far you got till now? 
> If no, we want to create such a storage. If we do so, should we use the MySQL storage as base for our development and are ther any other tips?
> 
> Regards,
> Friedrich 
> 


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php

Re: [Perfparse-devel] PostgreSQL Storage

[Yves <yme...@pe...>]

> Hello,
>
> We aim to use PostgreeSQL for some database purposes. We are using perf=
parse and we'd
> like to use a PostgreSQL storage intead of the MySQL storage for it.
> My question is: Is there any focus on creating a PostgreSQL storage at =
the moment?
> If yes, how far you got till now?
> If no, we want to create such a storage. If we do so, should we use the=
 MySQL storage as
> base for our development and are ther any other tips?

Today, there has only been mails of people asking if it is is out plans t=
o do it or not.
So if you can do it, it would be wonderful for the project, for all who w=
ould like
postgresql instead of mysql like you :)

Some tips ?
Well, for the parser, this should be easy :
- have a look on modules/storage_print.h (useless in production, but a go=
od example), on
modules/storage_mysql.h, and in fact, on all the files in the directory m=
odules/
- Take one of those files, hack it, and make your own storage module for =
postgresql.

For the db tools, no work has be done, and neither Ben or me will do it i=
n the short
future, just because we have other projects on perfparse before this :)

For the CGIs, may I ask you to wait a little ? My next project is to work=
 on perfchart
in order to put a modular system to load plugins to read from mysql and d=
irectly from
perfparsed. When this system is ready, you will be able to hack one of th=
e 2 plugins and
make yours for postgresql.
Then, the missing CGIs are perfparse.cgi and perfgant.cgi. I hope it will=
 not be too
hard to let them use the plugins of perfchart.

So if you finised the postgresql storage module for perfparsed and are st=
ill waiting for
me for perfchart, you will be able to do something on the db tools (insta=
ll, upgrade and
clean the database).

Merry Christmas :)
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/                 -
- Perfparse   - http://perfparse.sf.net/                           -

Re: [Perfparse-devel] PostgreSQL Storage

[Ben C. <bcl...@pe...>]

Priewasser,

There has been a lot of discussion about other DBMS's.  Oracle, 
PostgreSQL and others.  For what ever reason this seemed to come to nothing.

I can speak for all developers when I say we would be extremely excited 
and interested in a PostgreSQL port.  Please take a look and expect as 
much support as possible from my self, Yves, Flo and other interested 
parties.

At the moment our ideas are very simple:

#ifdef MYSQL
#elseif POSTGRESQL
#endif

(Or similar variable supplied by a configuration option programmed by Yves.)

I see the work in a few short parts: (Yves will probably clarify a few 
points.)

- Create new create/delete scripts in 'contrib'.

- Create a new lib libpp_psql as a copy of libpp_mysql.

- Edit dbms.c as above.  Try to leave dbms.h as is.  Edit other code in 
lib to adjust where needed.

- Examine the code for all SQL queries, and adjust where needed for 
PostgreSQL, again as above.

This is actually less than it seems.  If you want to have a look at 
that, please do.

Let us know how you get on, and please let us know if you need more _or_ 
less support!

You may also use our mailing list perfparse-devel-int for a more 
free-flowing relaxed discussion, if you want to involve developers in a 
public conversation.

Kind regards,

Ben Clewett.




Priewasser, Friedrich wrote:

> Hello,
> 
> We aim to use PostgreeSQL for some database purposes. We are using perfparse and we'd like to use a PostgreSQL storage intead of the MySQL storage for it.
> My question is: Is there any focus on creating a PostgreSQL storage at the moment?
> If yes, how far you got till now? 
> If no, we want to create such a storage. If we do so, should we use the MySQL storage as base for our development and are ther any other tips?
> 
> Regards,
> Friedrich 
> 


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php

[Perfparse-devel] PostgreSQL Storage

[Priewasser, F. <Fri...@fa...>]

Hello,

We aim to use PostgreeSQL for some database purposes. We are using =
perfparse and we'd like to use a PostgreSQL storage intead of the MySQL =
storage for it.
My question is: Is there any focus on creating a PostgreSQL storage at =
the moment?
If yes, how far you got till now?=20
If no, we want to create such a storage. If we do so, should we use the =
MySQL storage as base for our development and are ther any other tips?

Regards,
Friedrich=20

--=20
Friedrich Priewasser
Software Engineer
Fabalabs Software GmbH
Honauerstra=DFe 4
A-4020  Linz
Telefon: +43 732 2468 5091
e-mail: mailto:fri...@fa...
http://www.fabalabs.org

[Perfparse-devel] watch perfparsed

[Yves <yme...@pe...>]

Hi,

I don't remember who wanted to watch perfparsed with nagios.
Since 0.104.4ym1 (don't use 0.104.4ym1 but the latest version please), pe=
rfparsed
creates a new file:
-> in the config file, "Storage_Modules_Status_File"
-> content of that file : the storage modules that are loaded, and "enabl=
ed" if they are
enabled, or "disabled".
-> the modification time is updated every time perfparsed finish the main=
 loop : you can
watch the date of that file to see if perfparsed is blocked :)

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/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-devel] perfparse-0.104.4 broken... some news

[Yves <yme...@pe...>]

Hi developers, hi all

In my previous mail about perfparse-0.104.4ym1, I forgot to say that if y=
ou install that
version, you should subscribe to perfparse-devel mailing-list. Next mails=
 about
perfparse-0.104.4ymX versions will be only on perfparse-devel.

After 2 days running perfparse-0.104.4ym1, I found another bug : periodic=
 cleanup enters
an infinite loop if you already have compressed files in the dirs to clea=
n up.
1st day : compression of log files -> creation of .gz files
2nd day : infinite loop due to those .gz files.

This is why I wanted to wait at least 3 days before the release of 0.104.=
5.

I fixed that bug and you can find 0.104.4ym2 on
http://pagesperso.laposte.net/ymettier/perfparse-devel/perfparse-0.104.4/=
.
I think (and I hope) that 0.104.4ym2 is now stable but we need time to be=
 sure.
So we will wait at least 3 days again before the release of 0.104.5.
You won't have it for Christmas, sorry :)

Following mails about 0.104.4ymX (and any development versions) on perfpa=
rse-devel
mailing-list.

Merry Christmas to everybody,
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/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-devel] Re: [Perfparse-users] perfparse.cgi

[Massimiliano M. <mmi...@ab...>]

Hi Ben,
I followed your steps.

> You have a very interesting problem.  One which I have never seen 
> before.  Some call from you program is formatting 0.16 as 0,16.
> 
> Can you tell me what system you are running.  Also what compiler you are 
> using.
My system is a Fedora Core 2:
"Linux 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 i686 i386 GNU/Linux"

I use gcc and my current version is:
"Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info --enable-shared --enable-threads=posix 
--disable-checking --disable-libunwind-exceptions --with-system-zlib 
--enable-__cxa_atexit --host=i386-redhat-linuxThread model: posix
gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)"

> 
> Can you try these for me:
> 
> 1. In libpp_mysql/dbms.c can you uncomment the line:
> 
> #define SHOW_SQL
> 
> 2. Can you then make all you code again and try:
> 
> perfparse-db-tool --update
> 
The output is:
"SQL:  "SET AUTOCOMMIT=0"
Rows: 0
SQL:  "START TRANSACTION"
Rows: 0
SQL:  "SELECT rvalue,ctime from perfdata_registry WHERE host = 'dummy' 
AND rkey = 'pp/database/version'"
Rows: 1
Warning, this stage may take some time:
SQL:  "EXPLAIN perfdata_service_raw"
Rows: 6
SQL:  "EXPLAIN perfdata_graphs"
Rows: 6
Auto-convert database up to version 0.16...
SQL:  "SHOW TABLES"
Rows: 13
SQL:  "SELECT count(*) from perfdata_registry WHERE host = 'dummy' AND 
rkey = 'pp/database/version'"
Rows: 1
SQL:  "UPDATE perfdata_registry SET rvalue = '0,16', ctime = 
FROM_UNIXTIME(1103623029) WHERE host = 'dummy' AND rkey = 
'pp/database/version'"
SQL:  "COMMIT"
Rows: 0
SQL:  "SET AUTOCOMMIT=1"
Rows: 0
Conversions complete."

> 3. Do you see this line:  Can you return what you see?
> 
> SQL:  "UPDATE perfdata_registry SET rvalue = '0.16', ctime = 
> FROM_UNIXTIME(1103561358) WHERE host = 'dummy' AND rkey = 
> 'pp/database/version'"
> 
> 4. Please remove the SHOW_SQL and recompile.
> 
> 5. Can you launch MySQL and try:
> 
> mysql> create table test ( value double ) type=innodb;
> mysql> insert test values (0.15);
> mysql> select * from test;
> 
> Do you get 0.15 or 0,15?
I get 0.15
> 
> If you could try these, this would be extremely useful to us!
> 
> Kind regards,
> Ben.

Regards,
Massimiliano

Re: [Perfparse-devel] Re: [Perfparse-users] perfparse.cgi

[Yves <yme...@pe...>]

I have some idea, but no solution...
0,16 instead of 0.16 -> isn't that a problem with the locale ?
Massimiliano, could you test with an English locale ? Just set LANG=3DC i=
nstead of what
you may have LANG=3Dit. Then run Perfparse and tell us how it works :)
If this is it, our DB expert Ben will have some fun to find out how to do=
 that
transparently :)

Yves

> Massimiliano,
>
> You have a very interesting problem.  One which I have never seen
> before.  Some call from you program is formatting 0.16 as 0,16.
>
> Can you tell me what system you are running.  Also what compiler you ar=
e
> using.
>
> Can you try these for me:
>
> 1. In libpp_mysql/dbms.c can you uncomment the line:
>
> #define SHOW_SQL
>
> 2. Can you then make all you code again and try:
>
> perfparse-db-tool --update
>
> 3. Do you see this line:  Can you return what you see?
>
> SQL:  "UPDATE perfdata_registry SET rvalue =3D '0.16', ctime =3D
> FROM_UNIXTIME(1103561358) WHERE host =3D 'dummy' AND rkey =3D
> 'pp/database/version'"
>
> 4. Please remove the SHOW_SQL and recompile.
>
> 5. Can you launch MySQL and try:
>
> mysql> create table test ( value double ) type=3Dinnodb;
> mysql> insert test values (0.15);
> mysql> select * from test;
>
> Do you get 0.15 or 0,15?
>
> If you could try these, this would be extremely useful to us!
>
> Kind regards,
> Ben.
>
>
>
> Massimiliano Minniti wrote:
>
>> Hi All,
>>
>>> This is an interesting one, and I don't know how it happened.
>>>
>>> You version in your database is '0,15'.  It should be '0.15'.
>>> Internally this is converted to a double:
>>>
>>> double version =3D atof(version)
>>>
>>> So '0.15' -> 0.15  but '0,15' -> 0.00
>>>
>>> Can please enter:
>>>
>>> mysql> UPDATE perfdata_registry SET rvalue =3D '0.15' WHERE rkey =3D
>>> 'pp/database/version';
>>>
>>> Would you have any idea how this got like this to begin with?  Any
>>> information you have would be very useful.
>>>
>>> The code which sets this is:
>>>
>>> void setVersion(double version)
>>> {
>>>     char s[10];
>>>     sprintf(s, "%.2lf", version);
>>>
>>>
>>> Can you write a test program on your local UNIX box and let me know
>>> what this does on your system?
>>>
>>> int main() { double d =3D 0.15; printf("%.2lf", d); return 1 }
>>>
>> I have tested this source on my system and the output correctly is 0.1=
5.
>> I updated my perfparse installation to version 0.104.4.
>> Because my old database schema is 0.15 my browse visualized the curren=
t
>> error message:
>>
>> "Current Version: 0.00, Required Version: 0.16.
>>   Consider upgrading with:
>>   perfparse-db-tool --update"
>>
>> Then I run perfparse-db-tool --update that after it visualized the
>> following correct message:
>> "Warning, this stage may take some time:
>> Auto-convert database up to version 0.16...
>> Conversions complete."
>>
>> But on my db the old correct values 0.15 now it is a wrong value 0,16
>> and I fix this problem editing the correct value 0.16 on the db record=
.
>> IMHO the upgrading throught perfpars-db-tool have some some error.
>>
>> I hope that my description is clearly.
>>
>> Excuse me for my poor english! ;)
>>
>>> I note this is using the 'lf' GNU extension.  Which GNU takes to mean
>>> 'long float'.  Could your system take this to mean 'local float'?  If
>>> you change this to "%.2f" does this fix the problem?
>>>
>>> Regards,
>>>
>>> Ben
>>
>>
>> Regards,
>> Massimiliano Minniti
>>
>
>
> --
> Ben Clewett  bcl...@pe...
> PerfParse    http://www.perfparse.org
> PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users=
.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Perfparse-devel mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfparse-devel
>
>


--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-devel] Re: [Perfparse-users] perfparse.cgi

[Ben C. <bcl...@pe...>]

Massimiliano,

You have a very interesting problem.  One which I have never seen 
before.  Some call from you program is formatting 0.16 as 0,16.

Can you tell me what system you are running.  Also what compiler you are 
using.

Can you try these for me:

1. In libpp_mysql/dbms.c can you uncomment the line:

#define SHOW_SQL

2. Can you then make all you code again and try:

perfparse-db-tool --update

3. Do you see this line:  Can you return what you see?

SQL:  "UPDATE perfdata_registry SET rvalue = '0.16', ctime = 
FROM_UNIXTIME(1103561358) WHERE host = 'dummy' AND rkey = 
'pp/database/version'"

4. Please remove the SHOW_SQL and recompile.

5. Can you launch MySQL and try:

mysql> create table test ( value double ) type=innodb;
mysql> insert test values (0.15);
mysql> select * from test;

Do you get 0.15 or 0,15?

If you could try these, this would be extremely useful to us!

Kind regards,
Ben.



Massimiliano Minniti wrote:

> Hi All,
> 
>> This is an interesting one, and I don't know how it happened.
>>
>> You version in your database is '0,15'.  It should be '0.15'. 
>> Internally this is converted to a double:
>>
>> double version = atof(version)
>>
>> So '0.15' -> 0.15  but '0,15' -> 0.00
>>
>> Can please enter:
>>
>> mysql> UPDATE perfdata_registry SET rvalue = '0.15' WHERE rkey = 
>> 'pp/database/version';
>>
>> Would you have any idea how this got like this to begin with?  Any 
>> information you have would be very useful.
>>
>> The code which sets this is:
>>
>> void setVersion(double version)
>> {
>>     char s[10];
>>     sprintf(s, "%.2lf", version);
>>
>>
>> Can you write a test program on your local UNIX box and let me know 
>> what this does on your system?
>>
>> int main() { double d = 0.15; printf("%.2lf", d); return 1 }
>>
> I have tested this source on my system and the output correctly is 0.15.
> I updated my perfparse installation to version 0.104.4.
> Because my old database schema is 0.15 my browse visualized the current 
> error message:
> 
> "Current Version: 0.00, Required Version: 0.16.
>   Consider upgrading with:
>   perfparse-db-tool --update"
> 
> Then I run perfparse-db-tool --update that after it visualized the 
> following correct message:
> "Warning, this stage may take some time:
> Auto-convert database up to version 0.16...
> Conversions complete."
> 
> But on my db the old correct values 0.15 now it is a wrong value 0,16 
> and I fix this problem editing the correct value 0.16 on the db record.
> IMHO the upgrading throught perfpars-db-tool have some some error.
> 
> I hope that my description is clearly.
> 
> Excuse me for my poor english! ;)
> 
>> I note this is using the 'lf' GNU extension.  Which GNU takes to mean 
>> 'long float'.  Could your system take this to mean 'local float'?  If 
>> you change this to "%.2f" does this fix the problem?
>>
>> Regards,
>>
>> Ben
> 
> 
> Regards,
> Massimiliano Minniti
> 


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php

[Perfparse-devel] Fix for perfparse-0.104.4 available

[Yves <yme...@pe...>]

Hi,

As you probably know, a broken release of perfparse, with version number =
0.104.4, was
released this morning. That version contains some unfinished work on log =
rotation,
compression and removal of log files (logs, drop files and output files f=
rom
"file_output" storage module). Ben misunderstood me about that work and p=
robably thought
that it would not impact users, so he released 0.104.4.

I finished that work today, and made some tests and it looks correct now.
You can download 0.104.4ym1 from
http://pagesperso.laposte.net/ymettier/perfparse-devel/perfparse-0.104.4/

To test that new release in good conditions, I need 3 days to see if the =
files I watch
are compressed/uncompressed/removed as expected. So perfparse-0.104.5 wil=
l not be
released before Thurday 23th, and only if my tests are successful.

Ben also told me about minor changes, so you may find some other 0.104.4y=
mX before
Thursday on my perfparse unofficial web site :)

I apologize here for the trouble caused by releasing 0.104.4 too early. A=
nd I can now
say that you should not loose data with 0.104.4. However, because it does=
 not work as
expected, consider that version as unsupported.

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/                 -
- Perfparse   - http://perfparse.sf.net/                           -

[Perfparse-devel] Version 0.104.4, please read!

[Ben C. <bcl...@pe...>]

Further note on version 0.104.4

Please Read!

If you use the perfparsed part of PerfParse, used for instance for the 
Pipe method:  Please DO NOT use 0.104.4.  Please wait for next version.

Regards,

Ben.

-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php

[Perfparse-devel] New version, 0.104.4, please read.

[Ben C. <bcl...@pe...>]

Monday morning is not the time to make release announcements, some error 
is inevitable!

The correct details of release available here:

http://wiki.perfparse.org/tiki-view_forum_thread.php?comments_parentId=10&forumId=2

Note:-

If you are using the storage_file_output used to store Nagios data into 
the file database.  (NOT MySQL)  Please do not use this version. 
Another will be releases soon.

Regards, Ben.



-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php

[Perfparse-devel] New version, 0.104.4

[Ben C. <bcl...@pe...>]

There is a new version, 0.104.4.

Details available on announce forum:

http://wiki.perfparse.org/tiki-view_forum_thread.php?comments_parentId=5&topics_offset=1&forumId=2

Ben.

-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php