ssic-linux-users — User discussion

Re: [SSI-users] PXE Nodes

[Sergi B. <hi...@li...>]

John Hughes escribió:
>
> Well drat.
>
> Ok, do:
>
>    mklocalfile  "/etc/blkid.tab"
>     
> and retry your ssi-addnode.
The script ssi-addnode deletes /etc/blkid.tab simlynk and create this 
file again.

This is the problem.

-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] PXE Nodes

[Sergi B. <hi...@li...>]

John Hughes escribió:
>
> Well drat.
>
> Ok, do:
>
>    mklocalfile  "/etc/blkid.tab"
>     
> and retry your ssi-addnode.
I moved /cluster/nodetemplate//etc/blkid.tab to 
/cluster/nodetemplate//etc/blkid.tab.old then mklocalfile  "/etc/blkid.tab"

But ssi-addnode halt again.

-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] PXE Nodes

[Sergi B. <hi...@li...>]

John Hughes escribió:
>
> Well drat.
>
> Ok, do:
>
>    mklocalfile  "/etc/blkid.tab"
>     
> and retry your ssi-addnode.
This is the error message I get:

/usr/sbin/mklocalfile: ERROR: /cluster/nodetemplate//etc/blkid.tab 
already exists. Cannot make a CDSL.


And this is the diff between two files:

diff /etc/blkid.tab /cluster/nodetemplate//etc/blkid.tab
1c1
< <device DEVNO="0x0801" TIME="1239021353" 
UUID="022bc8e3-cce4-4195-bc49-0888eeec866d" TYPE="ext3">/dev/sda1</device>
---
 > <device DEVNO="0x0801" TIME="1239006821" 
UUID="022bc8e3-cce4-4195-bc49-0888eeec866d" TYPE="ext3">/dev/sda1</device>


-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] can't access public nic

[jhansen <jef...@gm...>]

What is the output of "apt-cache policy udev"


udev:
   Installed: 0.125-7
   Candidate: 0.125-7
   Version table
   ***0.125-7 -
        500 http://ftp.us.debian.org lenny/main Packages
        100 /var/lib/dpkg/status
     0.080-1 0
       1000 http://deb.openssi.org./ Packages
     
Please post your /etc/apt/preferences
(note: i created this file from scratch as it was not present.
--------------------preferences---------------------
Package: *
Pin: origin deb.openssi.org.org
Pin-Priority:1000   (i've had this both ways, i'll set back to 1001 per
above)
-----------------------------------------------------
    


 and /etc/apt/source.list files.

----------------------sources.list------------------------------
# deb http://ftps.us.gebian.org/debian lenny main

deb http://ftp.us.debian.org/debian/ lenny main
deb-src http://ftp.us.debian.org/debian/ lenny main

deb http://security.debian.org/ lenny/updates main
deb-src http://security.debian.org/ lenny/updates main

deb http://volatile.debian.org/debian-volatile lenny/volatile main
deb-src http://volatile.debian.org/debian-volatile lenny/volatile main

deb http://deb.openssi.org/alpha/openss-lenny ./
deb http://deb.openssi.org/alpha/openssi-lenny-extras ./
---------------------------------------------------

(forgive any minor typos, I typed these instead of trying to pull them off
the server as my public nic is not working ;) )
-- 
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22921448.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] PXE Nodes

[John H. <jo...@Ca...>]

Sergi Barroso wrote:
> John Hughes escribió:
>>
>> Normaly ssi-create is run automatically when openssi is installed.  
>> (In the "preinst" file for linux-ssi-image-2.6-686-smp).
>>
>> In /cluster/lib/ssi_distro.pm we have:
>>
>>        if ( ! -l "/etc/network"        ||
>>                ! -l "/var/run"         ||
>>                ! -l "/var/lock"        ||
>>                ! -l "/var/log"         ||
>>                ! -l "/etc/nodename"    ||
>>                ! -l "/var/lib/urandom" ||
>>                ! -l "/etc/blkid.tab"
>>
>>                ) {
>>                print "You should run ssi-create first\n";
>>                exit(1);
>>        }
>>
>>
>> So one of the files & directories above is not a symlink (not a CDSL 
>> in fact).
>>
>> Which one, and why?
> I tried to run it yet, but it shows this:
>
> debsrv:~# ssi-create
> A file named /etc/clustertab already exists.  You have already installed
> this cluster. It is not a good idea to install it again.
>
> These files it's not a symlink:
>
> ls -la /etc/blkid.tab*
> -rw-r--r-- 1 root root 116 abr  6 14:35 /etc/blkid.tab
> -rw-r--r-- 1 root root 116 abr  6 14:25 /etc/blkid.tab.old
>
Well drat.

