On Thu, 13 Mar 2003, R. Peter Ejtel wrote:
> We had a bit of a glitch and had to re-start that system. It was very short
> and everything is fine now.
Something is definitely wrong on the batch system since the "glitch". I
have confirmed this with another OpenSRS reseller. He tested the perl
script, a PHP script and from the shell. Here are his results:
#1
I get the same thing:
Writing data to file: /home/cmv/osrs.test
Using OpenSRS server: batch.opensrs.net
HTTP header: CONTENT-TYPE: text/html; charset=iso-8859-1
HTTP header: DATE: Thu, 13 Mar 2003 22:27:44 GMT
HTTP header: SERVER: Apache/1.3.20 (Unix) mod_ssl/2.8.4 OpenSSL/0.9.6
mod_perl/1.26
HTTP header: CONNECTION: close
Can't get authentication cookie!
However, I've been using a PHP version of the script that does pretty
much the same thing, and it seems to have been working lately.
#2
Hrmm ... checking again, it looks like the PHP code isn't working
either. This is the HTML I get from OpenSRS after sending the first
login request:
HTTP/1.1 500 Internal Server Error
Date: Thu, 13 Mar 2003 22:51:41 GMT
Server: Apache/1.3.20 (Unix) mod_ssl/2.8.4 OpenSSL/0.9.6 mod_perl/1.26
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>500 Internal Server Error</TITLE>
</HEAD><BODY>
<H1>Internal Server Error</H1>
The server encountered an internal error or
misconfiguration and was unable to complete
your request.<P>
Please contact the server administrator,
[EMAIL PROTECTED] and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.<P>
More information about this error may be available
in the server error log.<P>
<HR>
<ADDRESS>Apache/1.3.20 Server at batch.opensrs.net Port 443</ADDRESS>
</BODY></HTML>
#3
>From a shell, I'm trying:
curl https://batch.opensrs.net/resellers/index
About 66% of the time it fails with that 500 message I posted before.
The other third of the time it seems to work, and spits out the right
HTML. So, I'd say it's something on their end.
