Ticket #1212 (closed defect: duplicate)

Opened 15 months ago

Last modified 3 days ago

fast cgi process Core Dumps Light goes 100% cpu

Reported by: anonymous Owned by: jan
Priority: normal Milestone:
Component: mod_fastcgi Version: 1.4.15
Severity: normal Keywords:
Cc: Blocked By:
Need User Feedback: Blocking:

Description

Major things in the Lighty conf:

server.modules        = ( "mod_status","mod_fastcgi","mod_accesslog" )
fastcgi.debug = 1
fastcgi.server = (
    "/" =>
      ((  
          "socket"   => "/tmp/dump.fcgi.socket",
          "bin-path" => "/tmp/core.pl",
          "bin-environment" => (
                          "PERL5LIB" => "/home/dmarkham/stable2/evdb/modules/",
                               ),
          "check-local" => "disable",
          "disable-time" => 1,
          "max-procs"   =>  1,
      ))
)

the Perl script

#!/usr/bin/perl
use strict;
use CGI::Fast qw(:standard);
$| =1;
## Request Loop
REQ:
while (my $q = new CGI::Fast) {
  alarm(5);
  local $SIG{ALRM} = sub {
                      print STDERR  "Time Out Looking up:\n";
                      print $q->header(-status=>'500');
                      print "You Have Been Dumped\n";
                      CORE::dump();
                    };

   sleep 10;
}

Attachments

lighty_fcgi_core_dump_strace.rtf (5.7 kB) - added by dmarkham 15 months ago.
strace

Change History

Changed 15 months ago by dmarkham

strace

Changed 15 months ago by dmarkham

This technique works just fine in 1.4.13..

Changed 10 months ago by Olaf van der Spek

  • pending set

How about 1.4.18?

This might be fixed due to http://trac.lighttpd.net/trac/ticket/1245

Changed 10 months ago by dmarkham@…

yes! in 1.4.18 it looks good...

Thats a lot I'll start the migration.

-Dan

Changed 4 days ago by stbuehler

  • status changed from new to closed
  • resolution set to duplicate

Changed 3 days ago by stbuehler

  • pending unset

Add/Change #1212 (fast cgi process Core Dumps Light goes 100% cpu)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.