Ok, do:

    mklocalfile  "/etc/blkid.tab"
      

and retry your ssi-addnode.

Re: [SSI-users] PXE Nodes

[John H. <jo...@Ca...>]

Sergi Barroso wrote:
> Please make sure that the interface with MAC address 00:02:B3:16:06:FD
> is not configured via /etc/network/interfaces
>   
This is just a confusing warning, and can be ignored.  It means - "don't 
configure a node-interconnect nic in /etc/network/interfaces".
> Press Enter to acknowledge:
>
> The following configuration has been entered:
>     Node number:        2
>     IP address:        10.0.0.2
>     Network hardware addr:    00:02:B3:16:06:FD
>     Network boot protocol:    PXE
>     Local boot device:    none
>     Nodename:        debnode1
>     Potential initnode:    No
>
> (W)rite new configuration, (R)econfigure, or (Q)uit without writing [W]:
>   
vvvvvvvvvv
> You should run ssi-create first
>   
^^^^ That is an error.  I wonder where it comes from.

# man ssi-create
...
NAME
       ssi-create -  creates a SSI cluster

SYNOPSIS
       ssi-create [OPTIONS]

DESCRIPTION
       ssi-create creates a single node SSI cluster.

       This command does the following :

       Creates the /cluster/node# directory
...


Normaly ssi-create is run automatically when openssi is installed.  (In 
the "preinst" file for linux-ssi-image-2.6-686-smp).

In /cluster/lib/ssi_distro.pm we have:

        if ( ! -l "/etc/network"        ||
                ! -l "/var/run"         ||
                ! -l "/var/lock"        ||
                ! -l "/var/log"         ||
                ! -l "/etc/nodename"    ||
                ! -l "/var/lib/urandom" ||
                ! -l "/etc/blkid.tab"

                ) {
                print "You should run ssi-create first\n";
                exit(1);
        }


So one of the files & directories above is not a symlink (not a CDSL in 
fact).

Which one, and why?

Re: [SSI-users] PXE Nodes

[Sergi B. <hi...@li...>]

John Hughes escribió:
> Sergi Barroso wrote:
>> I tried to do ssi-addnode but doesn't add it in list....
>>   
> Strange.
>
> When you sat "doesn't add it in list", which list?  dhcpd.conf?  
> clustertab?
>
> Are there any error messages?
>> Can I edit /etc/clustertab manually?
>>   
> No, because it won't create all the files in /cluster/ that 
> ssi-addnode does.
>
> We have to find out why ssi-addnode isn't working for you.
>
>
Theres the output of ssi-addnode

debsrv:~# ssi-addnode

Enter a node number (2-125) or (?) [2]: 2

    Hardware address    Time last probed
    ----------------    ----------------
  1)    00:02:B3:16:06:FD    Apr 6 14:32:11

Select (1-2), (r)escan, (q)uit or (?) [1]: 1

Do you want to scan for available IP addresses (y/n/?) [n]:
Enter an IP address or (?): 10.0.0.2

Select (P)XE, (E)therboot or (?) [E]: P

Enter a nodename or (?): debnode1

Please make sure that the interface with MAC address 00:02:B3:16:06:FD
is not configured via /etc/network/interfaces

Press Enter to acknowledge:

The following configuration has been entered:
    Node number:        2
    IP address:        10.0.0.2
    Network hardware addr:    00:02:B3:16:06:FD
    Network boot protocol:    PXE
    Local boot device:    none
    Nodename:        debnode1
    Potential initnode:    No

(W)rite new configuration, (R)econfigure, or (Q)uit without writing [W]:
You should run ssi-create first


ssi-addnode try to find this interface inside 
/etc/networking/interfaces? why? this mac it's from client node 
interface, not server.

-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] PXE Nodes

[John H. <jo...@Ca...>]

