PS Interestingly, the first successful execution of the script after we saw the problem is the first request from the next day (according to IIS website logs in which the times are currently one hour out due to daylight saving). There are around 700 failed requests between the problem first occurring and where it starts working again time so it is an odd coincidence.
Cheers, Mark > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Mark > Knoop > Sent: 05 September 2005 16:47 > To: [email protected] > Subject: INTERNAL ERROR: PerlParse did not exit clean!!!! > > > Hi > > This seems to be similar to the problem detailed by Justin in the 'error > after upgrading from activeperl 5.6 to 5.8 (using ISAPI& IIS)' > thread from a > few days ago but wasn't sure how to post to a thread that was > started before > I subscribed and also this is not linked to an upgrade so perhaps > merits its > own thread anyhow. Perhaps it could shed some more light on Justin's > problem. > > I am using v5.8.4 with IIS and ISAPI and every now and then we > see the same > problem of all scripts bombing out with the message > INTERNAL ERROR: PerlParse did not exit clean!!!! > being logged to PerlIS-Err.log > > We have loads of perl cgi scripts on the server and I am not 100% > sure which > script has caused the problem but on the last occurrence the first error > logged is from the following script: > > ################################################################## > ########## > ################## > > use strict; > use CGI qw/:standard/; > > #check ip > my $q = new CGI; > > my $remote_addr = $ENV{'REMOTE_ADDR'}; > > unless ( ($remote_addr eq 'xxx.xxx.xxx.xxx') or ## had to x these out for > security reasons > ($remote_addr =~ /xxx.xxx.xxx.xxx/) or > ($remote_addr =~ /xxx.xxx.xxx.xxx/) or > ($remote_addr eq 'xxx.xxx.xxx.xxx') or > ($remote_addr eq 'xxx.xxx.xxx.xxx') or > ($remote_addr eq 'xxx.xxx.xxx.xxx') or > ($remote_addr eq '127.0.0.1') ) { > print $q->header(-status=>'404 Page not found'); > exit; > } > > my $oa = $q->param('smsfrom'); > my $msg = $q->param('smsmsg'); > $msg =~ s/^[\s]+//; > $msg =~ s/[\n]+/ /g; > my $da = $q->param('smsto'); > my $id = $q->param('smsid'); > my $date = $q->param('smsdate'); > > my $bits = $q->param('bits'); > > my $network = $q->param('network'); > my $smsudh = $q->param('smsudh'); > my $smsc = $q->param('smsc'); > my $smsucs = $q->param('smsucs'); > > open (INSMS, ">> inboundsms.txt") or die ("Could not open > inboundsms.txt"); > print INSMS > "$oa\t$msg\t$da\t$id\t$date\t$bits\t$network\t$smsudh\t$smsc\t$smsucs\n"; > close INSMS; > > print $q->header(-status=>'200 Response OK'); # sloppy of me to > leave this > debug in - could this cause it? > > print "Received message<br>Originating address = $oa<br>Msg = > [$msg]<br>Short code = $da<br>SMSID = $id<br>Date = $date<br>extra info > $bits,$network,$smsudh,$smsc,$smsucs<br/>from $remote_addr"; > > exit; > > #################################################################### > > This script is called a few hundred times a day and we only see > the problem > once every few months. > > This script can sometimes be called quite frequently. > > The file inboundsms.txt is regularly moved by an external > process. Could it > be a file access problem? > > After it has happened then it seems all scripts on our webserver cause the > error message. This usually continues for some time or until we > restart the > server - last time it seemd to fix itself after about 14 hours. > We are using > DBI::ODBC with sql server 2000 in our other scripts but nothing > complicated. > > Any help on this would be much appreciated. > > Kind regards > Mark > > > _______________________________________________ > ActivePerl mailing list > [email protected] > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > > _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
