IIS Malformed Header Error [revisit]

[Rick Draper]

Hi All,

There has been discussion from time to time on LT about an issue that a
few of us Windows users see on occasion.  We only have the issue on one
server and it had been unaffected for quite some time, but in the last
week we are seeing multiple instances of the could no communicate with
IIS / malformed header error.

LassoErrors  describes the event as "Failed to receive acknowledgment
from child. errno: 233 strerror: "No process is on the other end of the
pipe." site id: 1 site pid: 592", followed by "Restarted site process 1
default"  There is only one site on this W2K3/IIS6/LP8.5.5 box.

I have tried a number of things that have suggested, including changing
some registry entries associated with IIS (thanks, Douglas).  I have
also tried to isolate any code that might be triggering the issue, but
without success.   There was a suggestion that this may have been
session related, so I have tried varying the session settings (location
and clean-up time).... Again all without success.

This would be much easier if there were a pattern to it, but alas no
such luck.  If anyone has any other thoughts or suggestions, I would be
most pleased to give them a try.
 
Very best regards,
 
Rick

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

Just adding a little to this, I also am noting (as per previous threads
on this subject) that the Lasso Errors database shows multiple entries
for the highly informative "unknown exception caught" just ahead of the
"Lasso Error. Lasso Connector could not communicate with Lasso Service.
Server returned malformed header."


-----Original Message-----
From: Lasso Talk [mailto:lasso@...] On Behalf Of Rick
Draper
Sent: September 26, 2009 6:25 AM
To: Lasso Talk
Subject: IIS Malformed Header Error [revisit]

Hi All,

There has been discussion from time to time on LT about an issue that a
few of us Windows users see on occasion.  We only have the issue on one
server and it had been unaffected for quite some time, but in the last
week we are seeing multiple instances of the could no communicate with
IIS / malformed header error.

LassoErrors  describes the event as "Failed to receive acknowledgment
from child. errno: 233 strerror: "No process is on the other end of the
pipe." site id: 1 site pid: 592", followed by "Restarted site process 1
default"  There is only one site on this W2K3/IIS6/LP8.5.5 box.

I have tried a number of things that have suggested, including changing
some registry entries associated with IIS (thanks, Douglas).  I have
also tried to isolate any code that might be triggering the issue, but
without success.   There was a suggestion that this may have been
session related, so I have tried varying the session settings (location
and clean-up time).... Again all without success.

This would be much easier if there were a pattern to it, but alas no
such luck.  If anyone has any other thoughts or suggestions, I would be
most pleased to give them a try.
 
Very best regards,
 
Rick

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/





--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

 
Whoah!! The frequency of this has just reached a new high and is now a
major issue that I have to solve urgently.  

Is there any way to get more detail on the "unknown exception caught"??

-----

Just adding a little to this, I also am noting (as per previous threads
on this subject) that the Lasso Errors database shows multiple entries
for the highly informative "unknown exception caught" just ahead of the
"Lasso Error. Lasso Connector could not communicate with Lasso Service.
Server returned malformed header."

-----

Hi All,

There has been discussion from time to time on LT about an issue that a
few of us Windows users see on occasion.  We only have the issue on one
server and it had been unaffected for quite some time, but in the last
week we are seeing multiple instances of the could no communicate with
IIS / malformed header error.

LassoErrors  describes the event as "Failed to receive acknowledgment
from child. errno: 233 strerror: "No process is on the other end of the
pipe." site id: 1 site pid: 592", followed by "Restarted site process 1
default"  There is only one site on this W2K3/IIS6/LP8.5.5 box.

I have tried a number of things that have suggested, including changing
some registry entries associated with IIS (thanks, Douglas).  I have
also tried to isolate any code that might be triggering the issue, but
without success.   There was a suggestion that this may have been
session related, so I have tried varying the session settings (location
and clean-up time).... Again all without success.

This would be much easier if there were a pattern to it, but alas no
such luck.  If anyone has any other thoughts or suggestions, I would be
most pleased to give them a try.
 
Very best regards,
 
Rick


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[JP-14]

Is there a specific page being called around or just before the  
errors?  Can you determine which page is causing the error?

jp



--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[JP-14]