Sergi Barroso wrote:
> I tried to do ssi-addnode but doesn't add it in list....
>   
Strange.

When you sat "doesn't add it in list", which list?  dhcpd.conf?  clustertab?

Are there any error messages?
> Can I edit /etc/clustertab manually?
>   
No, because it won't create all the files in /cluster/ that ssi-addnode 
does.

We have to find out why ssi-addnode isn't working for you.

[SSI-users] PXE Nodes

[Sergi B. <hi...@li...>]

Hi again!

After installing server node I tried to boot some clients with pxe but 
server can't server ip addresses, getting this warning in daemon.log

dhcpd: DHCPDISCOVER from 00:02:b3:16:06:fd via eth0: network 10.0.0/24: 
no free leases

The file /etc/dhcp3/dhcpd.conf show like this:

# /etc/dhcp3/dhcpd.conf
#
# Do _not_ edit this file!! It was automatically generated by mkdhcpd.conf.
#

# Section 1 (from /etc/dhcp3/dhcpd.proto)

next-server 10.0.0.1;

# Section 2 (from /etc/clustertab)

subnet 10.0.0.0 netmask 255.255.255.0 {
        if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
                filename "/combined";
        } else {
                filename "/pxelinux.0";
        }


                host node1 {
                        hardware ethernet 00:02:B3:B3:63:A9;
                        fixed-address 10.0.0.1;
                }

}


I tried to do ssi-addnode but doesn't add it in list....

Can I edit /etc/clustertab manually?


-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

jhansen wrote:
> dpkg -l udev
>
> says what?
>
> Desired =
> Unknown/Install/Remove/Purge/Hold|Status=Not/Inst/Cfg-files/Unpacked/Failed-cfd/Half-inst/trig-aWait/Trig-Pend|Err?=(none)/Hold/Reinst-required/x=both-problems(Status,Err:
> uppercase = bad)
>
> udev 0.125-7 /dev/ add hotplug management daemon
>
>
> Also, question the Pin Priority am I supposed 1000 or 1001? I've done it
> both ways with the same results so far.
>   
You've still got the wrong udev installed.

pin-priority should be 1001

What is the output of "apt-cache policy udev"

Please post your /etc/apt/preferences and /etc/apt/source.list files.

Re: [SSI-users] can't access public nic

[jhansen <jef...@gm...>]

dpkg -l udev

says what?

Desired =
Unknown/Install/Remove/Purge/Hold|Status=Not/Inst/Cfg-files/Unpacked/Failed-cfd/Half-inst/trig-aWait/Trig-Pend|Err?=(none)/Hold/Reinst-required/x=both-problems(Status,Err:
uppercase = bad)

udev 0.125-7 /dev/ add hotplug management daemon


Also, question the Pin Priority am I supposed 1000 or 1001? I've done it
both ways with the same results so far.
-- 
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22886261.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

