Custom Query (121 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 121)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1 fixed configure a trac instance for GMOC operational monitoring use chaos@bbn.com chaos@bbn.com
Description

Create and configure a Trac instance at http://groups.geni.net/gmoc/ for use in discussing design and feature requests and bug reports.

#6 fixed add CNAMEs gmoc.geni.net and gmoc-staging.geni.net to point to GMOC databases somebody chaos@bbn.com
Description
  • Create DNS CNAMEs gmoc.geni.net and gmoc-staging.geni.net, pointing to gmoc-db.grnoc.iu.edu and gmoc-db2.grnoc.iu.edu, respectively
  • Configure apache on gmoc-db and gmoc-db2 to respond to those names
#7 fixed debug intermittent 500 errors in report_data_to_gmoc somebody chaos@bbn.com
Description

At GPO, we receive approximately half a dozen reporting errors per day of the form:

From: root@gpolab.bbn.com (Cron Daemon)
Date: Sat, 21 Jul 2012 14:01:18 -0400 (EDT)
To: ganglia@gpolab.bbn.com
Subject: [gpo-ops] Cron <ganglia@chasel> /usr/bin/report_data_to_gmoc           

500 Internal Server Error: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">   
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
 root@localhost and inform them of the time the error occurred,                 
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache/2.2.3 (Red Hat) Server at <a href="mailto:root@localhost">gmoc-db.grnoc.iu.edu</a> Port 443</address>
</body></html>
 at /usr/bin/report_relations line 34
        main::__ANON__('500 Internal Server Error: <!DOCTYPE HTML PUBLIC "-//IETF//DT...') called at /usr/bin/report_relations line 316
Execution of /usr/bin/report_relations failed!

These errors always seem to be received during the reporting run which is on the hour (i.e. the datestamp on the error is always NN:01:MM for some hour NN and second MM values). Diagnose and fix these intermittent failures.

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.