Lire 1.3 on RedHat 9

[Francis J. Lacoste]

On jeu, 2003-06-26 at 20:02, Willman, Matt B - CNF wrote:
> So, after upgrading everything to the latest (xml, xslt, blah, blah) the
> core dumps I've been experiencing have gone away.  However, I am getting a
> new, improved error! :)

Did you upgrade using the Red Hat-provided RPMS, or did you upgrade
to the latest vesrion provided by "upstreams" (the original download
place for each software piece)?

In any case, can you provide the "working" version numbers. Some 
other RH 9.0 users are experiencing the segfault, and we'd like
to be able to tell them which components versions "works".

> 
> Snippets from the debug output are below.  Apparently the 'maxdepth'
> parameter wasn't quite large enough, and is causing problems.
> 
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says
> runtime error: file /usr/local/share/lire/xml/stylesheet/xsl/docbook.xsl
> line 292 element row
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says
> xsltApplyOneTemplate: loop found ???
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says try
> increasing xsltMaxDepth (--maxdepth)
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says
> Templates:
> 
> <SNIPPED>
> 
> all all lr_tag-20030626162131-23322 lr_xslt info creating XML catalog
> /tmp/lr_xslt-lr_tag-20030626162131-23322-23530-catalog.xml
> all all lr_tag-20030626162131-23322 lr_xslt info running xsltproc with
> --maxdepth '100000' --nonet
> /usr/share/sgml/docbook/docbook-xsl-1.61.3/html/docbook.xsl
> /tmp/lr_xml2html.all.23423.dbx
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says
> /tmp/lr_xml2html.all.23423.dbx:1: error: Start tag expected, '<' not found
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says
> Object is a Node Set :
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says ^
> all all lr_tag-20030626162131-23322 lr_xslt info /usr/bin/xsltproc says
> unable to parse /tmp/lr_xml2html.all.23423.dbx
> all all lr_tag-20030626162131-23322 lr_xslt info stopped
> all all lr_tag-20030626162131-23322 lr_xml2html info stopped
> 
> I added a "--maxdepth 100000" option to the command line passed to xsltproc
> in lr_xslt, but it seems to not have any effect.  Since the default is 5000
> (according to the documentation I found) it appears that maxdepth is not the
> issue.  I'm only seeing this error when trying to parse medium to big
> logfiles (+250000 lines or so).
> 
> Anyone seen this before?  Any ideas?
> 

That's the first time I hear about this. Are you able to format these
reports using the ASCII format? (This is just a check that the XML
report is fine.)

Also, not all reports have the same structure. (The size of the report
doesn't usually increase linearly with the number of log lines.) What
kind of reports are you generating (ftp, www, email, ...) ? Are you
using customized report specification.

Thanks for all the infos you can provide.


Francis J. Lacoste

-- 
Francis J. Lacoste              . .           http://www.logreport.org
/^LogReport$/               . .               flacoste at logreport.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.logreport.org/pipermail/development/attachments/20030705/a046b55d/attachment.bin