Opened 12 years ago

Closed 12 years ago

#139 closed (fixed)

500 internal server error on submission of measurement data to gmoc-db (but not to gmoc-db2)

Reported by: chaos@bbn.com Owned by: somebody
Priority: major Milestone: GEC15 demo
Component: Database Version:
Keywords: Cc:
Dependencies:

Description

When i submit the following measurement data to gmoc-db as user ExoGENI-BBN: 

<?xml version="1.0" ?>
<timeseries_data originator="someone" time="1350583398" version="0.1">
        <type_info name="node_disk">
                <column_names>
                        disk_part_max_used
                </column_names>
                <column_units>
                        percent
                </column_units>
        </type_info>
        <type_info name="node_cpu">
                <column_names>
                        cpu_idle
                </column_names>
                <column_units>
                        percent
                </column_units>
        </type_info>
        <node_info name="bbn-hn.exogeni.net:11443">
                <location>
                        urn:publicid:IDN+gmoc.geni.net+pop+gpolab
                </location>
                <tags/>
        </node_info>
        <data_group end="1349759970" heartbeat="60" interval_type="open_closed" name="bbn-hn.exogeni.net:11443-node_cpu-aggregate_bbn-hn.exogeni.net:11443" start="1349759970" step="15">
                <column_names>
                        cpu_idle
                </column_names>
                <type>
                        node_cpu
                </type>
                <node_name>
                        bbn-hn.exogeni.net:11443
                </node_name>
                <tags>
                        aggregate:bbn-hn.exogeni.net:11443
                </tags>
                <data>
                        1349759955,;
1349759970,85.294;

                </data>
        </data_group>
        <data_group end="1349759970" heartbeat="60" interval_type="open_closed" name="bbn-hn.exogeni.net:11443-node_disk-aggregate_bbn-hn.exogeni.net:11443" start="1349759970" step="15">
                <column_names>
                        disk_part_max_used
                </column_names>
                <type>
                        node_disk
                </type>
                <node_name>
                        bbn-hn.exogeni.net:11443
                </node_name>
                <tags>
                        aggregate:bbn-hn.exogeni.net:11443
                </tags>
                <data>
                        1349759955,;
1349759970,64.3752165412;

                </data>
        </data_group>
</timeseries_data>

i get: 

<!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>

Weirdly, when i submit the following very similar data: 

<?xml version="1.0" ?>
<timeseries_data originator="someone" time="1350583586" version="0.1">
        <type_info name="node_disk">
                <column_names>
                        disk_part_max_used
                </column_names>
                <column_units>
                        percent
                </column_units>
        </type_info>
        <type_info name="node_cpu">
                <column_names>
                        cpu_idle
                </column_names>
                <column_units>
                        percent
                </column_units>
        </type_info>
        <node_info name="bbn-hn.exogeni.net:11443">
                <location>
                        urn:publicid:IDN+gmoc.geni.net+pop+gpolab
                </location>
                <tags/>
        </node_info>
        <data_group end="1349759970" heartbeat="60" interval_type="open_closed" name="bbn-hn.exogeni.net:11443-node_cpu-aggregate_bbn-hn.exogeni.net:11443" start="1349759970" step="15">
                <column_names>
                        cpu_idle
                </column_names>
                <type>
                        node_cpu
                </type>
                <node_name>
                        bbn-hn.exogeni.net:11443
                </node_name>
                <tags>
                        aggregate:bbn-hn.exogeni.net:11443
                </tags>
                <data>
                        1349759955,;
1349759970,85.294;

                </data>
        </data_group>
        <data_group end="1349759970" heartbeat="60" interval_type="open_closed" name="bbn-hn.exogeni.net:11443-node_disk-aggregate_bbn-hn.exogeni.net:11443" start="1349759970" step="15">
                <column_names>
                        disk_part_max_used
                </column_names>
                <type>
                        node_disk
                </type>
                <node_name>
                        bbn-hn.exogeni.net:11443
                </node_name>
                <tags>
                        aggregate:bbn-hn.exogeni.net:11443
                </tags>
                <data>
                        1349759955,;
1349759970,64.3752165412;

                </data>
        </data_group>
</timeseries_data>

to gmoc-db2 as user gpolab, it succeeds.

Change History (2)

comment:1 Changed 12 years ago by chaos@bbn.com

Incidentally, i also get a failure on gmoc-db submitting resource measurement data for the vmserver worker nodes (and that also works on gmoc-db2).

comment:2 Changed 12 years ago by chaos@bbn.com

Resolution: → fixed
Status: new → closed

This happened because the change which was made on gmoc-db2, to loosen the node_info restrictions to not require an FQDN, hadn't been made on gmoc-db yet. It has now been made, and submission works. Thanks!

Note: See TracTickets for help on using tickets.