Menu
▾
▴
perfparse-users — Problems using PerfParse
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(12) |
Jun
(56) |
Jul
(68) |
Aug
(141) |
Sep
(82) |
Oct
(76) |
Nov
(115) |
Dec
(74) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(65) |
Feb
(113) |
Mar
(82) |
Apr
(37) |
May
(44) |
Jun
(22) |
Jul
(12) |
Aug
(3) |
Sep
(17) |
Oct
(11) |
Nov
(23) |
Dec
(1) |
| 2006 |
Jan
(1) |
Feb
(9) |
Mar
(6) |
Apr
(12) |
May
(10) |
Jun
(23) |
Jul
(1) |
Aug
(4) |
Sep
(3) |
Oct
(4) |
Nov
(6) |
Dec
(15) |
| 2007 |
Jan
(17) |
Feb
(14) |
Mar
(20) |
Apr
(7) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(5) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2008 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(6) |
Jun
(5) |
Jul
(13) |
Aug
(2) |
Sep
(16) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael T. H. <mi...@ha...> - 2004-11-01 20:32:18
|
Update to this. I've installed mysql 4.0.22, and the problem is still th= e same (compiles fine with 101.1 but not 102.2) > I'm attempting to compile perfparse 0.102.2. I'm compiling everything > the same way I was > compiling 0.101.1, > > with options : > > --------------- > #!/bin/sh > > make -j clean > > ./configure \ > --prefix=3D/home/nagios \ > --with-imagedir=3D/home/nagios/html/images \ > --with-cgidir=3D/home/nagios/cgi-bin \ > --with-http_image_path=3D/images > make -j > make -j install-strip > --------------- > > > The compilation is failing with : > > make[2]: Entering directory > `/home/nagios_software/build/perfparse-0.102.2/perfparse' > /bin/sh ../libtool --mode=3Dlink gcc -g -O2 -Wall -o > perfparse-log2socket perfparse_log2socket-perfparse-log2any.o > perfparse_log2socket-perfparse-common.o > perfparse_log2socket-log_reader.o perfparse_log2socket-log_parser.o > perfparse_log2socket-storage.o > perfparse_log2socket-storage_socket_output.o -L/usr/lib/mysql > -lmysqlclient -lz -lcrypt -lnsl -lm -lc -lnss_files -lnss_dns -lresolv > -lc -lnss_files -lnss_dns -lresolv -lglib-2.0 -L../libpp_mysql > -lpp_mysql -L../libpp_common -lpp_common > /bin/sh ../libtool --mode=3Dlink gcc -g -O2 -Wall -o > perfparse-log2file perfparse_log2file-perfparse-log2any.o > perfparse_log2file-perfparse-common.o perfparse_log2file-log_reader.o > perfparse_log2file-log_parser.o perfparse_log2file-storage.o > perfparse_log2file-storage_file_output.o -L/usr/lib/mysql -lmysqlclient > -lz -lcrypt -lnsl -lm -lc -lnss_files -lnss_dns -lresolv -lc -lnss_file= s > -lnss_dns -lresolv -lglib-2.0 -L../libpp_mysql -lpp_mysql > -L../libpp_common -lpp_common > gcc -g -O2 -Wall -o .libs/perfparse-log2file > perfparse_log2file-perfparse-log2any.o > perfparse_log2file-perfparse-common.o perfparse_log2file-log_reader.o > perfparse_log2file-log_parser.o perfparse_log2file-storage.o > perfparse_log2file-storage_file_output.o -L/usr/lib/mysql > /usr/lib/mysql/libmysqlclient.a -lz -lcrypt -lnsl -lm -lc -lnss_files > -lnss_dns -lresolv -lglib-2.0 > -L/home/nagios_software/build/perfparse-0.102.2/libpp_mysql > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so > -L/home/nagios_software/build/perfparse-0.102.2/libpp_common > /home/nagios_software/build/perfparse-0.102.2/libpp_common/.libs/libpp_= common.so > -Wl,--rpath -Wl,/home/nagios/lib > gcc -g -O2 -Wall -o .libs/perfparse-log2socket > perfparse_log2socket-perfparse-log2any.o > perfparse_log2socket-perfparse-common.o > perfparse_log2socket-log_reader.o perfparse_log2socket-log_parser.o > perfparse_log2socket-storage.o > perfparse_log2socket-storage_socket_output.o -L/usr/lib/mysql > /usr/lib/mysql/libmysqlclient.a -lz -lcrypt -lnsl -lm -lc -lnss_files > -lnss_dns -lresolv -lglib-2.0 > -L/home/nagios_software/build/perfparse-0.102.2/libpp_mysql > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so > -L/home/nagios_software/build/perfparse-0.102.2/libpp_common > /home/nagios_software/build/perfparse-0.102.2/libpp_common/.libs/libpp_= common.so > -Wl,--rpath -Wl,/home/nagios/lib > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_store_result' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_fetch_row' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_affected_rows' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_init' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_options' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_close' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_num_rows' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_error' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_free_result' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_use_result' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_query' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_real_connect' > collect2: ld returned 1 exit status > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_store_result' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_fetch_row' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_affected_rows' > /home/nagios_software/buildmake[2]: /perfparse*** [perfparse-log2file] > Error 1 > -0.102.2/libpp_mysql/.libs/make[2]: libpp_mysql.so:*** Waiting for > unfinished jobs.... > undefined reference to `mysql_init' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_options' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_close' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_num_rows' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_error' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_free_result' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_use_result' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_query' > /home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_m= ysql.so: > undefined reference to `mysql_real_connect' > collect2: ld returned 1 exit status > make[2]: *** [perfparse-log2socket] Error 1 > make[2]: Leaving directory > `/home/nagios_software/build/perfparse-0.102.2/perfparse' > make[1]: *** [install-recursive] Error 1 > make[1]: Leaving directory `/home/nagios_software/build/perfparse-0.102= .2' > make: *** [install-strip] Error 2 > > ------- > > -- > ------------------- > BitPusher, LLC > http://www.bitpusher.com/ > 1.888.9PUSHER > (415) 724.7998 - Mobile > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=3D5588&alloc_id=3D12065&op=3Dclick > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users > ------------------- BitPusher, LLC http://www.bitpusher.com/ 1.888.9PUSHER (415) 724.7998 - Mobile |
|
From: Michael T. H. <mi...@ha...> - 2004-11-01 05:44:02
|
I'm attempting to compile perfparse 0.102.2. I'm compiling everything
the same way I was
compiling 0.101.1,
with options :
---------------
#!/bin/sh
make -j clean
./configure \
--prefix=/home/nagios \
--with-imagedir=/home/nagios/html/images \
--with-cgidir=/home/nagios/cgi-bin \
--with-http_image_path=/images
make -j
make -j install-strip
---------------
The compilation is failing with :
make[2]: Entering directory
`/home/nagios_software/build/perfparse-0.102.2/perfparse'
/bin/sh ../libtool --mode=link gcc -g -O2 -Wall -o
perfparse-log2socket perfparse_log2socket-perfparse-log2any.o
perfparse_log2socket-perfparse-common.o
perfparse_log2socket-log_reader.o perfparse_log2socket-log_parser.o
perfparse_log2socket-storage.o
perfparse_log2socket-storage_socket_output.o -L/usr/lib/mysql
-lmysqlclient -lz -lcrypt -lnsl -lm -lc -lnss_files -lnss_dns -lresolv
-lc -lnss_files -lnss_dns -lresolv -lglib-2.0 -L../libpp_mysql
-lpp_mysql -L../libpp_common -lpp_common
/bin/sh ../libtool --mode=link gcc -g -O2 -Wall -o
perfparse-log2file perfparse_log2file-perfparse-log2any.o
perfparse_log2file-perfparse-common.o perfparse_log2file-log_reader.o
perfparse_log2file-log_parser.o perfparse_log2file-storage.o
perfparse_log2file-storage_file_output.o -L/usr/lib/mysql -lmysqlclient
-lz -lcrypt -lnsl -lm -lc -lnss_files -lnss_dns -lresolv -lc -lnss_files
-lnss_dns -lresolv -lglib-2.0 -L../libpp_mysql -lpp_mysql
-L../libpp_common -lpp_common
gcc -g -O2 -Wall -o .libs/perfparse-log2file
perfparse_log2file-perfparse-log2any.o
perfparse_log2file-perfparse-common.o perfparse_log2file-log_reader.o
perfparse_log2file-log_parser.o perfparse_log2file-storage.o
perfparse_log2file-storage_file_output.o -L/usr/lib/mysql
/usr/lib/mysql/libmysqlclient.a -lz -lcrypt -lnsl -lm -lc -lnss_files
-lnss_dns -lresolv -lglib-2.0
-L/home/nagios_software/build/perfparse-0.102.2/libpp_mysql
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so
-L/home/nagios_software/build/perfparse-0.102.2/libpp_common
/home/nagios_software/build/perfparse-0.102.2/libpp_common/.libs/libpp_common.so
-Wl,--rpath -Wl,/home/nagios/lib
gcc -g -O2 -Wall -o .libs/perfparse-log2socket
perfparse_log2socket-perfparse-log2any.o
perfparse_log2socket-perfparse-common.o
perfparse_log2socket-log_reader.o perfparse_log2socket-log_parser.o
perfparse_log2socket-storage.o
perfparse_log2socket-storage_socket_output.o -L/usr/lib/mysql
/usr/lib/mysql/libmysqlclient.a -lz -lcrypt -lnsl -lm -lc -lnss_files
-lnss_dns -lresolv -lglib-2.0
-L/home/nagios_software/build/perfparse-0.102.2/libpp_mysql
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so
-L/home/nagios_software/build/perfparse-0.102.2/libpp_common
/home/nagios_software/build/perfparse-0.102.2/libpp_common/.libs/libpp_common.so
-Wl,--rpath -Wl,/home/nagios/lib
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_store_result'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_fetch_row'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_affected_rows'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_init'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_options'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_close'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_num_rows'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_error'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_free_result'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_use_result'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_query'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_real_connect'
collect2: ld returned 1 exit status
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_store_result'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_fetch_row'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_affected_rows'
/home/nagios_software/buildmake[2]: /perfparse*** [perfparse-log2file]
Error 1
-0.102.2/libpp_mysql/.libs/make[2]: libpp_mysql.so:*** Waiting for
unfinished jobs....
undefined reference to `mysql_init'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_options'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_close'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_num_rows'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_error'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_free_result'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_use_result'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_query'
/home/nagios_software/build/perfparse-0.102.2/libpp_mysql/.libs/libpp_mysql.so:
undefined reference to `mysql_real_connect'
collect2: ld returned 1 exit status
make[2]: *** [perfparse-log2socket] Error 1
make[2]: Leaving directory
`/home/nagios_software/build/perfparse-0.102.2/perfparse'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/nagios_software/build/perfparse-0.102.2'
make: *** [install-strip] Error 2
-------
--
-------------------
BitPusher, LLC
http://www.bitpusher.com/
1.888.9PUSHER
(415) 724.7998 - Mobile
|
|
From: Ben C. <Be...@cl...> - 2004-10-28 11:11:27
|
New version 0.102.2. This only contains a compilation fix for Solaris. Please update from 0.102.1 only if you have Solaris. Same notes apply for other users upgrading to 0.102.x version: 0.101.1 was a major rewrite of the code of the parser and few bugs were reported. 0.102.1 takes benefit of the new code to provide a lot of new features, including : - perfparse-log2file that outputs the perfdata to a file (rotation possible) - perfparse-log2socket to connect to a server and send the perfdata through the network - perfparsed, a daemon that can read from a pipe (native in nagios-2.0) or a network socket. - perfparse-log2db runs in the same way as in 0.101.1. perfparse-log2* binaries each enable one storage module. perfparsed can enable any. Here are the modules : - mysql : the one that you already use in perfparse-0.101.1. Some bug fixed. - output_file [new] : writes the data to a file. File rotation is possible with one file per day. - output_socket [new] : writes the data into a socket. The server can be perfparsed with the socket server enabled. - print : this is an example for developers, but is disabled by default. Documentation is in docbook format in doc/ and a html file was generated there too. Check the documentation for the new possibilities that perfparsed gives you ! Last thing : the undocumented --show_config in perfparse-log2* and perfparsed make them print the configuration option in a format compatible with the configuration file. Please check your default options :) Ben / Yves. |
|
From: Ben C. <Be...@cl...> - 2004-10-28 10:57:52
|
Dear PerfParse, I have set up a new mailing list: per...@li... This will be live 6 - 24 hours from this posting. This will be used to announce new versions and vital information, such as bug-fixes. For those members publishing development versions, alternate PHP front ends, other tools, conversions to other databases, please post here. The existing news groups will be kept as-is: users All general discussion and support. devel Technical discussion about the development of PP. Regards, Ben. |
|
From: Yves M. <yme...@li...> - 2004-10-27 12:58:55
|
> New version 0.102.1 released. Some last minute bug fixed was tested only on Linux. It does not compile = on Solaris (isinf does not exist). I'm working on that issue and Ben will probably release some 0.102.2 vers= ion today. If you can compile 0.102.1, there is no reason to wait for 0.102.2. Here are some more details about 0.102 branch : 0.101.1 was a major rewrite of the code of the parser and few bugs were r= eported. 0.102.1 takes benefit of the new code to provide a lot of new features, i= ncluding : - perfparse-log2file that outputs the perfdata to a file (rotation possible= ) - perfparse-log2socket to connect to a server and send the perfdata through= the network - perfparsed, a daemon that can read from a pipe (native in nagios-2.0) or = a network socket. - perfparse-log2db runs in the same way as in 0.101.1. perfparse-log2* binaries each enable one storage module. perfparsed can enable any. Here are the modules : - mysql : the one that you already use in perfparse-0.101.1. Some bug fix= ed. - output_file [new] : writes the data to a file. File rotation is possible = with one file per day. - output_socket [new] : writes the data into a socket. The server can be = perfparsed with the socket server enabled. - print : this is an example for developers, but is disabled by default. Documentation is in docbook format in doc/ and a html file was generated = there too. Check the documentation for the new possibilities that perfparsed gives y= ou ! Last thing : the undocumented --show_config in perfparse-log2* and perfpa= rsed make them print the configuration option in a format compatible with the configurat= ion file. Please check your default options :) 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/ - |
|
From: Ben C. <Be...@cl...> - 2004-10-27 12:27:01
|
New version 0.102.1 released. Release of new tools, including the PerfParse Daemon, perfparsed. See documentation for more details. With thanks to Yves for excellent programming. This also contains bug-fixes to previous version, including warn and critical storage issue. Please report any issues. All feedback welcome. Regards, Ben. |
|
From: Ben C. <Be...@cl...> - 2004-10-26 16:10:24
|
Sand Philipp wrote: > Sounds good, how will the tow tables look like? As well as some incremental changes, the main change is based around two observations: 1. With the current table most data is duplicated. Warn, Crit, Min, Max. are the same for thousands of rows at a time. When the Warn and Crit become a range, they will increase size from 4 to 10 bytes. Therefore 28 bytes of duplicate information in every row. 2. Secondly, the key structure contains the metric. Defined by VARCHAR(75), VARCHAR(75), VARCHAR(75). So there is also a maximum of 225 more bytes of duplicate data in every row. These two problems are countered using two changes. First a new table for all the peripheral duplicate information is defined. Warn, Max etc. There will only be a new record when there is a change to these values. Linked back to the main table by an integer foreign key. Reducing the field size by 24 bytes. Quite a lot if you have 10e+8 rows. If you like Entity Relationship Diagrams: +---------------+ +---------------+ | bin values |>----| bin extras | +---------------+ +---------------+ The second change will be to assign every Metric a unique ID. A MID. These will auto-increment from 1. Each value will be indexed by this MID and not the massive index above. Therefore saving another load of space. The schema is not yet defined. (Discussion should really be in the devel news group, but just for interested...) But the value table will be something like: TABLE perfdata_bin ( mid UNSIGNED INT NOT NULL, ctime DATETIME NOT NULL, PRIMARY KEY (mid, ctime), value DOUBLE, extra_data UNSIGNED INT NOT NULL ) type=innodb; You can see that the 'value' is now DOUBLE and not FLOAT. This allows date/time data to be safely stored, as well as other data to which an extremely accurate comparison is needed. NULL as the value can also be used. This will imply a missing data sample and reflected by a gap in the graph. Although not yet supported by the plugin performance output format. You can also see that duplicate data is now, thankfully, impossible! The extra table being: TABLE perfdata_bin_extra ( mid UNSIGNED INT NOT NULL, extra_data UNSIGNED INT AUTO_INCREMENT NOR NULL, PRIMARY KEY (mid, extra_data), ... When I get a moment, a more complete specification will be posted to the perfparse-devel news group. I hope this gives you some idea, Regards, Ben. |
|
From: Yves M. <yme...@li...> - 2004-10-26 16:05:49
|
> Also, one thing that I did using the latest version of mysql was to set= up > innodb to create separate files for each table. This makes it much eas= ier > to reclaim space on a per table basis, and it keeps me from having a ma= ssive > file for the innodb database... now I just have big files for the > perfparse_service_bin table ;) James, would you mind writing a short document about how you did that, for inclu= sion in the install guide ? xml docbook is preferred if you know how (OpenOffice.org can output that)= , but html, and plain text are accepted too :) 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/ - |
|
From: Ricardo D. M. <ric...@gm...> - 2004-10-26 15:49:03
|
> Does that mean that you have no problem to store the perf data into the d= atabase ? Yes. > My understanding is now : > you run perfparse (perfparse-log2db for 0.101.1) > perfparse connects to the database successfully > perfparse successfully makes all its query including those to insert data > something happen before or after perfparse exit > mysql writes the message in the log This seems right. Regards --=20 Ricardo David Martins ___________________________________________________________________________= __________________________ AVISO Esta mensagem (incluindo quaisquer anexos) pode conter informa=E7=E3o confidencial para uso exclusivo do destinat=E1rio. Se n=E3o for o destinat=E1rio pretendido, n=E3o dever=E1 usar, distribuir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado. DISCLAIMER This e-mail (including any attachments) may contain confidential information for exclusive use of its recipient. If you are not the intended recipient you must not use, distribute or copy this e-mail. If you have received this e-mail in error please notify the sender and delete it immediately. Thank You. ___________________________________________________________________________= __________________________ |
|
From: James O. <jo...@re...> - 2004-10-26 15:27:13
|
As far as recovering database space from using option one, I've = successfully used the optimize table function in mysqlcheck to compact the tables = and reclaim space. It runs relatively quickly, but you do need to have the database quiet (which I imaging you would while upgrading perfparse = anyway ;) Also, one thing that I did using the latest version of mysql was to set = up innodb to create separate files for each table. This makes it much = easier to reclaim space on a per table basis, and it keeps me from having a = massive file for the innodb database... now I just have big files for the perfparse_service_bin table ;) James -----Original Message----- From: Sand Philipp [mailto:Phi...@sy...]=20 Sent: Tuesday, October 26, 2004 4:07 AM To: Ben Clewett Cc: per...@li... Subject: RE: [Perfparse-users] Help Needed > When the current versions are stable, we will be looking to=20 > convert the binary table in the PP database. This will=20 > probably take our product up to version 1.0. I need some=20 > advise from users about the best method. >=20 > The advantages of the change are: > - A range for the Warn and Crit values, rather than just a=20 > single value. > - Smaller storage space needed for same data. > - Faster access to data, bigger graphs possible. > - A scalable solution where new information can be added easily. Sounds good, how will the tow tables look like? > Option 1. > --------- >=20 > Copy the old table to new tables and delete old table. >=20 > Pro: > Fast. > Easy to program & test =3D> low in bugs. > Con: > Will double size of MySQL database during conversion. > This space is very hard to recover. I think I would prefere that one. We're storing the performance Data = for long time (estimated 3years deletion policy) So over long terms our db will grow anyway :) Userers who store Data = for shortterms could easyly create a new Database for perfparse "1.0" and delete the old Database when it's not needed anymore... > Option 2. > --------- >=20 > Copy all data to an external text files. Delete old table. =20 > Copy back to new tables. Delete text files. >=20 > Pro: > Fast. > No increase in MySQL table space. > Con: > Harder to program & test =3D> bugs possible. > Text file size is far larger than table, which is binary. > Need database size again in temporary storage for text=20 > dump of table. After messing around with mysqldum(b)p this week, i think it's to risky to do it that way...but if you can make sure, that no data will be lost during that progress, it would be nice, too. But I think you should better use this time to put in some other features (like multiple metrics in one graph :) ) > Option 3. > --------- >=20 > Copy over a line at a time and delete line from old table. >=20 > Pro: > No extra space needed. No increase in MySQL table space. > Easy to program & test =3D> low in bugs. > Con: > Deleting line by line is slow. Conversion may take several weeks. I think thats no alternative...as you said, that would last a few weeks for a few million lines... Before doing that, I personally would start with a new database ... > Finally, a plee to anybody who knows some MySQL and a little=20 > 'c'. Can you spare some time to help develop and/or test a=20 > conversion program.=20 > You time will be welcome, and you will be credited as a developer. I now a little sql and can read a little c ... But we're just in a ADS Migration Process here, so I don't have very much time...but when I = find some time here, i'll try to help...But don't schedule me :) ************************************************ sycor plastics - die neue Branchenl=F6sung f=FCr die = Kunststoffindustrie www.sycor-plastics.de ************************************************ Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Informationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe = Empf=E4nger sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und benachrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine = Vertr=E4ge oder vertragliche Verpflichtungen ein oder =FCbermittelt = rechtsverbindliche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart = wurde. This e-mail is confidential and may contain personal and/or privileged information. If you are not the intended recipient please delete this = e-mail and all attachments immediately and inform us. The company sycor does = not agree with contracts or contract obligations sent by e-mail, neither do = we transmit legally binding offers by e-mail, unless this is not expressly agreed upon between the parties and documented in written form. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on = ITManagersJournal Use IT products in your business? Tell us what you think of them. Give = us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out = more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Perfparse-users mailing list Per...@li... https://lists.sourceforge.net/lists/listinfo/perfparse-users |
|
From: Yves M. <yme...@li...> - 2004-10-26 13:42:51
|
> Basically i have all functionality going but the error just keeps > appearing. Maybe when i update it Will disappear. Does that mean that you have no problem to store the perf data into the d= atabase ? I thought you had the problem *before* the connection to the database. My understanding is now : you run perfparse (perfparse-log2db for 0.101.1) perfparse connects to the database successfully perfparse successfully makes all its query including those to insert data something happen before or after perfparse exit mysql writes the message in the log my understanding was : you run perfparse connection to the database fails and perfparse does nothing. Well, in that case, we should move to perfparse-devel mailing-list. You first mail was definitely not clear. Thanks for insisting :) Ben, can you reproduce that bug ? I have such messages, but I don't know yet if they come from an old versi= on or from >=3D 0.101.1. I have to test. 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/ - |
|
From: Ricardo D. M. <ric...@gm...> - 2004-10-26 13:14:20
|
> I have another idea. Check your mysql config file. Do you have 3306 as th= e tcp port for > mysqld ? Same question for the client even if I don't know if this is imp= ortant. > Is skip-networking defined ? If yes, comment it. I'm sure I have all that well configured, or else i couldn't make crossed replication in mysql. Besides, i can make queries to perfparse databases using the IPv4 socket. I can see the results on the CGI, although the error is persistent. > For information for Ricardo and those who would try to help, nagios conne= cts to mysql > thanks to a local socket (some file in /tmp/...). Perfparse connects to m= ysql thanks to > the network (socket IPv4). I don't know for the client mysql, but it prov= ides a -P > option for the port, and -h for the host name. Maybe this can help ? Basically i have all functionality going but the error just keeps appearing. Maybe when i update it Will disappear. Regards -- Ricardo David Martins ___________________________________________________________________________= __________________________ AVISO Esta mensagem (incluindo quaisquer anexos) pode conter informa=E7=E3o confidencial para uso exclusivo do destinat=E1rio. Se n=E3o for o destinat=E1rio pretendido, n=E3o dever=E1 usar, distribuir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado. DISCLAIMER This e-mail (including any attachments) may contain confidential information for exclusive use of its recipient. If you are not the intended recipient you must not use, distribute or copy this e-mail. If you have received this e-mail in error please notify the sender and delete it immediately. Thank You. ___________________________________________________________________________= __________________________ |
|
From: Sand P. <Phi...@sy...> - 2004-10-26 11:07:19
|
> When the current versions are stable, we will be looking to=20 > convert the binary table in the PP database. This will=20 > probably take our product up to version 1.0. I need some=20 > advise from users about the best method. >=20 > The advantages of the change are: > - A range for the Warn and Crit values, rather than just a=20 > single value. > - Smaller storage space needed for same data. > - Faster access to data, bigger graphs possible. > - A scalable solution where new information can be added easily. Sounds good, how will the tow tables look like? > Option 1. > --------- >=20 > Copy the old table to new tables and delete old table. >=20 > Pro: > Fast. > Easy to program & test =3D> low in bugs. > Con: > Will double size of MySQL database during conversion. > This space is very hard to recover. I think I would prefere that one. We're storing the performance Data for long time (estimated 3years deletion policy) So over long terms our db will grow anyway :) Userers who store Data for shortterms could easyly create a new Database for perfparse "1.0" and delete the old Database when it's not needed anymore... > Option 2. > --------- >=20 > Copy all data to an external text files. Delete old table. =20 > Copy back to new tables. Delete text files. >=20 > Pro: > Fast. > No increase in MySQL table space. > Con: > Harder to program & test =3D> bugs possible. > Text file size is far larger than table, which is binary. > Need database size again in temporary storage for text=20 > dump of table. After messing around with mysqldum(b)p this week, i think it's to risky to do it that way...but if you can make sure, that no data will be lost during that progress, it would be nice, too. But I think you should better use this time to put in some other features (like multiple metrics in one graph :) ) > Option 3. > --------- >=20 > Copy over a line at a time and delete line from old table. >=20 > Pro: > No extra space needed. No increase in MySQL table space. > Easy to program & test =3D> low in bugs. > Con: > Deleting line by line is slow. Conversion may take several weeks. I think thats no alternative...as you said, that would last a few weeks for a few million lines... Before doing that, I personally would start with a new database ... > Finally, a plee to anybody who knows some MySQL and a little=20 > 'c'. Can you spare some time to help develop and/or test a=20 > conversion program.=20 > You time will be welcome, and you will be credited as a developer. I now a little sql and can read a little c ... But we're just in a ADS Migration Process here, so I don't have very much time...but when I find some time here, i'll try to help...But don't schedule me :) ************************************************ sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie www.sycor-plastics.de ************************************************ Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info= rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge= r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben= achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4= ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind= liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht= ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu= rde. This e-mail is confidential and may contain personal and/or privileged in= formation. If you are not the intended recipient please delete this e-mai= l and all attachments immediately and inform us. The company sycor does n= ot agree with contracts or contract obligations sent by e-mail, neither d= o we transmit legally binding offers by e-mail, unless this is not expres= sly agreed upon between the parties and documented in written form. |
|
From: Ben C. <Be...@cl...> - 2004-10-26 10:02:06
|
Dear Users,
When the current versions are stable, we will be looking to convert the
binary table in the PP database. This will probably take our product up
to version 1.0. I need some advise from users about the best method.
The advantages of the change are:
- A range for the Warn and Crit values, rather than just a single value.
- Smaller storage space needed for same data.
- Faster access to data, bigger graphs possible.
- A scalable solution where new information can be added easily.
In order to complete this conversion, the main table
'perfdata_service_bin' will be copied to two new tables, and then
dropped. But this causes problems. In order to complete this
conversion there are three methods. I would like you to suggest which
one you consider the best. Then we will program and use the method you
choose. Please let us know.
Option 1.
---------
Copy the old table to new tables and delete old table.
Pro:
Fast.
Easy to program & test => low in bugs.
Con:
Will double size of MySQL database during conversion.
This space is very hard to recover.
Option 2.
---------
Copy all data to an external text files. Delete old table. Copy back
to new tables. Delete text files.
Pro:
Fast.
No increase in MySQL table space.
Con:
Harder to program & test => bugs possible.
Text file size is far larger than table, which is binary.
Need database size again in temporary storage for text dump of table.
Option 3.
---------
Copy over a line at a time and delete line from old table.
Pro:
No extra space needed. No increase in MySQL table space.
Easy to program & test => low in bugs.
Con:
Deleting line by line is slow. Conversion may take several weeks.
Finally, a plee to anybody who knows some MySQL and a little 'c'. Can
you spare some time to help develop and/or test a conversion program.
You time will be welcome, and you will be credited as a developer.
Kind regards,
Ben Clewett.
|
|
From: Yves M. <yme...@li...> - 2004-10-26 08:05:44
|
> I have no problem seing the results, but the error appears just the > same. I only found the error because i am making tests for a real > production environment. > >> Could you run >> perfparse-log2db <your options here> --show-config > > I only have the perfparse-db-tool. Ooops, perfparse-log2db is the new version of perparse. With 0.100.x, I w= as meaning perfparse --show_config. But perfparse-db-tool answers the same thing so it's OK. OK, I see nothing unusual here. I have another idea. Check your mysql config file. Do you have 3306 as th= e tcp port for mysqld ? Same question for the client even if I don't know if this is imp= ortant. Is skip-networking defined ? If yes, comment it. Well, if this is not enough, the last thing I would do is : telnet localhost 3306 If the connection is refused, stop searching on perfparse side and read t= he documentation about mysql. If the connection is accepted, for me, it's ga= me over, and just hope that somebody else can help you :) For information for Ricardo and those who would try to help, nagios conne= cts to mysql thanks to a local socket (some file in /tmp/...). Perfparse connects to m= ysql thanks to the network (socket IPv4). I don't know for the client mysql, but it prov= ides a -P option for the port, and -h for the host name. Maybe this can help ? Yves > # ./perfparse-db-tool --show_config > DB_User =3D "nagios" > DB_Name =3D "nagios" > DB_Pass =3D "******" > DB_Host =3D "127.0.0.1" > Drop_File =3D "/tmp/perfparse.drop" > Service_Log =3D "/usr/local/nagios/var/serviceperf.log" > Host_Log =3D "/usr/local/nagios/var/hostperf.log" > Dummy_Hostname =3D "dummy" > Delete_Service_Log =3D "No" > Delete_Host_Log =3D "No" > Nagios_Lock =3D "/usr/local/nagios/var/nagios.lock" > Lock_File =3D "/var/lock/perfparse.lock" > Be_Silent =3D "no" > Do_Report =3D "no" > Accept_Odd_Chars_in_Label =3D "no" > Default_user_permissions_Policy =3D "rw" > Default_user_permissions_Host_groups =3D "rw" > > Regards > > -- > Ricardo David Martins > _______________________________________________________________________= ______________________________ > > AVISO > > Esta mensagem (incluindo quaisquer anexos) pode conter informa=E7=E3o > confidencial para uso exclusivo do destinat=E1rio. Se n=E3o for o > destinat=E1rio pretendido, n=E3o dever=E1 usar, distribuir ou copiar es= te > e-mail. Se recebeu esta mensagem por engano, por favor informe o > emissor e elimine-a imediatamente. Obrigado. > > DISCLAIMER > > This e-mail (including any attachments) may contain confidential > information for exclusive use of its recipient. If you are not the > intended recipient you must not use, distribute or copy this e-mail. > If you have received this e-mail in error please notify the sender and > delete it immediately. Thank You. > > _______________________________________________________________________= ______________________________ > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJourna= l > Use IT products in your business? Tell us what you think of them. Give = us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out = more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > 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/ - - Perfparse - http://perfparse.sf.net/ - |
|
From: Ben C. <Be...@cl...> - 2004-10-26 07:50:34
|
Paulo, I hope the next version will have these bugs sorted, please check when=20 you can. I want to answer just one comment from this email: > I've found performance problems also in 0.101.1, as I feel that it is > much slower than 0.100.7 when reading the serviceperf.log file and > putting it into the database. In 0.100.7 I've got thousands of lines > per second; in 0.101.1 this number never is greater than 70 lines/sec. > And I'm running on a machine with 512 MB RAM, 2xIntel Xeon 3.06 GHz! There was a bug in versions before 0.101.1. The performance in the=20 status line was being reported in error, far too high. You may want to=20 calculate your lines/second by hand to get a correct measure of whether=20 the next version is really any faster. This bug is fixed in new=20 versions, therefore showing a correct but much lower value. However, your figure of 70 lines/seconds on a duel Xeon 3.06 is terribly=20 low. I would expect ~1000 lines/second at least. Version 0.102.1 which=20 will be out very soon. Thanks from our friend Yves, this had five=20 different methods of getting data from Nagios to PP. Perhaps one of=20 these will work better. Regards, Ben. Paulo Afonso Graner Fessel wrote: > Ben, >=20 > I've found that perfparse has now the infrastructure to use ranges of w= arning/critical data, and the problem is that the database hasn't changed= in order to use these values (as far as I can see, at least). >=20 > Part of the problem is at save_bin_data at storage_mysql.c: >=20 > g_string_append_printf(s_SQL, ", %s", > getSafeD(perf->d[PERF_VALUE_WARN_START])); > g_string_append_printf(s_SQL, ", %s", > getSafeD(perf->d[PERF_VALUE_CRIT_START])); > g_string_append_printf(s_SQL, ", %s)", > getSafeD(perf->metric_state)); >=20 > I've changed it to >=20 > g_string_append_printf(s_SQL, ", %s", > getSafeD(perf->d[PERF_VALUE_WARN_END])); > g_string_append_printf(s_SQL, ", %s", > getSafeD(perf->d[PERF_VALUE_CRIT_END])); > g_string_append_printf(s_SQL, ", %s)", > getSafeD(perf->metric_state)); >=20 > and the data begun to show up in perfdata_service_bin. However, metric_= state values were still wrong and inconsistent indeed with perfdata_servi= ce_raw. In the example I sent you, the metrics were 2 (CRITICAL) in perfd= ata_service_bin; OTOH they were 0 (NORMAL) in perfdata_service_raw. And t= he graphs continued not showing the guides for warning/critical threshold= s. At this point, I rolled back to release 0.100.7. >=20 > I've found performance problems also in 0.101.1, as I feel that it is m= uch slower than 0.100.7 when reading the serviceperf.log file and putting= it into the database. In 0.100.7 I've got thousands of lines per second;= in 0.101.1 this number never is greater than 70 lines/sec. And I'm runni= ng on a machine with 512 MB RAM, 2xIntel Xeon 3.06 GHz! I've tried to opt= imize MySQL settings to no avail, and this was other reason that leaded m= e to roll back to 0.100.7. >=20 > Also, the documentation is a little confusing in this release. It took = me some time until I understood that, with --default-perfdata I wouldn't = have to use crontab entries anymore to update the database. There's no me= ntion of this in the doocumentation, and if it sounds obvious for the dev= eloping team, it may be not so clear for the users. >=20 > Don't get me wrong: I find that perfparse is THE solution for gathering= performance data for Nagios. However, I feel that this wasn't the right = time to release 0.101.1 because it clearly lacks polishing and has rough = edges on database architecture and plugin parsing output. >=20 > Why don't you add a compilation switch to disable these burning edge fe= atures? It would make life easier to people that rely on perfparse for da= ta gathering on production systems. >=20 > []'s and keep the great work, >=20 > Paulo Afonso Graner Fessel > Administrador de Ambiente e Sistemas UNIX > pau...@pr... > OWT > Fone: +55 (11) 3038-6554 > Fax: +55 (11) 3038-6508 > http://www.primesys.com.br > =20 > =20 > =20 > =20 >=20 >=20 >>-----Mensagem original----- >>De: Ben Clewett [mailto:Be...@cl...]=20 >>Enviada em: ter=E7a-feira, 19 de outubro de 2004 04:25 >>Para: Paulo Afonso Graner Fessel >>Cc: per...@li... >>Assunto: Re: [Perfparse-users] Warning/critical values not=20 >>going into the database... Again >> >>Paulo, >> >>Can you please send me a sample of your data, I want to=20 >>replicate and fix this problem. >> >>Regards, >> >>Ben Clewett. >> >>Paulo Afonso Graner Fessel wrote: >> >> >>>Hello, folks. >>>=20 >>>I've just upgraded to 0.101.1 and I'm noticing that=20 >> >>warning/critical=20 >> >>>values from plugins are not getting into the database again. But=20 >>>differently (and worst) than last time, seems that the=20 >> >>state field of=20 >> >>>perfdata_service_bin is also incorrect: >>>=20 >>> >> >>+-------------+-----------------------------+----------------- >>------------+---------------------+----------+--------+------- >>---+--------+ >> >>>| host_name | service_description |=20 >>>metric | ctime | value =20 >> >> | warn |=20 >> >>>critical | state | >>> >> >>+-------------+-----------------------------+----------------- >>------------+---------------------+----------+--------+------- >>---+--------+ >> >>>| D01 | Cache Hits |=20 >>>lib | 2004-10-18 17:35:58 | =20 >> >>99.99 | 0=20 >> >>>| 0 | 2 | >>>| D01 | Cache Hits |=20 >>>buffer | 2004-10-18 17:35:58 | =20 >> >>99.95 | 0=20 >> >>>| 0 | 2 | >>> >> >>+-------------+-----------------------------+----------------- >>------------+---------------------+----------+--------+------- >>---+--------+ >> >>>In my definition of this particular service, I want these=20 >> >>two metrics=20 >> >>>to be as high as possible, with a maximum value of 100%.=20 >> >>However, as=20 >> >>>you can see, I don't have warning and critical values for=20 >> >>this metric,=20 >> >>>and also its state as determined by perfparse is 2 (CRITICAL); it=20 >>>should be 0 actually (NORMAL). >>>=20 >>>[]'s >>>=20 >>>*Paulo Afonso Graner Fessel* >>>/Administrador de Ambiente e Sistemas UNIX/=20 >>>pau...@pr... <mailto:pau...@pr...> >>>OWT >>>Fone: +55 (11) 3038-6554 >>>Fax: +55 (11) 3038-6508 >>>http://www.primesys.com.br <http://www.primesys.com.br/> >>>=20 >>>=20 >>>=20 >> >> >=20 |
|
From: Ricardo D. M. <ric...@gm...> - 2004-10-25 18:12:31
|
I have no problem seing the results, but the error appears just the same. I only found the error because i am making tests for a real production environment. > Could you run > perfparse-log2db <your options here> --show-config I only have the perfparse-db-tool. # ./perfparse-db-tool --show_config DB_User =3D "nagios" DB_Name =3D "nagios" DB_Pass =3D "******" DB_Host =3D "127.0.0.1" Drop_File =3D "/tmp/perfparse.drop" Service_Log =3D "/usr/local/nagios/var/serviceperf.log" Host_Log =3D "/usr/local/nagios/var/hostperf.log" Dummy_Hostname =3D "dummy" Delete_Service_Log =3D "No" Delete_Host_Log =3D "No" Nagios_Lock =3D "/usr/local/nagios/var/nagios.lock" Lock_File =3D "/var/lock/perfparse.lock" Be_Silent =3D "no" Do_Report =3D "no" Accept_Odd_Chars_in_Label =3D "no" Default_user_permissions_Policy =3D "rw" Default_user_permissions_Host_groups =3D "rw" Regards --=20 Ricardo David Martins ___________________________________________________________________________= __________________________ AVISO Esta mensagem (incluindo quaisquer anexos) pode conter informa=E7=E3o confidencial para uso exclusivo do destinat=E1rio. Se n=E3o for o destinat=E1rio pretendido, n=E3o dever=E1 usar, distribuir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado. DISCLAIMER This e-mail (including any attachments) may contain confidential information for exclusive use of its recipient. If you are not the intended recipient you must not use, distribute or copy this e-mail. If you have received this e-mail in error please notify the sender and delete it immediately. Thank You. ___________________________________________________________________________= __________________________ |
|
From: Yves M. <yme...@li...> - 2004-10-25 14:48:45
|
>> We (the developpers) try to support only the latest versions. If this = is a bug, it can >> have been fixed in a more recent version. We are not a company that se= ll support on >> older version of the software but few hackers who are trying to do our= best on some >> free >> software. >> For bug reports, please upgrade to some more recent version. > > I fetched PP 2 months ago... time flies but really!!! I copied the > version from perfparse_state table but the tar.gz is 0.100.3. Perfparse was rewritten. So any bug reported on 0.100.X or older version = will not help. >> If you are asking for support, maybe somebody here can answer you. Thi= s is probably >> the >> best place to ask for support. > > Support for what? Fixing bugs? This doesn't seem like support. Seems > like development. Use per...@li... for development :) [...] >> And ask yourself if you would answer to somebody who says he has probl= ems to connect >> to >> localhost.localdomain with user nagios on db nagios with no other prec= isions. What >> would >> you answer then ? > > I mentioned mysql, PP version 0.14, nagios queries being OK and 8 > times the mysql error log (this seemed a little over the top) and that > the error happens on PP CGI consulting GUI. It seems null > information, so i tell more... pp is version 0.100.3 as you wrote it at the beginning. Not 0.14. Some interesting remark to Ben : we don't have a table with what version = of perfparse use what version of the database schema. However, 0.100.3 <-> 0.14 is cor= rect. No problem here :) > Archlinux wombat kernel 2.6.8.1, mysql 4.0.21, nagios 1.2 (all on both > replicas, which means the problem occurs on two hosts) > > I just want to know if any body else found this error before or even > an idea for this to happen (Yves doesn't seem to). Yes, I've already had such a problem : mistyping in the password :) Could you run perfparse-log2db <your options here> --show-config and tell us the results (notice that you will print the db password. Hide= it if you want) I don't say I will be able to help, but I ask questions and maybe somebod= y will have the idea :) 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/ - |
|
From: Ricardo D. M. <ric...@gm...> - 2004-10-25 14:33:03
|
> We (the developpers) try to support only the latest versions. If this is = a bug, it can > have been fixed in a more recent version. We are not a company that sell = support on > older version of the software but few hackers who are trying to do our be= st on some free > software. > For bug reports, please upgrade to some more recent version. I fetched PP 2 months ago... time flies but really!!! I copied the version from perfparse_state table but the tar.gz is 0.100.3. > If you are asking for support, maybe somebody here can answer you. This i= s probably the > best place to ask for support. Support for what? Fixing bugs? This doesn't seem like support. Seems like development. > But don't copy the log without understanding it. We don't need 8 times th= e same line. "... don't copy the log without understanding..." Is this the wrong mailing list? > And ask yourself if you would answer to somebody who says he has problems= to connect to > localhost.localdomain with user nagios on db nagios with no other precisi= ons. What would > you answer then ? I mentioned mysql, PP version 0.14, nagios queries being OK and 8 times the mysql error log (this seemed a little over the top) and that the error happens on PP CGI consulting GUI. It seems null information, so i tell more... Archlinux wombat kernel 2.6.8.1, mysql 4.0.21, nagios 1.2 (all on both replicas, which means the problem occurs on two hosts) I just want to know if any body else found this error before or even an idea for this to happen (Yves doesn't seem to). Regards --=20 Ricardo David Martins ___________________________________________________________________________= __________________________ AVISO Esta mensagem (incluindo quaisquer anexos) pode conter informa=E7=E3o confidencial para uso exclusivo do destinat=E1rio. Se n=E3o for o destinat=E1rio pretendido, n=E3o dever=E1 usar, distribuir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado. DISCLAIMER This e-mail (including any attachments) may contain confidential information for exclusive use of its recipient. If you are not the intended recipient you must not use, distribute or copy this e-mail. If you have received this e-mail in error please notify the sender and delete it immediately. Thank You. ___________________________________________________________________________= __________________________ |
|
From: Yves M. <yme...@li...> - 2004-10-25 13:42:40
|
> Hi, > > i am currently testing perfparse version 0.14 on a mysql crossed > replication solution. I know it's not the last version. Anyways i We (the developpers) try to support only the latest versions. If this is = a bug, it can have been fixed in a more recent version. We are not a company that sell = support on older version of the software but few hackers who are trying to do our be= st on some free software. For bug reports, please upgrade to some more recent version. If you are asking for support, maybe somebody here can answer you. This i= s probably the best place to ask for support. But don't copy the log without understanding it. We don't need 8 times th= e same line. And ask yourself if you would answer to somebody who says he has problems= to connect to localhost.localdomain with user nagios on db nagios with no other precisi= ons. What would you answer then ? Regards, 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/ - |
|
From: Ricardo D. M. <ric...@gm...> - 2004-10-25 13:19:09
|
Hi, i am currently testing perfparse version 0.14 on a mysql crossed replication solution. I know it's not the last version. Anyways i found a problem dealing with mysql innodb queries. When i consult the nagios native CGIs i found no problem. When consulting PerfParse CGI (the only that uses innodb) I found this persistent error on each resulting query to the data base. 041025 14:02:29 Aborted connection 1882 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) 041025 14:02:34 Aborted connection 1884 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) 041025 14:02:55 Aborted connection 1889 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) 041025 14:02:59 Aborted connection 1891 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) 041025 14:03:04 Aborted connection 1893 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) 041025 14:04:04 Aborted connection 1896 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) 041025 14:10:21 Aborted connection 1904 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) 041025 14:10:22 Aborted connection 1903 to db: 'nagios' user: 'nagios' host: `localhost.localdomain' (Got an error reading communication packets) I actually didn't detect (yet) any practical manifestation of this error but i felt i should report it. My regards --=20 Ricardo David Martins ___________________________________________________________________________= __________________________ AVISO Esta mensagem (incluindo quaisquer anexos) pode conter informa=E7=E3o confidencial para uso exclusivo do destinat=E1rio. Se n=E3o for o destinat=E1rio pretendido, n=E3o dever=E1 usar, distribuir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado. DISCLAIMER This e-mail (including any attachments) may contain confidential information for exclusive use of its recipient. If you are not the intended recipient you must not use, distribute or copy this e-mail. If you have received this e-mail in error please notify the sender and delete it immediately. Thank You. ___________________________________________________________________________= __________________________ |
|
From: Yves M. <yme...@li...> - 2004-10-25 13:17:44
|
Hi Nick, Well, sorry for answering so late... Yes, this is a bug. In fact, gd provides some gdlib-config script to get the flags and libs t= o use to link against gdlib. But 0.100.7 and previous version, and 0.101.1 too, don't u= se that but do it "by hand". This is why some may have to specify something about iconv = and why you have problems with png. In 0.102 versions (starting at 0.102.0ym7 on my unofficial web page http://pagesperso.laposte.net/ymettier/perfparse-devel/), this is fixed, = and perfparse uses gdlib-config. This was tested with libgd 2.0. If you have an older version of libgd, please upgrade. If not possible, y= ou will have to specify the options yourself when running make : make CFLAGS=3D"-I/path/to/gd/lib" LDFLAGS=3D"-L/path/to/libraries -lpng -= liconv ..." Thanks Nick for reporting this bug, and again, sorry to answer so late Yves > > I am new to Nagios and Perfparse, but though this might be useful to so= meone: > > I was having trouble installing PP on RH FC 2, although I had all the > prerequisite packages installed, I was getting lots of compile errors l= ike: > > gcc -g -O2 -Wall -o .libs/perfchart.png perfchart.o cgi.o -L/usr/lib/m= ysql > /usr/lib/mysql/libmysqlclient.a -lcrypt -lnsl -lm -lz -lc -lnss_files -= lnss_dns -lresolv > -lglib-2.0 -L/lib -lgd -L/opt/perfparse-0.100.7/libperfparse > /opt/perfparse-0.100.7/libperfparse/.libs/libperfparse.so -Wl,--rpath > -Wl,/opt/nagios/lib > /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgd.a(gd_png.o)(.te= xt+0x37): In > function `gdPngErrorHandler': > : undefined reference to `png_get_error_ptr' > /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgd.a(gd_png.o)(.te= xt+0xa9): In > function `gdPngReadData': > : undefined reference to `png_get_io_ptr' > /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libgd.a(gd_png.o)(.te= xt+0xe9): In > function `gdPngWriteData': > > After adding -lpng to the line starting MYSQL_LIBS in cgi/Makefile (bef= ore -lz) > compilation proceeded sucessfully! > > Perhaps someone else knows if there is a bug in the configure script? > > Cheers > > =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D > Nick P G Smith --=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/ - |
|
From: Yves M. <yme...@li...> - 2004-10-25 12:14:28
|
> Hi Yves, > > Wouldn't it be better to set a default path there (e.g. $NAGIOSDIR$\var= ) > like it's already been used by the perfparse logfiles when you use the > Service_Log_Save_Position "yes" option? No. Read the code and you will notice that what you are asking for is exa= ctly what is in perfparse-0.101.1. But you have problems with it. This is the proof that $NAGIOSDIR$/var (this is LOCALSTATEDIR thanks to autoconf/automake) is not a good solution. Ben had the same problems as you, in the same conditions. So you are not = even part of the 20% who complain 80% of the time :) I don't pretend to offer the Solution to that problem with my new impleme= ntation and I'm open to any suggestion :) > Ok, my changes in the doc would be obsolete then but... :-) ... but I read them and updated the doc according to what was not obsolet= e ! Thanks again :) > I think there will be a few irritations and Maillist posts of users who > don't read the manual correctly and who will run into an error after > starting perfparse. Before perfparse-1.0, I read carefully the mailing lists and pay attentio= n to any good suggestion. If some irritation in a post is constructive anyways, I read = it too :) 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/ - |
|
From: Sand P. <Phi...@sy...> - 2004-10-25 10:34:21
|
Hi Yves, Wouldn't it be better to set a default path there (e.g. $NAGIOSDIR$\var) like it's already been used by the perfparse logfiles when you use the Service_Log_Save_Position "yes" option?=20 Ok, my changes in the doc would be obsolete then but... :-) I think there will be a few irritations and Maillist posts of users who don't read the manual correctly and who will run into an error after starting perfparse.=20 Regards, Philipp > -----Original Message----- > From: Yves Mettier [mailto:yme...@li...]=20 > Sent: Monday, October 25, 2004 11:50 AM > To: per...@li... > Cc: Sand Philipp > Subject: RE: [Perfparse-users] install guide update (was : DB=20 > Size grows very fast since v101.01) >=20 >=20 > > I did a little update to Method 1 in the docbook. Hope=20 > thats what you=20 > > meant :) See file Attached >=20 > Thanks Philipp, > Thanks Tim too for your previous mail. >=20 > The install guide had been updated already (for coming=20 > 0.102.1) so I mixed your changes more than I applied them. > I also modified your comments about the position mark path=20 > because I made a change in perfparse : you have to set=20 > Service_Log_Save_Position to "yes" now. This is enabled by default. > You also have to specify a path, that is "" by default. >=20 > If you don't configure anything, perfparse wants to use the=20 > position mark path but finds an empty path. This used to mean=20 > that you did not want to use the option and perfparse used to=20 > run a way you did not want. This is now explicitely an error=20 > and perfparse will not run that way. > Either disable the use of the Service_Log_Save_Position or=20 > explicitely specify a path. >=20 > You can find some updated documentation here : > http://pagesperso.laposte.net/ymettier/perfparse-devel/perfparse-doc/ >=20 > This is the documentation for perfparse-0.102.0ym6 that you=20 > can find here : > http://pagesperso.laposte.net/ymettier/perfparse-devel/perfpar > se-0.102.0/ >=20 > Warning : perfparse source packages with ymX appended to the=20 > version number are my own versions and are unofficial. I do=20 > not support them. Use them at your own risk. > However, I appreciate feedback to improve those versions that=20 > will become official when Ben validates them. >=20 > Yves >=20 >=20 > --=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/ - >=20 >=20 >=20 >=20 ************************************************ sycor plastics - die neue Branchenl=F6sung f=FCr die Kunststoffindustrie www.sycor-plastics.de ************************************************ Diese E-Mail ist vertraulich und kann dar=FCber hinaus pers=F6nliche Info= rmationen beinhalten. Wenn Sie nicht der bestimmungsgem=E4=DFe Empf=E4nge= r sind, l=F6schen Sie bitte die E-Mail und deren Anh=E4nge sofort und ben= achrichtigen Sie uns dar=FCber. Die Firma sycor willigt in keine Vertr=E4= ge oder vertragliche Verpflichtungen ein oder =FCbermittelt rechtsverbind= liche Angebote, die in Form von E-Mail versandt werden, sofern dies nicht= ausdr=FCcklich in schriftlicher Form zwischen den Parteien vereinbart wu= rde. This e-mail is confidential and may contain personal and/or privileged in= formation. If you are not the intended recipient please delete this e-mai= l and all attachments immediately and inform us. The company sycor does n= ot agree with contracts or contract obligations sent by e-mail, neither d= o we transmit legally binding offers by e-mail, unless this is not expres= sly agreed upon between the parties and documented in written form. |
|
From: Yves M. <yme...@li...> - 2004-10-25 09:50:05
|
> I did a little update to Method 1 in the docbook. Hope thats what you > meant :) > See file Attached Thanks Philipp, Thanks Tim too for your previous mail. The install guide had been updated already (for coming 0.102.1) so I mixe= d your changes more than I applied them. I also modified your comments about the position mark path because I made= a change in perfparse : you have to set Service_Log_Save_Position to "yes" now. This = is enabled by default. You also have to specify a path, that is "" by default. If you don't configure anything, perfparse wants to use the position mark= path but finds an empty path. This used to mean that you did not want to use the option = and perfparse used to run a way you did not want. This is now explicitely an error and = perfparse will not run that way. Either disable the use of the Service_Log_Save_Position or explicitely sp= ecify a path. You can find some updated documentation here : http://pagesperso.laposte.net/ymettier/perfparse-devel/perfparse-doc/ This is the documentation for perfparse-0.102.0ym6 that you can find here= : http://pagesperso.laposte.net/ymettier/perfparse-devel/perfparse-0.102.0/ Warning : perfparse source packages with ymX appended to the version numb= er are my own versions and are unofficial. I do not support them. Use them at your own = risk. However, I appreciate feedback to improve those versions that will become= official when Ben validates them. 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/ - |
34 messages has been excluded from this view by a project administrator.
