Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

2008-10-30 Thread Ethan Mallove 
On Thu, Oct/30/2008 01:46:58PM, Josh Hursey wrote:
> This is probably me. I haven't had a chance to do anything about it yet. 
> Hopefully tomorrow.
>
> I'm running the release branch (I believe), does this option exist for the 
> release branch yet?

It does not.

-Ethan

>
> -- Josh
>
> On Oct 30, 2008, at 11:36 AM, Ethan Mallove wrote:
>
>> On Wed, Oct/29/2008 09:15:37AM, Ethan Mallove wrote:
>>> On Tue, Oct/28/2008 06:17:12PM, Jeff Squyres wrote:
 Should we set a default value of report_after_n_results to, say, 50 or 
 100?

>>>
>>> We should.
>>>
>>> -Ethan
>>>
>>>
 On Oct 28, 2008, at 6:15 PM, Jeff Squyres wrote:

> That host is in one of IU's clusters (odin).
>
> Tim/Josh -- this is you guys...
>>
>> Got another submit.php failure alert last night from IU. If
>> the IU tests are running on the MTT trunk, an "svn up" on it
>> should eliminate the issue. (report_after_n_results now
>> defaults to 100 - see r1239.)
>>
>> -Ethan
>>
>>
>
>
> On Oct 28, 2008, at 3:45 PM, Ethan Mallove wrote:
>
>> Folks,
>>
>> I got an alert from the http-log-checker.pl script. Somebody appears 
>> to
>> have
>> lost some MTT results. (Possibly due to an oversized database 
>> submission
>> to
>> submit/index.php?) There's an open ticket for this (see
>> https://svn.open-mpi.org/trac/mtt/ticket/375).  Currently there exists 
>> a
>> simple
>> workaround for this problem. Put the below line in the problematic 
>> "Test
>> run"
>> section(s). This will prevent oversided submissions by directing MTT 
>> to
>> submit
>> the results in batches of 50 results instead of an entire section at a
>> time,
>> which can reach 400+ for an Intel test run section.
>>
>>  report_after_n_results = 50
>>
>> It's hard to know whose errors are in the HTTP error log with only the 
>> IP
>> address. If you want to verify they are or are not yours, visit a 
>> bogus
>> URL off
>> open-mpi.org, e.g., www.open-mpi.org/what-is-foobars-ip-address, and 
>> ping
>> me
>> about it. This will write your IP address to the log file, and then 
>> this
>> can be
>> matched with the IP addr against the submit.php errors.
>>
>> -Ethan
>>
>>
>> - Forwarded message from Ethan Mallove  -
>>
>> From: Ethan Mallove 
>> Date: Tue, 28 Oct 2008 08:00:41 -0400
>> To: ethan.mall...@sun.com, http-log-checker.pl-no-re...@open-mpi.org
>> Subject: [Alert] Found server-side submit error messages
>> Original-recipient: rfc822;ethan.mall...@sun.com
>>
>> This email was automatically sent by http-log-checker.pl. You have
>> received
>> it because some error messages were found in the HTTP(S) logs that
>> might indicate some MTT results were not successfully submitted by the
>> server-side PHP submit script (even if the MTT client has not
>> indicated a submission error).
>>
>> ###
>> #
>> # The below log messages matched "gz.*submit/index.php" in
>> # /var/log/httpd/www.open-mpi.org/ssl_error_log
>> #
>> ###
>>
>> [client 129.79.240.114] PHP Warning:  gzeof(): supplied argument is 
>> not a
>> valid stream resource in
>> /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
>> on
>> line 1923
>> [client 129.79.240.114] PHP Warning:  gzgets(): supplied argument is 
>> not
>> a valid stream resource in
>> /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
>> on
>> line 1924
>> ...
>> 
>>
>>
>>
>>
>> - End forwarded message -
>> ___
>> mtt-users mailing list
>> mtt-us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>
>
> -- 
> Jeff Squyres
> Cisco Systems
>
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users


 -- 
 Jeff Squyres
 Cisco Systems

 ___
 mtt-users mailing list
 mtt-us...@open-mpi.org
 http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>> ___
>>> mtt-users mailing list
>>> mtt-us...@open-mpi.org
>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>

Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