> Googling on this ....found a few hits ...one submitted by Rick last  
> year
>
Response to Rick's post last year:

> A couple weeks ago I was getting this error and it turned out to be  
> global
> variables I started using within an include on our intranet.
>
> The global variables caused threading issues (per Bil Cory's  
> description). I
> used another method and have not had the Lasso error since.
>
> (from http://www.listsearch.com/Lasso/Thread/index.lasso?21591#243529)
>
> Could it be a memory leak in IIS?

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Marc Vos-3]

We had this issue with nested ODBC inlines - I think this was resolved  
with 8.5. And I still see them sometimes after a day querying via  
ODBC / MySql every two minutes.

Lasso 8.5.6 on Wind2003 server

- -
Marc

Sent from my iPhone

On 26 sep 2009, at 15:27, Rick Draper <Rick.Draper@...> wrote:

>
> Whoah!! The frequency of this has just reached a new high and is now a
> major issue that I have to solve urgently.
>
> Is there any way to get more detail on the "unknown exception  
> caught"??
>
> -----
>
> Just adding a little to this, I also am noting (as per previous  
> threads
> on this subject) that the Lasso Errors database shows multiple entries
> for the highly informative "unknown exception caught" just ahead of  
> the
> "Lasso Error. Lasso Connector could not communicate with Lasso  
> Service.
> Server returned malformed header."
>
> -----
>
> Hi All,
>
> There has been discussion from time to time on LT about an issue  
> that a
> few of us Windows users see on occasion.  We only have the issue on  
> one
> server and it had been unaffected for quite some time, but in the last
> week we are seeing multiple instances of the could no communicate with
> IIS / malformed header error.
>
> LassoErrors  describes the event as "Failed to receive acknowledgment
> from child. errno: 233 strerror: "No process is on the other end of  
> the
> pipe." site id: 1 site pid: 592", followed by "Restarted site  
> process 1
> default"  There is only one site on this W2K3/IIS6/LP8.5.5 box.
>
> I have tried a number of things that have suggested, including  
> changing
> some registry entries associated with IIS (thanks, Douglas).  I have
> also tried to isolate any code that might be triggering the issue, but
> without success.   There was a suggestion that this may have been
> session related, so I have tried varying the session settings  
> (location
> and clean-up time).... Again all without success.
>
> This would be much easier if there were a pattern to it, but alas no
> such luck.  If anyone has any other thoughts or suggestions, I would  
> be
> most pleased to give them a try.
>
> Very best regards,
>
> Rick
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[bilcorry]

Rick Draper wrote on 9/26/2009 5:24 AM:
> LassoErrors  describes the event as "Failed to receive acknowledgment
> from child. errno: 233 strerror: "No process is on the other end of the
> pipe." site id: 1 site pid: 592", followed by "Restarted site process 1
> default"  There is only one site on this W2K3/IIS6/LP8.5.5 box.

IIS communicates with the Lasso Server via the Lasso Connector.  The error above just means that the Lasso Connector couldn't communicate with the Lasso Server, either because the Lasso Server crashed, was shut down/restarted, etc.  IOW, it's a dead-end error that doesn't tell you much.


Rick Draper wrote on 9/26/2009 5:42 AM:
> Just adding a little to this, I also am noting (as per previous threads
> on this subject) that the Lasso Errors database shows multiple entries
> for the highly informative "unknown exception caught" just ahead of the
> "Lasso Error. Lasso Connector could not communicate with Lasso Service.
> Server returned malformed header."

This is probably the error that is causing the issue.  I've seen that error mostly when using Java-based tags (LJAPI tags).

The easiest way to track it down is to add a define_atbegin that logs all requests to a file or db, then use it to see which request(s) happened when Lasso crashed.  Once you have a page or two that you suspect are causing the issue, you can add logging to just those pages to determine the code that is causing the issue.


- Bil


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

Thanks JP, Marc & Bil,

I appreciate the suggestions and am trying to isolate the issue.

Not being familiar with AtBegin handler, would it be feasible to simply
place a compound expression in LassoStartUp folder to log as much as I
can to a file for a period of time until I can isolate the likely calls
that are triggering this problem.  Would something like this be viable?