jhansen wrote:
> Hi,
> I got to this point:
>       apt-get install udev
>
> and the program said udev is already at latest version and did not install
> anything and my kernal was not replaced.
>           
>       rm /etc/udev/rules.d/*
>       sh -c 'source /var/lib/dpkg/info/udev.postinst abort-deconfigure;
> create_rules_symlink'
>
> When I ran the above sh command I recieved an error "command
> create_rules_symlink not found"          
>
> What do you think?
>   
dpkg -l udev

says what?

Re: [SSI-users] can't access public nic

[jhansen <jef...@gm...>]

Hi,
I got to this point:
      apt-get install udev

and the program said udev is already at latest version and did not install
anything and my kernal was not replaced.
          
      rm /etc/udev/rules.d/*
      sh -c 'source /var/lib/dpkg/info/udev.postinst abort-deconfigure;
create_rules_symlink'

When I ran the above sh command I recieved an error "command
create_rules_symlink not found"          

What do you think?
-- 
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22879688.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] If anyone had any problems getting to www.openssi.org or deb.openssi.org last night...

[John H. <jo...@Ca...>]

John Hughes wrote:
> It was caused by problems at register.com:
>
> http://mailman.nanog.org/pipermail/nanog/2009-April/009115.html
>
> http://www.reddit.com/r/technology/comments/89a7p/anyone_else_having_issues_resolving_registercom/
>
>   
Down again last night (2/4/2009 around 21:00 +02:00 (CET DST))

[SSI-users] If anyone had any problems getting to www.openssi.org or deb.openssi.org last night...

[John H. <jo...@Ca...>]

It was caused by problems at register.com:

http://mailman.nanog.org/pipermail/nanog/2009-April/009115.html

http://www.reddit.com/r/technology/comments/89a7p/anyone_else_having_issues_resolving_registercom/

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

I've updated the instructions at 
http://deb.openssi.org/alpha/openssi-lenny/ to cope with the changes in 
apt-get's behaviour and show how to set up the udev/rules.d directory 
correctly.  The important bit is:

   1.

      apt-get dist-upgrade
          

      This should replace all the standard versions of the packages by
      our modified versions. However apt-get seems to have changed its
      behaviour, it no longer considers some downgrades, so now we have
      to do:
   2.

      apt-get install udev
          

      At this point you will be warned that the running kernel will be
      removed.  This is because of a necessary downgrade of udev.  Allow
      it to happen.

      :-(  Warning - your system is unbootable starting from this point.

      (We only need this step because apt-get seems not to notice that
      udev needs downgrading on an "apt-get dist-upgrade", it used to
      work. This is annoying).

   3. As the udev install is not smart enough to fix it's configuration
      files after a downgrade we need to do it manualy:

      rm /etc/udev/rules.d/*
      sh -c 'source /var/lib/dpkg/info/udev.postinst abort-deconfigure; create_rules_symlink'
          


Admittedly the shell command is rather barbaric, but it does the job.

Re: [SSI-users] can't access public nic

[Sergi B. <hi...@li...>]

John Hughes escribió:
> Sergi Barroso wrote:
>> Downgrading udev don't load old rules version, the solution is don't 
>> delete it.
>>
>>   
> Well, the problem is both simpler and harder than I thought.
>
> In my instructions I have:
>
> ...
>
>    1. As we're going to downgrade udev we must zap all rules our old
>       version isn't smart enough to handle:
>       rm /etc/udev/rules.d/*
>           
>    2. As we're going to remove the running kernel we must modprobe all
>       modules needed to build the initrd or we won't be able to make a
>       bootable system (*don't forget this or you'll be stuck with an
>       unbootable system*):
>       modprobe loop
>       modprobe ext2
>           
>   3.
>       apt-get dist-upgrade
>           
>       At this point you will be warned that the running kernel will be
>       removed.  This is because of a necessary downgrade of udev. 
>       Allow it to happen.
>
>       :-(  Warning - your system is unbootable starting from this point.
>
> But, in fact,udev *is not* downgraded when we do the apt-get 
> dist-upgrade.  It looks like apt has been modified to use the same 
> algorithm as aptitude and not consider downgrades when we ask it to 
> upgrade.
>
> An extra step has to be added, before the "apt-get dist-upgrade" we 
> need a "apt-get install udev" which will force the install of our old 
> version of udev.
>
> There is still a problem with the creation of the rules.d directory, 
> but at least that should get things working better.
>
>
>
ok, cool! as easy as this :D

Thanks John, I'll try it on friday....

-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

Sergi Barroso wrote:
> Downgrading udev don't load old rules version, the solution is don't 
> delete it.
>
>   
Well, the problem is both simpler and harder than I thought.

In my instructions I have:

...

   1. As we're going to downgrade udev we must zap all rules our old
      version isn't smart enough to handle:

      rm /etc/udev/rules.d/*
          

   2. As we're going to remove the running kernel we must modprobe all
      modules needed to build the initrd or we won't be able to make a
      bootable system (*don't forget this or you'll be stuck with an
      unbootable system*):

      modprobe loop
      modprobe ext2
          

   3.

      apt-get dist-upgrade
          

      At this point you will be warned that the running kernel will be
      removed.  This is because of a necessary downgrade of udev.  Allow
      it to happen.

      :-(  Warning - your system is unbootable starting from this point.

But, in fact,udev *is not* downgraded when we do the apt-get 
dist-upgrade.  It looks like apt has been modified to use the same 
algorithm as aptitude and not consider downgrades when we ask it to upgrade.

An extra step has to be added, before the "apt-get dist-upgrade" we need 
a "apt-get install udev" which will force the install of our old version 
of udev.

There is still a problem with the creation of the rules.d directory, but 
at least that should get things working better.

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

Sergi Barroso wrote:
> Downgrading udev don't load old rules version, the solution is don't 
> delete it.
>
>   
This is really wierd.  I'm going to get around to checking it out later.

Re: [SSI-users] can't access public nic

[Sergi B. <hi...@li...>]

John Hughes escribió:
> jhansen wrote:
>   
>> And is the module for the public loaded?
>>       --> in /etc/mkinitrd/modules?
>>     
> No, I meant does it show up in lsmod.  And if it's not does the nic show 
> up if you do a modprobe.
>   
>>  I just have the interconnect per my
>> instructions so, no. I can try reinstall again and add 3C509?
>>   
>>     
> Shouldn't need to.  It should be loaded by udev
>   
>> What do you have in /etc/udev/rules.d?
>>      -->There is nothing in this directory.
>>   
>>     
> And this is the problem.
>
> In my instructions it says to delete /etc/udev/rules.d *before* doing 
> the apt-get dist-upgrade.  The dist-upgrade is supposed to load a new 
> (older) version of udev that should load its own rules.  Something seems 
> to be going wrong.
>
> I'm going to have to try this out myself today.  I'll get back to you 
> when I have more information.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ssic-linux-users mailing list
> Ssi...@li...
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
>   
Downgrading udev don't load old rules version, the solution is don't 
delete it.

-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

Sergi Barroso wrote:
> I also put all my nic drivers in /etc/mkinitrd/modules, and not deleted 
> udev rules files, if you want I can send it to you, or maybe you want to 
> reinstall it.
>   
Do you get udev errors on boot?

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

jhansen wrote:
> And is the module for the public loaded?
>       --> in /etc/mkinitrd/modules?
No, I meant does it show up in lsmod.  And if it's not does the nic show 
up if you do a modprobe.
>  I just have the interconnect per my
> instructions so, no. I can try reinstall again and add 3C509?
>   
Shouldn't need to.  It should be loaded by udev
> What do you have in /etc/udev/rules.d?
>      -->There is nothing in this directory.
>   
And this is the problem.

In my instructions it says to delete /etc/udev/rules.d *before* doing 
the apt-get dist-upgrade.  The dist-upgrade is supposed to load a new 
(older) version of udev that should load its own rules.  Something seems 
to be going wrong.

I'm going to have to try this out myself today.  I'll get back to you 
when I have more information.

Re: [SSI-users] can't access public nic

[Sergi B. <hi...@li...>]

jhansen escribió:
> And is the module for the public loaded?
>       --> in /etc/mkinitrd/modules? I just have the interconnect per my
> instructions so, no. I can try reinstall again and add 3C509?
>
> What do you have in /etc/udev/rules.d?
>      -->There is nothing in this directory.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ssic-linux-users mailing list
> Ssi...@li...
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
>
>
>
>   
Hi!

I also put all my nic drivers in /etc/mkinitrd/modules, and not deleted 
udev rules files, if you want I can send it to you, or maybe you want to 
reinstall it.


-- 
Sergi Barroso
Linux user #313577
PGPID: D318F5E8
http://www.lionclan.org

Re: [SSI-users] can't access public nic

[jhansen <jef...@gm...>]

And is the module for the public loaded?
      --> in /etc/mkinitrd/modules? I just have the interconnect per my
instructions so, no. I can try reinstall again and add 3C509?

What do you have in /etc/udev/rules.d?
     -->There is nothing in this directory.

------------------------------------------------------------------------------
_______________________________________________
Ssic-linux-users mailing list
Ssi...@li...
https://lists.sourceforge.net/lists/listinfo/ssic-linux-users



-- 
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22819190.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] can't access public nic

[John H. <jo...@Ca...>]

jef...@gm... wrote:
> lspci shows among other things, both nics:
>
> private nic: is 3COM 3c905 B 100base TX (rev 30)
> public nic: is Intell Ethernet Pro 100 (rev 08).
And is the module for the public loaded?

This sounds a lot like the problem Sergi Barroso <hi...@li...> 
was having - maybe I've screwed up my lenny instructions somewhere.

What do you have in /etc/udev/rules.d?