2008-10-30 Thread Josh Hursey 
This is probably me. I haven't had a chance to do anything about it  
yet. Hopefully tomorrow.


I'm running the release branch (I believe), does this option exist for  
the release branch yet?


-- Josh

On Oct 30, 2008, at 11:36 AM, Ethan Mallove wrote:


On Wed, Oct/29/2008 09:15:37AM, Ethan Mallove wrote:

On Tue, Oct/28/2008 06:17:12PM, Jeff Squyres wrote:
Should we set a default value of report_after_n_results to, say,  
50 or 100?




We should.

-Ethan



On Oct 28, 2008, at 6:15 PM, Jeff Squyres wrote:


That host is in one of IU's clusters (odin).

Tim/Josh -- this is you guys...


Got another submit.php failure alert last night from IU. If
the IU tests are running on the MTT trunk, an "svn up" on it
should eliminate the issue. (report_after_n_results now
defaults to 100 - see r1239.)

-Ethan





On Oct 28, 2008, at 3:45 PM, Ethan Mallove wrote:


Folks,

I got an alert from the http-log-checker.pl script. Somebody  
appears to

have
lost some MTT results. (Possibly due to an oversized database  
submission

to
submit/index.php?) There's an open ticket for this (see
https://svn.open-mpi.org/trac/mtt/ticket/375).  Currently there  
exists a

simple
workaround for this problem. Put the below line in the  
problematic "Test

run"
section(s). This will prevent oversided submissions by directing  
MTT to

submit
the results in batches of 50 results instead of an entire  
section at a

time,
which can reach 400+ for an Intel test run section.

 report_after_n_results = 50

It's hard to know whose errors are in the HTTP error log with  
only the IP
address. If you want to verify they are or are not yours, visit  
a bogus

URL off
open-mpi.org, e.g., www.open-mpi.org/what-is-foobars-ip-address,  
and ping

me
about it. This will write your IP address to the log file, and  
then this

can be
matched with the IP addr against the submit.php errors.

-Ethan


- Forwarded message from Ethan Mallove   
-


From: Ethan Mallove 
Date: Tue, 28 Oct 2008 08:00:41 -0400
To: ethan.mall...@sun.com, http-log-checker.pl-no-re...@open-mpi.org
Subject: [Alert] Found server-side submit error messages
Original-recipient: rfc822;ethan.mall...@sun.com

This email was automatically sent by http-log-checker.pl. You have
received
it because some error messages were found in the HTTP(S) logs that
might indicate some MTT results were not successfully submitted  
by the

server-side PHP submit script (even if the MTT client has not
indicated a submission error).

###
#
# The below log messages matched "gz.*submit/index.php" in
# /var/log/httpd/www.open-mpi.org/ssl_error_log
#
###

[client 129.79.240.114] PHP Warning:  gzeof(): supplied argument  
is not a

valid stream resource in
/nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
 on

line 1923
[client 129.79.240.114] PHP Warning:  gzgets(): supplied  
argument is not

a valid stream resource in
/nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
 on

line 1924
...





- End forwarded message -
___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

2008-10-30 Thread Ethan Mallove 
On Wed, Oct/29/2008 09:15:37AM, Ethan Mallove wrote:
> On Tue, Oct/28/2008 06:17:12PM, Jeff Squyres wrote:
> > Should we set a default value of report_after_n_results to, say, 50 or 100?
> >
> 
> We should.
> 
> -Ethan
> 
> 
> > On Oct 28, 2008, at 6:15 PM, Jeff Squyres wrote:
> >
> >> That host is in one of IU's clusters (odin).
> >>
> >> Tim/Josh -- this is you guys...

Got another submit.php failure alert last night from IU. If
the IU tests are running on the MTT trunk, an "svn up" on it
should eliminate the issue. (report_after_n_results now
defaults to 100 - see r1239.)

-Ethan


