[Rocks-Discuss] insert-ethers, cabinet & rank, and a bug report

167 views
Skip to first unread message

Rob Hutten

unread,
Sep 4, 2009, 10:21:55 AM9/4/09
to npaci-rocks...@sdsc.edu

Hi all,

A question about running insert-ethers, and a bug report.

I'm adding a node to one of our Rocks 5.1 clusters using this command:

insert-ethers --rank=28 --cabinet=1

The existing nodes are numbered c1-0 to c1-31, but for historical
reasons c1-28 was never brought online until now.

When the node PXIE-boots, insert-ethers crashes with an error, the text of
which is dumped to the screen rendered with unreadable/non-ascii chars.
So I re-ran insert-ethers with stderr redirected to a file; this showed
the message to be:

error - int() argument must be a string or a number

It works just fine without the --rank and --cabinet params, but it names
my node "compute-0-0". "insert-ethers --cabinet=1" (without the --rank)
also produces this error. I've also tried --rack instead of --cabinet,
just for shiggles. Same error.

Is this not the standard way to name a new compute node "compute-1-28"?

I've attached the output of "dbreport bug".

...

And the bug report: Again under Rocks 5.1, insert-ethers was giving
me the aforementioned display grief so I was futzing with different
$TERM settings. As per below, insert-ethers doesn't seem to clean up
its lockfile when it bails:

[root@fog ~]# export TERM=tty
[root@fog ~]# insert-ethers
Unknown terminal: tty
Check the TERM environment variable.
Also make sure that the terminal is defined in the terminfo database.
Alternatively, set the TERMCAP environment variable to the desired
termcap entry.
[root@fog ~]# export TERMCAP=tty
[root@fog ~]# insert-ethers
Traceback (most recent call last):
   File "/opt/rocks/sbin/insert-ethers", line 1718, in ?
     app.run()
   File "/opt/rocks/sbin/insert-ethers", line 1677, in run
     raise _("error - lock file %s exists") % self.lockFile
error - lock file /var/lock/insert-ethers exists
[root@fog ~]# ls -ltr /var/lock/insert-ethers
-rw-r--r-- 1 root root 0 Sep  3 16:52 /var/lock/insert-ethers
[root@fog ~]# date
Thu Sep  3 16:53:21 ADT 2009

Ignore that "tty" is invalid - it should still clean up its lockfile.
No-one else was running insert-ethers at the time.


Thanks,
-Rob

--
Rob Hutten
Senior HPC Engineer
Flagstone RE
Suite 700, Cogswell Tower
2000 Barrington Street
Halifax, Nova Scotia B3J 3K1
www.flagstonere.bm


**********************************************************************
This communication contains information which is confidential and may also be legally privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), disclosure, copying, distribution, or other use of, or action taken or omitted to be taken in reliance upon, this communication or the information in it is prohibited and maybe unlawful. If you have received this communication in error please notify the sender by return email, delete it from your system and destroy any copies.
**********************************************************************

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dbreport-bug.txt
Url: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20090904/76984a4b/dbreport-bug.txt

Bart Brashers

unread,
Sep 4, 2009, 11:12:20 AM9/4/09
to Discussion of Rocks Clusters
You could try to add the host to the database first, then PXE boot it. Basically:

# rocks add host compute-1-28 rack=1 rank=28
# rocks set host interface compute-1-28 eth0 ip=10.X.Y.Z

(make all the settings except ip match the output of "rocks list host interface compute-1-27)

# rocks set host interface mac compute-1-28 eth0 00:0a:0b:0c:0d:ff

(the mac should be on a sticker on the nic or mb)

I've probably missed some steps, but if you google the "rocks set host interface" you'll probably find another posting by greg that lists all the steps.

Bart


This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to em...@environcorp.com and immediately delete all copies of the message.

Bart Brashers

unread,
Sep 4, 2009, 11:33:55 AM9/4/09
to Discussion of Rocks Clusters

Also, isn't it supposed to be "--rack=1 --rank=28"? Give it a shot...

Bart

> -----Original Message-----
> From: npaci-rocks-dis...@sdsc.edu
> [mailto:npaci-rocks-dis...@sdsc.edu] On Behalf Of
> Rob Hutten
> Sent: Friday, September 04, 2009 7:22 AM
> To: npaci-rocks...@sdsc.edu
> Subject: [Rocks-Discuss] insert-ethers, cabinet & rank, and a
> bug report
>
>
>

Greg Bruno

unread,
Sep 4, 2009, 11:46:05 AM9/4/09
to Discussion of Rocks Clusters
On Fri, Sep 4, 2009 at 7:21 AM, Rob Hutten<rhu...@flagstonere.bm> wrote:
>
> Hi all,
>
> A question about running insert-ethers, and a bug report.
>
> I'm adding a node to one of our Rocks 5.1 clusters using this command:
>
>         insert-ethers --rank=28 --cabinet=1
>
> The existing nodes are numbered c1-0 to c1-31, but for historical
> reasons c1-28 was never brought online until now.
>
> When the node PXIE-boots, insert-ethers crashes with an error, the text of
> which is dumped to the screen rendered with unreadable/non-ascii chars.
> So I re-ran insert-ethers with stderr redirected to a file; this showed
> the message to be:
>
>        error - int() argument must be a string or a number
>
> It works just fine without the --rank and --cabinet params, but it names
> my node "compute-0-0".  "insert-ethers --cabinet=1" (without the --rank)
> also produces this error.  I've also tried --rack instead of --cabinet,
> just for shiggles.  Same error.

try:

# rocks sync config

then try:

# insert-ethers --cabinet=1 --rank=28

- gb

Rob Hutten

unread,
Sep 4, 2009, 1:03:14 PM9/4/09
to Discussion of Rocks Clusters

I asked:
> A question about running insert-ethers, [...]


And Greg Bruno suggested:

> try:
>
> # rocks sync config
>
> then try:
>
> # insert-ethers --cabinet=1 --rank=28

This worked perfectly. Thanks, Greg!

-Rob

Reply all
Reply to author
Forward
0 new messages