cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2004/10/02 07:46:32
Modified:src/docs/1.0/guide troubleshooting.pod
Log:
another solution for the print problem on OSX
Revision ChangesPath
1.31 +19 -0 modperl-docs/src/docs/1.0/guide/troubleshooting.pod
Index: troubleshooting.pod
===
RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -u -r1.30 -r1.31
--- troubleshooting.pod 2 Oct 2004 14:43:43 - 1.30
+++ troubleshooting.pod 2 Oct 2004 14:46:32 - 1.31
@@ -443,6 +443,25 @@
PerlHeaderParserHandler sub { tie *STDOUT, 'Apache' unless tied *STDOUT;
}
+Another solution is not to use un unqualified Cprint(), but
+C$r-Egtprint(), for example replace:
+
+ print Hello;
+
+with:
+
+ $r-print(Hello);
+
+If you don't have C$r, you can obtain it with:
+
+ my $r = Apache-request;
+
+
+
+
+
+
+
=head2 exit signal Segmentation fault (11) with mysql
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2004/05/04 20:29:38 Modified:src/docs/1.0/guide troubleshooting.pod Log: be aware that CPerl sections can also cause leaks during graceful restarts. Submitted by: Brad Bowman [EMAIL PROTECTED] Revision ChangesPath 1.28 +7 -2 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.27 retrieving revision 1.28 diff -u -u -r1.27 -r1.28 --- troubleshooting.pod 12 Apr 2004 19:08:06 - 1.27 +++ troubleshooting.pod 5 May 2004 03:29:38 - 1.28 @@ -759,13 +759,18 @@ cleanup normally isn't a requirement, you can disable it by setting the PERL_DESTRUCT_LEVEL environment variable to -1. See the section LSpeeding up the Apache Termination and -Restart|general::control::control/Speeding_up_the_Apache_Termination_and_Restart for -more information. +Restart|general::control::control/Speeding_up_the_Apache_Termination_and_Restart +for more information. =head2 httpd keeps on growing after each restart See the IHUP Signal explanation at the section: LServer Stopping and Restarting|general::control::control/Server_Stopping_and_Restarting + +Also, be aware that CEltPerlEgt sections can also cause leaks +during graceful restarts. See the (sub)thread: +http://aspn.activestate.com/ASPN/Mail/Message/modperl/304620 (META: we +don't have code samples, so if you have such please let us know). =head1 OS Specific Notes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2004/04/07 10:12:53 Modified:src/docs/1.0/guide troubleshooting.pod Log: document the issue with Symbol.pm and . being first in @INC during the mod_perl build Revision ChangesPath 1.26 +31 -0 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.25 retrieving revision 1.26 diff -u -u -r1.25 -r1.26 --- troubleshooting.pod 13 Jun 2003 00:30:14 - 1.25 +++ troubleshooting.pod 7 Apr 2004 17:12:53 - 1.26 @@ -21,8 +21,39 @@ =head1 Building and Installation +=head2 Bareword gensym not allowed while strict subs + +When building mod_perl one may get the following failure: + + make[1]: Entering directory `.../mod_perl-1.29/Symbol' + Running Mkbootstrap for Apache::Symbol () + ... + Bareword gensym not allowed while strict subs in use at + /usr/lib/perl5/5.8.3/Pod/Parser.pm line 1158. + ... + make: *** [subdirs] Error 2 + +That happens when you you've modify C@INC to push C. before all +other directories, whereas it should be last. When C. is first in +C@INC it picks Fmod_perl-1.29/Symbol/Symbol.pm when it's inside +the directory Fmod_perl-1.29/Symbol. This shouldn't happen if your +system paths are coming first. To check your C@INC, run: + + % perl -V + +and it'll appear at the end of the output. Usually C. is pushed +first by setting a CPERL5LIB or a similar environment +variable. Unset it and repeat the build process to solve the problem. + + +=head2 make test issues + See Lmake Troubleshooting|guide::install/make_Troubleshooting and Lmake test Troubleshooting|guide::install/make_test_Troubleshooting + + + + =head1 Configuration and Startup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2003/06/12 17:30:14 Modified:src/docs/1.0/guide troubleshooting.pod Log: document the RH locale issues Submitted by: Perrin Harkins [EMAIL PROTECTED] Revision ChangesPath 1.25 +13 -0 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- troubleshooting.pod 10 Jun 2003 23:37:50 - 1.24 +++ troubleshooting.pod 13 Jun 2003 00:30:14 - 1.25 @@ -670,6 +670,19 @@ =head1 OS Specific Notes +=head2 RedHat Linux + +=head3 RH 8 and 9 Locale Issues + +RedHat 8 and 9 ship Perl with a locale setting that breaks perl. To +solve the problem either change the locale to en_US.ISO8859-1 or +simply remove the UTF8 part. + +For more information refer to: +http://twiki.org/cgi-bin/view/Codev/UsingPerl58OnRedHat8 +http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=87682 + + =head2 OpenBSD =head3 Issues Caused by httpd being Cchroot'ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2003/06/10 16:37:50 Modified:src/docs/1.0/guide troubleshooting.pod Log: correct an L entry Revision ChangesPath 1.24 +1 -1 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- troubleshooting.pod 29 May 2003 23:54:04 - 1.23 +++ troubleshooting.pod 10 Jun 2003 23:37:50 - 1.24 @@ -484,7 +484,7 @@ Perl 5.005+ plus is recommended for its improved malloc.c and other features that improve mod_perl and are turned on by default. -See also L/Out_of_memory_ +See also LOut of memory|/Out_of_memory_ =head2 Out of memory! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2003/05/29 16:54:04 Modified:src/docs/1.0/guide troubleshooting.pod Log: OpenBSD and chroot issues Submitted by: Ed [EMAIL PROTECTED] Revision ChangesPath 1.23 +16 -0 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- troubleshooting.pod 29 May 2003 04:04:39 - 1.22 +++ troubleshooting.pod 29 May 2003 23:54:04 - 1.23 @@ -670,6 +670,22 @@ =head1 OS Specific Notes +=head2 OpenBSD + +=head3 Issues Caused by httpd being Cchroot'ed + +Since OpenBSD 3.2, the Apache Chttpd(8) server has been +Cchroot(2)ed by default. + +A mod_perl enabled OpenBSD httpd will NOT work as is. A proper +Cchroot(2) environment must be setup for the default chrooted +behavior to work. The C-u option to httpd disables the chroot +behavior, and returns the httpd to the expanded unsecure behavior. +See the OpenBSD Chttpd(8) man page. + +For more information see Isection 10.16 of the OpenBSD FAQ. +Ihttp://www.openbsd.org/faq/faq10.html#httpdchroot. + =head2 Win FU =head3 Apache::DBI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2003/01/15 15:54:03 Modified:src/docs/1.0/guide troubleshooting.pod Log: add a solution for __floatdisf problem. solved by Paul Weiss [EMAIL PROTECTED] Revision ChangesPath 1.18 +35 -0 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- troubleshooting.pod 4 Dec 2002 02:57:07 - 1.17 +++ troubleshooting.pod 15 Jan 2003 23:54:03 - 1.18 @@ -149,6 +149,41 @@ This can also happen when you try to run a non-mod_perl Apache server using the configuration from a mod_perl server. +=head2 symbol __floatdisf: referenced symbol not found + +This problem is experienced by users on certain Solaris versions. When +the server is built with modules that use the C__floatdisf symbol it +can't be started. e.g.: + + Cannot load /usr/local/apache/libexec/libproxy.so into server: + ld.so.1: ../bin/httpd: fatal: relocation error: file + /usr/local/apache/libexec/libproxy.so: symbol __floatdisf: referenced + symbol not found + +The missing symbol is in Ilibgcc.a. Use + + % gcc -print-libgcc-file-name + +to see where that file is. Once found you have to relink the module +with that file. You can also look for it in the gcc tree, e.g. under +Igcc-3.2.1/gcc. + +First, configure and install Apache. Next, relink Imod_proxy.so or +Imod_negotiation.so, or whatever the module that reports the problem +with Ilibgcc.a. + + % cd apache_1.3.27/src/modules + % ld -G -o mod_proxy.so mod_proxy.lo /pathto/libgcc.a + +(adjust the I/pathto/ to point to the right file from the gcc output +stage.) + +You can now verify with Cnm that Imod_proxy.so includes that +symbol. + + + + =head2 RegistryLoader: Translation of uri [...] to filename failed RegistryLoader: Translation of uri [/home/httpd/perl/test.pl] to filename - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2002/11/25 23:39:57 Modified:src/docs/1.0/guide troubleshooting.pod Log: document the DynaLoader vs XSLoader segfaul problem as explained by Doug back in May. Revision ChangesPath 1.15 +29 -4 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- troubleshooting.pod 25 Oct 2002 13:10:13 - 1.14 +++ troubleshooting.pod 26 Nov 2002 07:39:57 - 1.15 @@ -31,14 +31,39 @@ =head2 SegFaults During Startup +Possible reasons and solutions: + +=over + +=item * + You have to build mod_perl with the same compiler as Perl was built with. Otherwise you may see segmentation faults and other weird things happen. -However if this is not the situation and you still experience -segmentation faults, please refer to the ISUPPORT file in the -mod_perl source distribution and post the trace from the core file as -explained there. +=item * + +This could be the XSLoader vs. DynaLoader problem, where the list of +dl_handles created by XSLoader is wiped out by DynaLoader. Try +adding: + + use DynaLoader (); + +to your Istartup.pl before any other module is loaded. + +This has been resolved in perl 5.8.0. For earlier versions of Perl you +need to comment out: + + [EMAIL PROTECTED] = (); # things we have loaded + [EMAIL PROTECTED] = (); # Modules we have loaded + +in IDynaLoader.pm. + +=back + +However if none of this cases applies and you still experience +segmentation faults, please report the problem using the Lfollowing +guidelines|guide::help/How_to_Report_Problems. =head2 libexec/libperl.so: open failed: No such file or directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2002/11/26 03:03:02 Modified:src/docs/1.0/guide troubleshooting.pod Log: add a new troubleshooting section: Problematic Perl Modules - add IPC::Open* Revision ChangesPath 1.16 +14 -0 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- troubleshooting.pod 26 Nov 2002 07:39:57 - 1.15 +++ troubleshooting.pod 26 Nov 2002 11:03:02 - 1.16 @@ -650,6 +650,20 @@ can succeed on the second load. Without that flag, the second load fails. +=head1 Problematic Perl Modules + +Here is the list of Perl Modules that are known to have problems under +mod_perl 1.0 and possible workarounds, solutions. + +=over + +=item CIPC::Open* + +use CIPC::Run instead. It provides the same functionality as the +CIPC::Open* family and more... and it works fine with mod_perl. + +=back + =head1 Maintainers Maintainer is the person(s) you should contact with updates, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/1.0/guide troubleshooting.pod
stas2002/06/27 09:05:21 Modified:src/docs/1.0/guide troubleshooting.pod Log: clarify the explanation Revision ChangesPath 1.12 +3 -3 modperl-docs/src/docs/1.0/guide/troubleshooting.pod Index: troubleshooting.pod === RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/troubleshooting.pod,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- troubleshooting.pod 12 May 2002 18:09:12 - 1.11 +++ troubleshooting.pod 27 Jun 2002 16:05:21 - 1.12 @@ -230,9 +230,9 @@ exit signal Segmentation fault (11) -The solution is not rely on PHP's built-in MySQL support, and instead -build it with your local MySQL support files, by adding -C--with-mysql=/path/to/mysql to your C./configure line. +The solution is to not rely on PHP's built-in MySQL support, and +instead build mod_php with your local MySQL support files by adding +C--with-mysql=/path/to/mysql during C./configure. =head2 foo ... at /dev/null line 0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