> >>
> >>
> >> On Oct 28, 2008, at 3:45 PM, Ethan Mallove wrote:
> >>
> >>> Folks,
> >>>
> >>> I got an alert from the http-log-checker.pl script. Somebody appears to 
> >>> have
> >>> lost some MTT results. (Possibly due to an oversized database submission 
> >>> to
> >>> submit/index.php?) There's an open ticket for this (see
> >>> https://svn.open-mpi.org/trac/mtt/ticket/375).  Currently there exists a 
> >>> simple
> >>> workaround for this problem. Put the below line in the problematic "Test 
> >>> run"
> >>> section(s). This will prevent oversided submissions by directing MTT to 
> >>> submit
> >>> the results in batches of 50 results instead of an entire section at a 
> >>> time,
> >>> which can reach 400+ for an Intel test run section.
> >>>
> >>>   report_after_n_results = 50
> >>>
> >>> It's hard to know whose errors are in the HTTP error log with only the IP
> >>> address. If you want to verify they are or are not yours, visit a bogus 
> >>> URL off
> >>> open-mpi.org, e.g., www.open-mpi.org/what-is-foobars-ip-address, and ping 
> >>> me
> >>> about it. This will write your IP address to the log file, and then this 
> >>> can be
> >>> matched with the IP addr against the submit.php errors.
> >>>
> >>> -Ethan
> >>>
> >>>
> >>> - Forwarded message from Ethan Mallove  -
> >>>
> >>> From: Ethan Mallove 
> >>> Date: Tue, 28 Oct 2008 08:00:41 -0400
> >>> To: ethan.mall...@sun.com, http-log-checker.pl-no-re...@open-mpi.org
> >>> Subject: [Alert] Found server-side submit error messages
> >>> Original-recipient: rfc822;ethan.mall...@sun.com
> >>>
> >>> This email was automatically sent by http-log-checker.pl. You have 
> >>> received
> >>> it because some error messages were found in the HTTP(S) logs that
> >>> might indicate some MTT results were not successfully submitted by the
> >>> server-side PHP submit script (even if the MTT client has not
> >>> indicated a submission error).
> >>>
> >>> ###
> >>> #
> >>> # The below log messages matched "gz.*submit/index.php" in
> >>> # /var/log/httpd/www.open-mpi.org/ssl_error_log
> >>> #
> >>> ###
> >>>
> >>> [client 129.79.240.114] PHP Warning:  gzeof(): supplied argument is not a 
> >>> valid stream resource in 
> >>> /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php on 
> >>> line 1923
> >>> [client 129.79.240.114] PHP Warning:  gzgets(): supplied argument is not 
> >>> a valid stream resource in 
> >>> /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php on 
> >>> line 1924
> >>> ...
> >>> 
> >>>
> >>>
> >>>
> >>>
> >>> - End forwarded message -
> >>> ___
> >>> mtt-users mailing list
> >>> mtt-us...@open-mpi.org
> >>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> >>
> >>
> >> -- 
> >> Jeff Squyres
> >> Cisco Systems
> >>
> >> ___
> >> mtt-users mailing list
> >> mtt-us...@open-mpi.org
> >> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> >
> >
> > -- 
> > Jeff Squyres
> > Cisco Systems
> >
> > ___
> > mtt-users mailing list
> > mtt-us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users

Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

2008-10-28 Thread Tim Mattox 
I ran into this a week ago on sif, so I added report_after_n_results = 100
for our regular nightly tests on sif, odin and bigred.  Josh, could this be a
problem with any of the tests you run?

