irc-collective-support Mailing List for IRC Collective
Status: Beta
Brought to you by:
ramsesm
Menu
▾
▴
irc-collective-support — For help on installing and using the software.
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
|
|
From: Ramses M. <ra...@ma...> - 2009-10-25 14:29:26
|
> chip@some:~/dl/irc-collective-0.1.4/parser> ./parselog -g -e > --output-handler=SQL --output-filename=./this --input-format=Irssi -c "fluidgravity" -l ~/irclogs/Freenode/#fluidgravity.log.20091020 > Direct ConfigFile usage is deprecated, please use Config::File instead at ./parselog line 31 > Can't call method "print_config" on an undefined value at ./parselog line 268. The ConfigFile module that the parselog script *should* load is actually part of the IRC Collective distribution itself and not Perl. I am thinking that your Perl installation is actually trying to load a *different* ConfigFile Perl module instead. You could try to insert the following statement at line 30: use lib '.'; > If you don't mind, I might hack it up a bit, fix for the new > Config::File usage, and see what else I can do with it. I'll submit the diff as per your dev instructions, if you use it, great, if not, that's cool too. > I don't mind at all! I'm actually looking forward to your diff. :) -- Ramses |
|
From: Token <to...@fl...> - 2009-10-22 23:18:21
|
chip@some:~/dl/irc-collective-0.1.4/parser> ./parselog -g -e --output-handler=SQL --output-filename=./this --input-format=Irssi -c "fluidgravity" -l ~/irclogs/Freenode/#fluidgravity.log.20091020 Direct ConfigFile usage is deprecated, please use Config::File instead at ./parselog line 31 Can't call method "print_config" on an undefined value at ./parselog line 268. If you don't mind, I might hack it up a bit, fix for the new Config::File usage, and see what else I can do with it. I'll submit the diff as per your dev instructions, if you use it, great, if not, that's cool too. I've been lookin for an app like this for a while, started writing my own and then found this. Ultimately I'd like to have something similar to: http://weblog.disgu.st WARNING that site has some rather unsavory things, but the working of it is neat. --chip On Thu, Oct 22, 2009 at 7:13 PM, Token <to...@fl...> wrote: > I honestly wasn't. I plan on using the SQL to stick it in the > database, I was just testing the output before I started filling up > the DB. > > I'll go try SQL and see how that goes. > > Thanks! > > --chip > > On Thu, Oct 22, 2009 at 1:59 PM, Ramses Matabadal <ra...@ma...> wrote: >>> I'm calling the parselog script as: >>> ./parselog -e --output-handler=XML --output-filename=./this >>> --input-format=Irssi -c "fluidgravity" -l >>> ~/irclogs/IRC/#fluidgravity.log.20091020 >>> >> >> Hi Chip, >> >> The XML output handler has not yet been implemented. The program could be a >> bit more user friendly in terms of error messages regarding this issue. >> >> Out of curiosity, how where you going to use the XML output? >> >> >> -- >> Ramses >> >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Irc-collective-support mailing list >> Irc...@li... >> https://lists.sourceforge.net/lists/listinfo/irc-collective-support >> > |
|
From: Token <to...@fl...> - 2009-10-22 23:13:47
|
I honestly wasn't. I plan on using the SQL to stick it in the database, I was just testing the output before I started filling up the DB. I'll go try SQL and see how that goes. Thanks! --chip On Thu, Oct 22, 2009 at 1:59 PM, Ramses Matabadal <ra...@ma...> wrote: >> I'm calling the parselog script as: >> ./parselog -e --output-handler=XML --output-filename=./this >> --input-format=Irssi -c "fluidgravity" -l >> ~/irclogs/IRC/#fluidgravity.log.20091020 >> > > Hi Chip, > > The XML output handler has not yet been implemented. The program could be a > bit more user friendly in terms of error messages regarding this issue. > > Out of curiosity, how where you going to use the XML output? > > > -- > Ramses > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Irc-collective-support mailing list > Irc...@li... > https://lists.sourceforge.net/lists/listinfo/irc-collective-support > |
|
From: Ramses M. <ra...@ma...> - 2009-10-22 18:24:30
|
> I'm calling the parselog script as: > ./parselog -e --output-handler=XML --output-filename=./this > --input-format=Irssi -c "fluidgravity" -l > ~/irclogs/IRC/#fluidgravity.log.20091020 > Hi Chip, The XML output handler has not yet been implemented. The program could be a bit more user friendly in terms of error messages regarding this issue. Out of curiosity, how where you going to use the XML output? -- Ramses |
|
From: Chip G. <ch...@fl...> - 2009-10-21 06:54:33
|
Getting around the deprecated ConfigFile usage by specifying all the options from the command line I get this: Use of uninitialized value in subroutine entry at IRCParser.pm line 344. Undefined subroutine &main:: called at IRCParser.pm line 344. I'm calling the parselog script as: ./parselog -e --output-handler=XML --output-filename=./this --input-format=Irssi -c "fluidgravity" -l ~/irclogs/IRC/#fluidgravity.log.20091020 Full Output: chip@some:~/dl/irc-collective-0.1.4/parser> ./parselog -e --output-handler=XML --output-filename=./this --input-format=Irssi -c "fluidgravity" -l ~/irclogs/Freenode/#fluidgravity.log.20091020 Direct ConfigFile usage is deprecated, please use Config::File instead at ./parselog line 31 WARNING: --logfile given, ignoring --directory. Use of uninitialized value in subroutine entry at IRCParser.pm line 344. Undefined subroutine &main:: called at IRCParser.pm line 344. When enabling debug: chip@some:~/dl/irc-collective-0.1.4/parser> ./parselog -g -e --output-handler=XML --output-filename=./this --input-format=Irssi -c "fluidgravity" -l ~/irclogs/Freenode/#fluidgravity.log.20091020 Direct ConfigFile usage is deprecated, please use Config::File instead at ./parselog line 31 Can't call method "print_config" on an undefined value at ./parselog line 268. I'll be happy to supply any additional info, just let me know what you need. System Info: chip@some:~> cat /etc/issue Ubuntu 8.04.3 LTS \n \l chip@some:~> uname -a Linux some.boxonthe.net 2.6.18.8-xen #1 SMP Mon Mar 2 16:51:54 EST 2009 i686 GNU/Linux chip@some:~> perl -v This is perl, v5.8.8 built for i486-linux-gnu-thread-multi Copyright 1987-2006, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using "man perl" or "perldoc perl". If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. chip@some:~> |
|
From: Dave T <da...@li...> - 2007-09-12 00:28:45
|
This issue was just a matter of the naming convention of the logfile...with a properly named file it works fine. Dave On Tuesday 11 September 2007 4:13:55 pm Dave T wrote: > I am trying to parse some eggdrop logs...I get a whole bunch of this: > > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 280, <LOG> line 488. > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 280, <LOG> line 488. > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 280, <LOG> line 488. > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 358, <LOG> line 488. > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 358, <LOG> line 488. > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 358, <LOG> line 488. > DBD::mysql::st execute failed: Duplicate entry '0000-00-00-488' for key 1 > at OutputHandler/SQL.pm line 365, <LOG> line 488. > entry '0000-00-00-434' for key 1ERROR: Could not add to database: Duplicate > entry '0000-00-00-435' for key 1ERROR: Could not add to database: Duplicate > (lots of output trimmed here.....) > entry '0000-00-00-486' for key 1ERROR: Could not add to database: Duplicate > entry '0000-00-00-487' for key 1ERROR: Could not add to database: DuUse of > uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm > line 280, <LOG> line 489. > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 280, <LOG> line 489. > Use of uninitialized value in concatenation (.) or string at > OutputHandler/SQL.pm line 280, <LOG> line 489. > > Any idea how to work around this? I am using version 0.1.4. > > BTW: Nice project...fits my needs pretty well. > > Thanks, > Dave |
|
From: Dave T <da...@li...> - 2007-09-11 23:12:52
|
I am trying to parse some eggdrop logs...I get a whole bunch of this: Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 280, <LOG> line 488. Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 280, <LOG> line 488. Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 280, <LOG> line 488. Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 358, <LOG> line 488. Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 358, <LOG> line 488. Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 358, <LOG> line 488. DBD::mysql::st execute failed: Duplicate entry '0000-00-00-488' for key 1 at OutputHandler/SQL.pm line 365, <LOG> line 488. entry '0000-00-00-434' for key 1ERROR: Could not add to database: Duplicate entry '0000-00-00-435' for key 1ERROR: Could not add to database: Duplicate (lots of output trimmed here.....) entry '0000-00-00-486' for key 1ERROR: Could not add to database: Duplicate entry '0000-00-00-487' for key 1ERROR: Could not add to database: DuUse of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 280, <LOG> line 489. Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 280, <LOG> line 489. Use of uninitialized value in concatenation (.) or string at OutputHandler/SQL.pm line 280, <LOG> line 489. Any idea how to work around this? I am using version 0.1.4. BTW: Nice project...fits my needs pretty well. Thanks, Dave |