[

Define_AtBegin({Inline(-UserName='***',-Password='***';
File_Write(C://logs/tracker.txt, date->Format('%Y%m%d %H:%M') + ' | ' +
Client_IP + ' | ' + Client_Type  + ' | ' + Response_FilePath + ' | ' +
Lasso_CurrentAction);
/Inline;
})

]

Thanks again and very best regards,
 
 
Rick

-----Original Message-----
From: Lasso Talk [mailto:lasso@...] On Behalf Of Bil
Corry
Sent: September 26, 2009 6:45 PM
To: Lasso Talk
Subject: Re: IIS Malformed Header Error [revisit]

Rick Draper wrote on 9/26/2009 5:24 AM:
> LassoErrors  describes the event as "Failed to receive acknowledgment
> from child. errno: 233 strerror: "No process is on the other end of
> the pipe." site id: 1 site pid: 592", followed by "Restarted site
> process 1 default"  There is only one site on this W2K3/IIS6/LP8.5.5
box.

IIS communicates with the Lasso Server via the Lasso Connector.  The
error above just means that the Lasso Connector couldn't communicate
with the Lasso Server, either because the Lasso Server crashed, was shut
down/restarted, etc.  IOW, it's a dead-end error that doesn't tell you
much.


Rick Draper wrote on 9/26/2009 5:42 AM:
> Just adding a little to this, I also am noting (as per previous
> threads on this subject) that the Lasso Errors database shows multiple

> entries for the highly informative "unknown exception caught" just
> ahead of the "Lasso Error. Lasso Connector could not communicate with
Lasso Service.
> Server returned malformed header."

This is probably the error that is causing the issue.  I've seen that
error mostly when using Java-based tags (LJAPI tags).

The easiest way to track it down is to add a define_atbegin that logs
all requests to a file or db, then use it to see which request(s)
happened when Lasso crashed.  Once you have a page or two that you
suspect are causing the issue, you can add logging to just those pages
to determine the code that is causing the issue.


- Bil


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/





--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

After a bit of fiddling with syntax and all the typos in my previous
post, I have the following working and we will see what it points
towards...

[Define_AtBegin({Inline(-UserName='***',-Password='***');File_Write('C:/
/logs/tracker.txt', date->Format('%Y%m%d %H:%M') + ' | ' + Client_IP+ '
| ' + Server_Name + Response_FilePath + ' | Get: ' + Client_GetParams  +
' | Post: ' + Client_PostParams  + ' | ' + Client_Type  );/Inline;})]

... more to follow.

-----Original Message-----
From: Lasso Talk [mailto:lasso@...] On Behalf Of Rick
Draper
Sent: September 27, 2009 7:10 PM
To: Lasso Talk
Subject: Re: IIS Malformed Header Error [revisit]

Thanks JP, Marc & Bil,

I appreciate the suggestions and am trying to isolate the issue.

Not being familiar with AtBegin handler, would it be feasible to simply
place a compound expression in LassoStartUp folder to log as much as I
can to a file for a period of time until I can isolate the likely calls
that are triggering this problem.  Would something like this be viable?

[

Define_AtBegin({Inline(-UserName='***',-Password='***';
File_Write(C://logs/tracker.txt, date->Format('%Y%m%d %H:%M') + ' | ' +
Client_IP + ' | ' + Client_Type  + ' | ' + Response_FilePath + ' | ' +
Lasso_CurrentAction); /Inline;
})

]

Thanks again and very best regards,
 
 
Rick

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

 
Just a quick update on this - since adding the AtBegin logging, there
has not been one recurrence of the issue...

I will continue to monitor the situation, but somehow the AtBegin call
seems to be keeping the connector in check.

Very best regards,
 
Rick
 

-----Original Message-----
From: Lasso Talk [mailto:lasso@...] On Behalf Of Rick
Draper
Sent: Monday, 28 September 2009 10:08 AM
To: Lasso Talk
Subject: Re: IIS Malformed Header Error [revisit]

After a bit of fiddling with syntax and all the typos in my previous
post, I have the following working and we will see what it points
towards...

[Define_AtBegin({Inline(-UserName='***',-Password='***');File_Write('C:/
/logs/tracker.txt', date->Format('%Y%m%d %H:%M') + ' | ' + Client_IP+ '
| ' + Server_Name + Response_FilePath + ' | Get: ' + Client_GetParams  +
' | Post: ' + Client_PostParams  + ' | ' + Client_Type  );/Inline;})]

... more to follow.




--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Jeff Payanis]

Rick,

Did you just add this code as a file in the LassoStartup directory?  
We have been having this same issue with Lasso on IIS for a while and  
it is quite frustrating.  How long have you gone now without a crash  
since you added the AtBegin logging?

Anyone with further insight into how this code could possibly remedy  
this issue with the connector?

Jeff Payanis



On Oct 2, 2009, at 4:10 PM, Rick Draper wrote:

>
> Just a quick update on this - since adding the AtBegin logging, there
> has not been one recurrence of the issue...
>
> I will continue to monitor the situation, but somehow the AtBegin call
> seems to be keeping the connector in check.
>
> Very best regards,
>
> Rick
>
>
> -----Original Message-----
> From: Lasso Talk [mailto:lasso@...] On Behalf Of Rick
> Draper
> Sent: Monday, 28 September 2009 10:08 AM
> To: Lasso Talk
> Subject: Re: IIS Malformed Header Error [revisit]
>
> After a bit of fiddling with syntax and all the typos in my previous
> post, I have the following working and we will see what it points
> towards...
>
> [Define_AtBegin({Inline(-UserName='***',-
> Password='***');File_Write('C:/
> /logs/tracker.txt', date->Format('%Y%m%d %H:%M') + ' | ' + Client_IP
> + '
> | ' + Server_Name + Response_FilePath + ' | Get: ' +  
> Client_GetParams  +
> ' | Post: ' + Client_PostParams  + ' | ' + Client_Type  );/Inline;})]
>
> ... more to follow.
>
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

Hi Jeff,

Yes, with appropriate permissions in place, we just added this to the
LassoStartup directory.

As it is only the one server that was causing us issues, I have a
watchdog looking at the site every 15 mins and it has apparently not
missed a beat since the restart to enable the code - just on a week now.
 


Very best regards,
 
Rick

 

-----Original Message-----
From: Lasso Talk [mailto:lasso@...] On Behalf Of Jeff
Payanis
Sent: Tuesday, 6 October 2009 4:14 AM
To: Lasso Talk
Subject: Re: IIS Malformed Header Error [revisit]

Rick,

Did you just add this code as a file in the LassoStartup directory?  
We have been having this same issue with Lasso on IIS for a while and it
is quite frustrating.  How long have you gone now without a crash since
you added the AtBegin logging?

Anyone with further insight into how this code could possibly remedy
this issue with the connector?

Jeff Payanis



On Oct 2, 2009, at 4:10 PM, Rick Draper wrote:

>
> Just a quick update on this - since adding the AtBegin logging, there
> has not been one recurrence of the issue...
>
> I will continue to monitor the situation, but somehow the AtBegin call

> seems to be keeping the connector in check.
>
> Very best regards,
>
> Rick
>
>
> -----Original Message-----
> From: Lasso Talk [mailto:lasso@...] On Behalf Of Rick
> Draper
> Sent: Monday, 28 September 2009 10:08 AM
> To: Lasso Talk
> Subject: Re: IIS Malformed Header Error [revisit]
>
> After a bit of fiddling with syntax and all the typos in my previous
> post, I have the following working and we will see what it points
> towards...
>
> [Define_AtBegin({Inline(-UserName='***',-
> Password='***');File_Write('C:/
> /logs/tracker.txt', date->Format('%Y%m%d %H:%M') + ' | ' + Client_IP
> + '
> | ' + Server_Name + Response_FilePath + ' | Get: ' +
> Client_GetParams  +
> ' | Post: ' + Client_PostParams  + ' | ' + Client_Type  );/Inline;})]
>
> ... more to follow.
>
>
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/ 
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/





--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

 
Hi all,

Just a quick update on this.

As we had not seen any recurrence of the issue, I tried disabling the
atbegin code we had implemented and within 48 hours we saw three errors.
I enabled the logging again and it has been solid again ever since.

Not that we are seeing any serious speed issues with the logging in
place, the next experiment will be to remove the logging and try just
having some benign function called with atbegin and see if we have the
same stability.

Very best regards,

Rick

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[JP-14]

How about an atbegin that does nothing?

In other words, nothing --no statements between the {}

jp


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

 
> How about an atbegin that does nothing?

Will give that a try on the next service restart.

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

 
OK, things are getting interesting.

We actually had the first malformed header returned with the atbegin
logging on, and it seems that immediately prior to the error, one quite
old site was being absolutely hammered by a bot (MJ12bot/v1.3.0;
http://www.majestic12.co.uk/bot.php+ - all from 87.212.120.245)

The error was picked up by our watchdog which in turn triggered an
automatic Lasso restart, bringing into play the atbegin without any
functions called.  No further error since the restart, and based on
recent experience I fully expect to see at least one or two more.

The next clue will be in the old site that was getting hit when the
malformed header error was generated.  Thanks again to Bil for the
atbegin logging idea... on with the investigation.

Very best regards,

Rick

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Douglas Burchard]

On Oct 13, 2009, at 12:31 PM, Rick Draper wrote:

> OK, things are getting interesting.

I'm beginning to look on this thread as a mystery series I watch each  
week. Can't wait until the end of the season, but hoping it's not a  
cliff-hanger.  ;-)