On Tue, Oct 28, 2008 at 6:15 PM, Jeff Squyres  wrote:
> That host is in one of IU's clusters (odin).
>
> Tim/Josh -- this is you guys...
>
>
> On Oct 28, 2008, at 3:45 PM, Ethan Mallove wrote:
>
>> Folks,
>>
>> I got an alert from the http-log-checker.pl script. Somebody appears to
>> have
>> lost some MTT results. (Possibly due to an oversized database submission
>> to
>> submit/index.php?) There's an open ticket for this (see
>> https://svn.open-mpi.org/trac/mtt/ticket/375).  Currently there exists a
>> simple
>> workaround for this problem. Put the below line in the problematic "Test
>> run"
>> section(s). This will prevent oversided submissions by directing MTT to
>> submit
>> the results in batches of 50 results instead of an entire section at a
>> time,
>> which can reach 400+ for an Intel test run section.
>>
>>   report_after_n_results = 50
>>
>> It's hard to know whose errors are in the HTTP error log with only the IP
>> address. If you want to verify they are or are not yours, visit a bogus
>> URL off
>> open-mpi.org, e.g., www.open-mpi.org/what-is-foobars-ip-address, and ping
>> me
>> about it. This will write your IP address to the log file, and then this
>> can be
>> matched with the IP addr against the submit.php errors.
>>
>> -Ethan
>>
>>
>> - Forwarded message from Ethan Mallove  -
>>
>> From: Ethan Mallove 
>> Date: Tue, 28 Oct 2008 08:00:41 -0400
>> To: ethan.mall...@sun.com, http-log-checker.pl-no-re...@open-mpi.org
>> Subject: [Alert] Found server-side submit error messages
>> Original-recipient: rfc822;ethan.mall...@sun.com
>>
>> This email was automatically sent by http-log-checker.pl. You have
>> received
>> it because some error messages were found in the HTTP(S) logs that
>> might indicate some MTT results were not successfully submitted by the
>> server-side PHP submit script (even if the MTT client has not
>> indicated a submission error).
>>
>> ###
>> #
>> # The below log messages matched "gz.*submit/index.php" in
>> # /var/log/httpd/www.open-mpi.org/ssl_error_log
>> #
>> ###
>>
>> [client 129.79.240.114] PHP Warning:  gzeof(): supplied argument is not a
>> valid stream resource in
>> /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php on line
>> 1923
>> [client 129.79.240.114] PHP Warning:  gzgets(): supplied argument is not a
>> valid stream resource in
>> /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php on line
>> 1924
>> ...
>> 
>>
>>
>>
>>
>> - End forwarded message -
>> ___
>> mtt-users mailing list
>> mtt-us...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>
>
> --
> Jeff Squyres
> Cisco Systems
>
> ___
> mtt-users mailing list
> mtt-us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>



-- 
Tim Mattox, Ph.D. - http://homepage.mac.com/tmattox/
 tmat...@gmail.com || timat...@open-mpi.org
I'm a bright... http://www.the-brights.net/

Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

2008-10-28 Thread Jeff Squyres 
Should we set a default value of report_after_n_results to, say, 50 or  
100?


On Oct 28, 2008, at 6:15 PM, Jeff Squyres wrote:


That host is in one of IU's clusters (odin).

Tim/Josh -- this is you guys...


On Oct 28, 2008, at 3:45 PM, Ethan Mallove wrote:


Folks,

I got an alert from the http-log-checker.pl script. Somebody  
appears to have
lost some MTT results. (Possibly due to an oversized database  
submission to

submit/index.php?) There's an open ticket for this (see
https://svn.open-mpi.org/trac/mtt/ticket/375).  Currently there  
exists a simple
workaround for this problem. Put the below line in the problematic  
"Test run"
section(s). This will prevent oversided submissions by directing  
MTT to submit
the results in batches of 50 results instead of an entire section  
at a time,

which can reach 400+ for an Intel test run section.

  report_after_n_results = 50

It's hard to know whose errors are in the HTTP error log with only  
the IP
address. If you want to verify they are or are not yours, visit a  
bogus URL off
open-mpi.org, e.g., www.open-mpi.org/what-is-foobars-ip-address,  
and ping me
about it. This will write your IP address to the log file, and then  
this can be

matched with the IP addr against the submit.php errors.

-Ethan


- Forwarded message from Ethan Mallove   
-


From: Ethan Mallove 
Date: Tue, 28 Oct 2008 08:00:41 -0400
To: ethan.mall...@sun.com, http-log-checker.pl-no-re...@open-mpi.org
Subject: [Alert] Found server-side submit error messages
Original-recipient: rfc822;ethan.mall...@sun.com

This email was automatically sent by http-log-checker.pl. You have  
received

it because some error messages were found in the HTTP(S) logs that
might indicate some MTT results were not successfully submitted by  
the

server-side PHP submit script (even if the MTT client has not
indicated a submission error).

###
#
# The below log messages matched "gz.*submit/index.php" in
# /var/log/httpd/www.open-mpi.org/ssl_error_log
#
###

[client 129.79.240.114] PHP Warning:  gzeof(): supplied argument is  
not a valid stream resource in /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
 on line 1923
[client 129.79.240.114] PHP Warning:  gzgets(): supplied argument  
is not a valid stream resource in /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
 on line 1924

...





- End forwarded message -
___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

2008-10-28 Thread Jeff Squyres 

That host is in one of IU's clusters (odin).

Tim/Josh -- this is you guys...


