Can you get ANY mod_perl working at all? Personally I've had HORRIBLE problems with DSO's on Solaris 9. I never got mod_perl to work there except statically linked. Solaris is a total mess in this respect (don't get me started on Solaris, I think its KAKA in generally, but thats off topic...).
On Sunday 02 February 2003 04:02 pm, V Shah wrote: > Tried the virtual host method with no improvement. I decided to try > building a test apache with mod_perl compiled statically instead of as a > DSO... and AxKit works in this configuration. I tried copying this new > httpd.conf to the old apache tree (with LoadModule/AddModule > modifications), but the old server still fails. AxKit shouldn't require > mod_perl to be compiled statically, right? Could this be a solaris 9 > issue? > > V Shah > ----- Original Message ----- > From: "Pavel Penchev" <[EMAIL PROTECTED]> > To: "V Shah" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Sunday, February 02, 2003 11:20 AM > Subject: Re: can't get axkit working > > > Hi, I recomend you to stick with the Wiki docs. > Anyway here is my httpd.conf - it works perfectly for me: > > > NameVirtualHost * > PerlModule AxKit > > <VirtualHost *> > ServerName test.com > DocumentRoot /home/test > > <Directory "/home/test"> > Options -All +FollowSymLinks > > DirectoryIndex index.xsp > AddHandler AxKit .xml .xsp > > AxDebugLevel 10 > AxGzipOutput on > AxCacheDir /tmp > AxLogDeclines On > > > <Files *.xsp> > AxAddProcessor application/x-xsp . > AxAddProcessor text/xsl main.xsl > </Files> > > > AxAddXSPTaglib AxKit::XSP::Util > AxAddXSPTaglib AxKit::XSP::Param > AxAddXSPTaglib AxKit::XSP::Exception > AxAddXSPTaglib AxKit::XSP::WebUtils > > AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT > AxAddStyleMap application/x-xsp Apache::AxKit::Language::XSP > </Directory> > > CustomLog /home/test/LOGFILE combined > ErrorLog /home/test/ERRLOG > </VirtualHost> > > > I recomend you using virtual hosts even for testing purposes. The part with > the <Files> directive makes AxKit transform all .xsp files first with the > XSP processor and then through a main XSL stylesheet. The <Files> approach > I like very much - it keeps your .xsp code clean from transforming > directives. > > If this doesn't help it will be useful to see what your error log says - > set AxDebugLevel to 10 and give us the resulting error log. Also compile > apache without PHP because there are problems running PHP and mod_perl > statically compiled in the same apache server (it is a problem with some > shared mysql libraries as far as I know, try to search for this in google). > > Regards, > Pavel > ----- Original Message ----- > From: V Shah > To: [EMAIL PROTECTED] > Sent: Sunday, February 02, 2003 9:17 AM > Subject: can't get axkit working > > > Just installed AxKit 1.6 via CPAN on Solaris 9/sparc, Apache 1.3.27, > mod_perl 1.27. I'm trying to get some quick test examples working, but > haven't seen any success yet. > Following the instructions from the INSTALL document, I added the > following > directives to the end of my httpd.conf: > PerlModule AxKit > SetHandler axkit > AxCacheDir /tmp/axkit_cache/ > AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT > > I added the test.xml and test.xps documents as listed in > http://axkit.org/docs/guide.dkb, restarted the web server, then tried > accessing test.xml, and got just the xml source. The guide indicates > that I > should have gotten some output in the error log, but no errors are > reported, > even after adding the AxDebugLevel 10 directive. I tried another example > using xsl instead of xps, but got the same result, just the xml source. > I added AxLogDeclines On to my config, but again no errors were reported to > the log. > > Apache reports the following on a HEAD request, indicating that AxKit is > active: > Server: Apache/1.3.27 (Unix) AxKit/1.6 mod_perl/1.27 PHP/4.3.0 > I've tried disabling php and mod_ssl, but that didn't help. > > One interesting note is that my DirectoryIndex docs no longer work - > trying > to access the webserver root, I get a 500 internal server error, and this > does produce some axkit error output in the errorlog: > [Sun Feb 2 00:53:42 2003] [error] [client 192.168.1.100] [AxKit] [Error] > xmlParse returned error: 4, Document is empty > Start tag expected, '<' not found > > [Sun Feb 2 00:53:42 2003] [error] [client 192.168.1.100] [AxKit] From: > > /usr/local/lib/perl5/site_perl/5.8.0/sun4-solaris/Apache/AxKit/Exception.pm > > : 9 > > No additional output is given even when increasing AxDebugLevel to 10. > The > error goes away if I specifically enter in the name of the document (i.e. > I > access http://site/index.html instead of just http://site). > > Different docs on the site all suggest slightly different sets of > directives > to add to httpd.conf, but they all produce the same failure mode for me. > The main AxKit perldoc adds this line on top of those given in the > INSTALL document: > AxAddStyleMap application/x-xpathscript > Apache::AxKit::Language::XPathScript > > The "Main Guide" (http://axkit.org/docs/guide.dkb): > PerlModule AxKit > AddHandler axkit .xml > AddHandler axkit .xsp > AddHandler axkit .dkb > PerlSetVar AxXPSInterpolate 1 > > http://axkit.org/wiki/view/AxKit/AxKitConfigurationExample gives: > PerlModule AxKit > AddHandler axkit .xml .xsp .dkb > AxAddStyleMap text/xsl Apache::AxKit::Language::LibXSLT > AxAddStyleMap application/x-xsp Apache::AxKit::Language::XSP > AxAddStyleMap application/x-xpathscript > Apache::AxKit::Language::XPathScript > > The quick start (http://www.axkit.org/docs/quick_start.dkb): > PerlModule AxKit > SetHandler perl-script > PerlHandler AxKit > AxAddStyleMap application/x-xpathscript > Apache::AxKit::Language::XPathScript > AxAddStyleMap text/xsl Apache::AxKit::Language::Sablot > > The perl.com "Introducing AxKit" article: > PerlModule AxKit > <Directory "/home/me/axkit_articles-1.0/www/htdocs"> > Options -All +Indexes +FollowSymLinks > DirectoryIndex index.xsp > AddHandler axkit .xml .xsp > AxAddXSPTaglib AxKit::XSP::Util > AxAddStyleMap application/x-xsp \ > Apache::AxKit::Language::XSP > </Directory> > > I've tried using Apache::AxKit::Language::Sablot instead of > Apache::AxKit::Language::LibXSLT... doesn't make a difference. > > Versions of relevant supporting software: > gcc-3.2 > expat-1.95.5 > libxml2-2.4.26 > libxslt-1.0.22 > Sablot-0.97 > perl-5.8.0 > libapreq 1.1 > XML::LibXML 1.52 > XML::LibXSLT 1.52 > XML::Sablotron 0.90 > XML::XPath 1.13 > XML::SAX 0.12 > XML::Parser 2.31 > XML::NamespaceSupport 1.08 > > I've attached my httpd.conf as well as output from truss attached to a > running httpd -X upon access to test.xml (xps version). I'm sure there's > a > simple answer to this problem, but I've been staring at these config > files and searching the web for a while now and I just can't see it... > Thanks in advance. > > V Shah > > > > --------------------------------------------------------------------------- >- -- Tod Harter Giant Electronic Brain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