--
Douglas Burchard, President
DouglasBurchard.com, Web Applications
15024 NE 66th Street
Redmond, WA  98052, USA

direct: [phone]
solutions@...
http://www.douglasburchard.com/




--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Rick Draper]

 
> I'm beginning to look on this thread as a mystery series I watch each
week. Can't wait until the end of the season, but hoping it's not a
cliff-hanger.  ;-)

I am beginning to suspect the butler in the server room with IE6
(candlestick).

Very best regards,
 
Rick

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Steve Piercy]

On 10/14/09 at 9:18 AM, douglas.burchard@...
(Douglas Burchard) pronounced:

>On Oct 13, 2009, at 12:31 PM, Rick Draper wrote:
>
>>OK, things are getting interesting.
>
>I'm beginning to look on this thread as a mystery series I
>watch each week. Can't wait until the end of the season, but
>hoping it's not a cliff-hanger.  ;-)

The island will never let you leave.

--steve

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<web@...>                  <http://www.StevePiercy.com/>


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/

[Jeff Payanis]

Yesterday, we implemented the same atBegin logging Rick is using.  It  
did not seem to resolve the IIS malformed header error, as we had  
another instance of it today.  However, the logging seems to point to  
a google bot being the source of the issue.  I am sure some of the  
code on the pages being requested could be optimized here and there,  
but I believe the root of the issue is the large influx of requests  
coming in simultaneously.  Obviously, it is a good thing for google to  
crawl public-facing sites, but I am wondering what would be the best  
solution for thwarting this issue.  I've read you can throttle the  
crawl rate (http://www.google.com/support/webmasters/bin/answer.py?hl=en-uk&answer=48620 
).  Seems it would be on a per site basis.  This could be a tedious  
task with a high number of sites on the server.  Plus, this really  
isn't feasible to do for every bot that might crawl our sites.

Any other suggestions?  Any way we could throttle crawl rates via a  
server setting? Or programmatically in an efficient manner?


Jeff Payanis




On Oct 13, 2009, at 3:31 PM, Rick Draper wrote:

>
> OK, things are getting interesting.
>
> We actually had the first malformed header returned with the atbegin
> logging on, and it seems that immediately prior to the error, one  
> quite
> old site was being absolutely hammered by a bot (MJ12bot/v1.3.0;
> http://www.majestic12.co.uk/bot.php+ - all from 87.212.120.245)
>
> The error was picked up by our watchdog which in turn triggered an
> automatic Lasso restart, bringing into play the atbegin without any
> functions called.  No further error since the restart, and based on
> recent experience I fully expect to see at least one or two more.
>
> The next clue will be in the old site that was getting hit when the
> malformed header error was generated.  Thanks again to Bil for the
> atbegin logging idea... on with the investigation.
>
> Very best regards,
>
> Rick
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/Lasso/Browse/
> Manage your subscription: http://www.ListSearch.com/Lasso/
>
>

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/Lasso/Browse/
Manage your subscription: http://www.ListSearch.com/Lasso/