On Oct 28, 2008, at 3:45 PM, Ethan Mallove wrote:


Folks,

I got an alert from the http-log-checker.pl script. Somebody appears  
to have
lost some MTT results. (Possibly due to an oversized database  
submission to

submit/index.php?) There's an open ticket for this (see
https://svn.open-mpi.org/trac/mtt/ticket/375).  Currently there  
exists a simple
workaround for this problem. Put the below line in the problematic  
"Test run"
section(s). This will prevent oversided submissions by directing MTT  
to submit
the results in batches of 50 results instead of an entire section at  
a time,

which can reach 400+ for an Intel test run section.

   report_after_n_results = 50

It's hard to know whose errors are in the HTTP error log with only  
the IP
address. If you want to verify they are or are not yours, visit a  
bogus URL off
open-mpi.org, e.g., www.open-mpi.org/what-is-foobars-ip-address, and  
ping me
about it. This will write your IP address to the log file, and then  
this can be

matched with the IP addr against the submit.php errors.

-Ethan


- Forwarded message from Ethan Mallove  -

From: Ethan Mallove 
Date: Tue, 28 Oct 2008 08:00:41 -0400
To: ethan.mall...@sun.com, http-log-checker.pl-no-re...@open-mpi.org
Subject: [Alert] Found server-side submit error messages
Original-recipient: rfc822;ethan.mall...@sun.com

This email was automatically sent by http-log-checker.pl. You have  
received

it because some error messages were found in the HTTP(S) logs that
might indicate some MTT results were not successfully submitted by the
server-side PHP submit script (even if the MTT client has not
indicated a submission error).

###
#
# The below log messages matched "gz.*submit/index.php" in
# /var/log/httpd/www.open-mpi.org/ssl_error_log
#
###

[client 129.79.240.114] PHP Warning:  gzeof(): supplied argument is  
not a valid stream resource in /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
 on line 1923
[client 129.79.240.114] PHP Warning:  gzgets(): supplied argument is  
not a valid stream resource in /nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php 
 on line 1924

...





- End forwarded message -
___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

[MTT users] Fwd: [Alert] Found server-side submit error messages

2008-10-28 Thread Ethan Mallove 
Folks,

I got an alert from the http-log-checker.pl script. Somebody appears to have
lost some MTT results. (Possibly due to an oversized database submission to
submit/index.php?) There's an open ticket for this (see
https://svn.open-mpi.org/trac/mtt/ticket/375).  Currently there exists a simple
workaround for this problem. Put the below line in the problematic "Test run"
section(s). This will prevent oversided submissions by directing MTT to submit
the results in batches of 50 results instead of an entire section at a time,
which can reach 400+ for an Intel test run section.

report_after_n_results = 50

It's hard to know whose errors are in the HTTP error log with only the IP
address. If you want to verify they are or are not yours, visit a bogus URL off
open-mpi.org, e.g., www.open-mpi.org/what-is-foobars-ip-address, and ping me
about it. This will write your IP address to the log file, and then this can be
matched with the IP addr against the submit.php errors.

-Ethan


- Forwarded message from Ethan Mallove  -

From: Ethan Mallove 
List-Post: mtt-users@lists.open-mpi.org
Date: Tue, 28 Oct 2008 08:00:41 -0400
To: ethan.mall...@sun.com, http-log-checker.pl-no-re...@open-mpi.org
Subject: [Alert] Found server-side submit error messages
Original-recipient: rfc822;ethan.mall...@sun.com

This email was automatically sent by http-log-checker.pl. You have received
it because some error messages were found in the HTTP(S) logs that
might indicate some MTT results were not successfully submitted by the
server-side PHP submit script (even if the MTT client has not
indicated a submission error).

###
#
# The below log messages matched "gz.*submit/index.php" in 
# /var/log/httpd/www.open-mpi.org/ssl_error_log
#
###

[client 129.79.240.114] PHP Warning:  gzeof(): supplied argument is not a valid 
stream resource in 
/nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php on line 
1923
[client 129.79.240.114] PHP Warning:  gzgets(): supplied argument is not a 
valid stream resource in 
/nfs/rontok/xraid/data/osl/www/www.open-mpi.org/mtt/submit/index.php on line 
1924
...





- End forwarded message -