Jump to content

Anyone seen these 500 (server fail) errors lately?

Jenni Darkwatch

By Jenni Darkwatch,
in LSL Scripting

 Share
You are about to reply to a thread that has been inactive for 4001 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Jenni Darkwatch

Jenni Darkwatch

Posted
Posted

In the last week or two I see some rather odd messages like the one below. The script doesn't get throttled, but this error gets tossed. It's not entirely reproducable as far as I can tell. It almost looks like a Squid config error to me.

 

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>ERROR: The requested URL could not be retrieved</title>
    <style type="text/css">
      <!--   %l  body :lang(fa) { direction: rtl; font-size: 100%; font-family: Tahoma, Roya, sans-serif; float: right; } :lang(he) { direction: rtl; float: right; }  -->
    </style>
  </head>
  <body>
    <div id="titles">
      <h1>ERROR</h1>
      <h2>The requested URL could not be retrieved</h2>
    </div>
    <hr>
    <div id="content">
      <p>The following error was encountered while trying to retrieve the URL: <a href="http://xxx.yyy.zzz/aaa/bbb.php">http://xxx.yyy.zzz/aaa/bbb.php</a></p>
      <blockquote id="error"> <p><b>Socket Failure</b></p> </blockquote>
      <p id="sysmsg">The system returned: <i>(98) Address already in use</i></p>
      <p>Squid is unable to create a TCP socket, presumably due to excessive load. Please retry your request.</p>
      <p>

 

Link to comment
Share on other sites
Ron Khondji

Ron Khondji

Posted
Posted

Might be because of server changes since april 30.

This is from the release notes:

Keepalive connections for some HTTP-based servicesThe behavioral change for HTTP connections marks the beginning of support for 
persistent (keepalive) connections. 
Services transiting the capabilities router, at ports 12043 and 12046, may honor a request for 
keepalives and keep a connection open after request completion. These services may include 
such activities as texture and  mesh fetching, event delivery to viewer, HTTP-In for LSL scripts, 
asset uploads and inventory operations. 
Benefits from keepalives include immediate and future throughput increases and less 
TCP connection churn (which often disrupts consumer-grade networking equipment).
The exact set of services that will see this is expected to change over time.

 I believe I read somewhere that users might see more 500 errors resulting from those changes.

Link to comment
Share on other sites
You are about to reply to a thread that has been inactive for 4001 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...