ERROR XMLTooling.ParserPool

[Andy Bennett]

Hi,

This is a progress report on this issue. It presents some findings and
asks for help with the logging settings. Any hints or tips will be
warmly received.


> The other thing that triggered errors of this sort were mixing versions on
> the two sides of the remoting. For example, updating the Apache module and
> not shibd or failing to restart both after an upgrade. That's why I'm
> suspicious about the packaging.

I'm still plagued by this. I've done wider testing and there is always a
successful login and then subsequent logins to different IdPs always fail.

I built my own Debian package from the regular debian package source and
modified it to pass --with-fastcgi to configure. I then installed that
package and that's what I've been using.

I ensured that there was only the 2.4 versions of the other shib
packages (libshib5, rather than the 2.3 version libshib4).

I tested my FCGI binaries on Lighttpd and I get the problem.

I also tested the apache module that was built at the same time, with
the same compiler and libraries, as part of the same package. The Apache
module works reliably.

For both lighttpd and apache tests the package in question is
libapache2-mod-shib2 - 2.4.3+dfsg-2~bpo60+1local1 and differs from
2.4.3+dfsg-2~bpo60 only in the addition of --with-fastcgi at configure
time. It contains, amongst other things:

/usr/sbin/shibd
/usr/bin/shib-metagen
/usr/bin/resolvertest
/usr/bin/mdquery
/usr/lib/apache2/modules/mod_shib_22.so
/usr/lib/shibboleth/adfs-lite.so
/usr/lib/shibboleth/odbc-store.so
/usr/lib/shibboleth/adfs.so
/usr/lib/shibboleth/memcache-store.so

... and my additions:

/usr/lib/shibboleth/shibauthorizer
/usr/lib/shibboleth/shibresponder


...so it's something to do with the FastCGI build or implementation.
I shall continue to investigate further. Any assistance or pointers
would be greatly appreciated.

My configure settings in shibboleth-sp2/debian/rules are:
-----
override_dh_auto_configure:
        dh_auto_configure -- \
            --libexecdir=/usr/lib/$(DEB_HOST_MULTIARCH)/shibboleth \
            --localstatedir=/var --enable-apache-22 \
            --with-apxs2=/usr/bin/apxs2 --disable-dependency-tracking \
            --with-fastcgi \
            --with-memcached $(SYSTEM)
-----



I've not yet been able to get a useful package trace, but the logs
usually say:

-----
2012-10-04 09:52:01 ERROR XMLTooling.ParserPool [2]: fatal error on line
1, column 1, message: invalid byte '�' at position 1 of a 1-byte sequence
2012-10-04 09:52:01 ERROR Shibboleth.Listener [2]: error processing
incoming message: XML error(s) during parsing, check log for specifics
-----

and occasionally say any of the following:

-----
2012-10-04 06:38:26 ERROR XMLTooling.ParserPool [2]: fatal error on line
1, column 1, message: invalid byte '8' at position 2 of a 2-byte sequence
-----

-----
2012-10-03 14:14:41 ERROR XMLTooling.ParserPool [6]: fatal error on line
1, column 7265, message: invalid character 0x5
-----

-----
2012-10-03 14:31:50 ERROR XMLTooling.ParserPool [10]: fatal error on
line 1, column 1, message: invalid byte '' at position 2 of a 3-byte
sequence
-----

-----
2012-10-04 06:38:26 ERROR XMLTooling.ParserPool [2]: fatal error on line
1, column 1, message: invalid byte '8' at position 2 of a 2-byte sequence
-----

-----
2012-10-04 09:24:32 ERROR XMLTooling.ParserPool [2]: fatal error on line
1, column 7281, message: invalid character 0x5
-----

-----
2012-09-21 07:14:09 ERROR XMLTooling.ParserPool [2]: fatal error on line
1, column 7265, message: invalid character 0x5
-----


Can anyone tell me which bit of logging to wind up and where to tweak it?





Regards,
@ndy

-- 
andyjpb at knodium.com
http://www.knodium.com/