Custom Query (98 matches)

Serial console access from the control node to the rack dataplane switch does not work yet.

I created the experiment peni-gpolab-bbn-com/ecgtest on Saturday morning, and used it on Saturday and (possibly) yesterday. Today, ​https://boss.utah.geniracks.net/showexp.php3?experiment=952 shows the node status of pcvm3-1 as "up (TBFAILED)", and i can't SSH into the VM. I get the error:

capybara,[~],14:23(0)$ sshtmp -p 30010 pc3.utah.geniracks.net
The authenticity of host 'pc3.utah.geniracks.net (155.98.34.13)' can't be established.
RSA key fingerprint is 6d:1d:76:53:a5:25:99:39:e2:89:ea:b0:99:e3:d3:b9.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'pc3.utah.geniracks.net,155.98.34.13' (RSA) to the list of known hosts.
Warning: no access to tty (Bad file descriptor).
                                                Thus no job control in this shell.

and then the shell hangs (sshtmp is an alias for "ssh -o UserKnownHostsFile?=/dev/null".)

Determine what happened to the experiment and why it got into a bad state.

I hope this is an easy fix, because it is making our mailserver slightly unhappy...

After yesterday's upgrade, Luisa created 10 slivers at utah.geniracks.net. As a result, we received over 1600 e-mails which looked like this:

From: Unprivileged user <nobody@pgeni.gpolab.bbn.com>
Date: Wed, 30 May 2012 16:25:29 -0400 (EDT)
To: testbed-ops@ops.pgeni.gpolab.bbn.com
Cc: protogeni-errors@flux.utah.edu
Reply-To: testbed-ops@ops.pgeni.gpolab.bbn.com
Subject: [gpo-ops] PGENI.GPOLAB.BBN.COM: protogeni-wrapper.pl

protogeni-wrapper.pl
Invoked by nobody (Unprivileged user)
URN:     urn:publicid:IDN+utah.geniracks.net+authority+cm
Target:  urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+10vmslice1                 
Module:  sa
Method:  RegisterSliver
Start:   16:25:29:579861
End:     16:25:29:662445
Elapsed: 0.082565
Error:   2
Output:  Could not create credential object
Result:
$VAR1 = 0;

Over 200 of these e-mails contain the name of each sliver, and they appear to be sent approximately once per sliver per minute for about 3 hours.

I replicated this just now with my own ecgtest slice, and we have started receiving these e-mails for my slice too.