ssic-linux-users

[SSI-users] first node stuck

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

On to the next step. I have installed fresh server install of debian and open
ssi. I have started the process of adding the new node. I have etherboot on
'child1' server connecting to the interconnect and run 'ssi-addnode' on my
init node, and successfuly written the configuration script. The child node
appears to start to process of adding itself to the cluser and i see where
it is found the ramdisck and mounted root (ext2 filesystem). I also see
where it has added my interconnect module (eepro100.c etc...

Now at the bottom of the screen it appears stuck on this line:
input: IMExPS/2 Generic Exploerer Mouse on isa0060/serio1

checking the init node with "cluster -v" only shows:
1: UP

I have rebooted both nodes with no luck. 

I also tried booting without the moust attached. I get to the statement
about eepro100.c and it still just hangs. again "cluster -v" just shows "1:
UP"

What now?

Thanks in advance,


Jeff
-- 
View this message in context: http://www.nabble.com/first-node-stuck-tp23239473p23239473.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] first [actually 2nd] node stuck

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

jhansen wrote:
> On to the next step. I have installed fresh server install of debian and open
> ssi. I have started the process of adding the new node. I have etherboot on
> 'child1' server connecting to the interconnect and run 'ssi-addnode' on my
> init node, and successfuly written the configuration script. The child node
> appears to start to process of adding itself to the cluser and i see where
> it is found the ramdisck and mounted root (ext2 filesystem). I also see
> where it has added my interconnect module (eepro100.c etc...
>
> Now at the bottom of the screen it appears stuck on this line:
> input: IMExPS/2 Generic Exploerer Mouse on isa0060/serio1
>
> checking the init node with "cluster -v" only shows:
> 1: UP
>   
Could you please provide a little more info about the on-screen messages.

Here's what a boot of a 2nd node looks like when it works:

Linux version 2.6.14-ssi-686-smp (john@a.baltic) (gcc version 3.4.6 (Debian 3.4.6-9)) #1 SMP Thu Mar 26 09:51:34 CET 2009
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000f9f0000 (usable)
 BIOS-e820: 000000000f9f0000 - 000000000fa00000 (ACPI data)
 BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
249MB LOWMEM available.
DMI 2.4 present.
Using APIC driver default
ACPI: PM-Timer IO Port: 0xb008
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:3 APIC version 17
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 10000000 (gap: 0fa00000:f05c0000)
Built 1 zonelists
Kernel command line: root=/dev/hdb1 ro console=ttyS0,38400
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Detected 2595.143 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 242660k/255936k available (3957k kernel code, 12604k reserved, 2174k data, 260k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 5294.48 BogoMIPS (lpj=10588976)
kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved
kdb_cmd[0]: defcmd archkdb "" "First line arch debugging"
kdb_cmd[6]: defcmd archkdbcpu "" "archkdb with only tasks on cpus"
kdb_cmd[12]: defcmd archkdbshort "" "archkdb with less detailed backtrace"
kdb_cmd[18]: defcmd archkdbcommon "" "Common arch debugging"
Mount-cache hash table entries: 512
VProc hash table entries: 8192 (order: 4, 65536 bytes)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
mtrr: v2.0 (20020519)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: Intel Pentium II (Klamath) stepping 03
Total of 1 processors activated (5294.48 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=0 pin2=-1
Brought up 1 CPUs
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
softlockup thread 0 started up.
Freeing initrd memory: 1942k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb200, last bus=0
PCI: Using configuration type 1
ACPI: Subsystem revision 20050902
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region b000-b03f claimed by PIIX4 ACPI
PCI quirk: region b100-b11f claimed by PIIX4 SMB
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 6 devices
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
audit(1240822836.788:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
CFS server token hash table entries: 8192 (order: 3, 32768 bytes)
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Limiting direct PCI/PCI transfers.
Activating ISA DMA hang workarounds.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: CPU0 (power states: C1[C1])
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
Linux agpgart interface v0.101 (c) Dave Jones
PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 32 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16450
ttyS0 at I/O 0x3f8 (irq = 4) is a 16450
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller at PCI slot 0000:00:01.1
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
hda: QEMU HARDDISK, ATA DISK drive
hdb: QEMU HARDDISK, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: QEMU CD-ROM, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 2097152 sectors (1073 MB) w/256KiB Cache, CHS=2080/255/63, (U)DMA
hda: cache flushes supported
 hda: hda1 hda2
hdb: max request size: 1024KiB
hdb: 12582912 sectors (6442 MB) w/256KiB Cache, CHS=12483/255/63, (U)DMA
hdb: cache flushes supported
 hdb: hdb1
hdc: ATAPI 4X CD-ROM drive, 512kB Cache, (U)DMA
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
usbmon: debugfs is not available
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 3.39
NET: Registered protocol family 2
input: AT Translated Set 2 keyboard on isa0060/serio0
input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
IPVS: Registered protocols (TCP, UDP, AH, ESP)
IPVS: Connection hash table configured (size=65536, memory=512Kbytes)
IPVS: ipvs loaded.
IPVS: [wlc] scheduler registered.
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 10
Disabled Privacy Extensions on device c065de00(lo)
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 260k freed
initrd-tools: 0.1.84.2.ssi4
mount: unknown filesystem type 'devfs'
ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
eth0: RealTek RTL-8029 found at 0xc100, IRQ 10, 52:54:00:12:02:00.
Waiting for 5 seconds, press ENTER to obtain a shell.
umount: devfs: not mounted
Gathering cluster info
Configuring eth0: 192.168.64.2/255.255.255.0
Configuring cluster
Running pre-root cluster initialization
Searching for an existing root node...
Found node 1 as the root node.
nm_add_node: Node 1 added
ipcnameserver ready completed

This is a CI/OpenSSI kernel.
    This Cluster Node: 2
    Potential Initnode(s): 1:192.168.64.1,2:192.168.64.2

Name server registered with clms
ipcname_read completed
Attempting to pivot_root
Running post-root cluster initialization
warning: can't open /proc/mounts: No such file or directory
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...FDC 0 is a S82078B
piix4_smbus 0000:00:01.3: Found 0000:00:01.3 device
e100: Intel(R) PRO/100 Network Driver, 3.4.14-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
e100: eth1: e100_probe: addr 0xf2001000, irq 9, MAC addr 52:54:00:12:02:02
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
done.
Waiting for /dev to be fully populated...done.
Unmounting /sys
Unmounting /proc
Starting init
/etc/init.d/rc.nodeup 2 running
Syncing clock with node 1: Mon Apr 27 11:01:12 CEST 2009 date
Cleaning up ifupdown....
Checking all file systems...
fsck 1.40-WIP (14-Nov-2006)
... done.
Setting up networking....
Configuring network interfaces...Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
Listening on LPF/eth1/52:54:00:12:02:02
Sending on   LPF/eth1/52:54:00:12:02:02
Sending on   Socket/fallback
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 10.0.2.2
bound to 10.0.2.15 -- renewal in 34534 seconds.
done.
CVIP_NOT_CONFIGURED
Starting system log daemon....
Starting kernel log daemon....
Starting ACPI services....
Starting system message bus: dbus.
Starting Hardware abstraction layer: hald.
Starting Hardware abstraction layer: hald/usr/sbin/hald already running.
.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
invoke-rc.d: WARNING: Service system-tools-backends has no entry in rc.nodeinfo
invoke-rc.d: Starting only on initnode
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Starting OpenBSD Secure Shell server: sshd.
Starting portmap daemon: portmap.
WARNING: Service cups not in rc.nodeinfo
WARNING: Service exim4 not in rc.nodeinfo
WARNING: Service ipvsadm not in rc.nodeinfo
Starting internet superserver: inetd.
WARNING: Service policycoreutils not in rc.nodeinfo
WARNING: Service saned not in rc.nodeinfo
WARNING: Service fam not in rc.nodeinfo
WARNING: Service system-tools-backends not in rc.nodeinfo
Synchronizes SSI boot materials across the cluster
WARNING: Service atd not in rc.nodeinfo
Starting OpenSSI root failover initialization script: SSIfailover.
Starting OpenSSI Cluster load leveling initialisation: loadlevel.

...

Re: [SSI-users] first [actually 2nd] node stuck

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

is this enough info:

....
IPVS: Registered protocols (TCP, UDP, AH, ESP)
IPVS: Connection hash table configured (size=65536, memory=512Kbytes)
IPVS: ipvs loaded.
IPVS: [wlc] scheduler registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 10
Disabled Privacy Extensions on device C06706a(lo)
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17 
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 272kfreed 
Input AT Translated set 2 keyboard on isa0060/serw0
eepro100.c: V1.09 jut 9/29/33 Donald Bec.....
eepro100.c: $Revision 1.36$2000/11/17 Donald Bercw....
Input: ImExPS/2 Generic mouse on ISa0060 serio1

That's where it gets stuck...

I noticed some lines missing compared to yours 
example: initrd-tools: 0.1.84.2.ssi4 is missing after kernal memory is
freed.


I am using RTL-8139 nic with etherboot  for the same without floppy
emulation in cdrom drive.
My interconnect is a eepro100.

Is this enough info? If not, is this output sent to log someplace?
/var/logs? My 2nd node is currently unbootable on its own right now, so I
will need to install something. Just not sure if etherboot writes anything.

-- 
View this message in context: http://www.nabble.com/first-node-stuck-tp23239473p23253491.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] first [actually 2nd] node stuck

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

jhansen wrote:
> is this enough info:
>
> ....
> IPVS: Registered protocols (TCP, UDP, AH, ESP)
> IPVS: Connection hash table configured (size=65536, memory=512Kbytes)
> IPVS: ipvs loaded.
> IPVS: [wlc] scheduler registered
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 10
> Disabled Privacy Extensions on device C06706a(lo)
> IPv6 over IPv4 tunneling driver
> NET: Registered protocol family 17 
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 272kfreed 
> Input AT Translated set 2 keyboard on isa0060/serw0
> eepro100.c: V1.09 jut 9/29/33 Donald Bec.....
> eepro100.c: $Revision 1.36$2000/11/17 Donald Bercw....
> Input: ImExPS/2 Generic mouse on ISa0060 serio1
>
> That's where it gets stuck...
I have:

[...same].
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 260k freed
initrd-tools: 0.1.84.2.ssi4
mount: unknown filesystem type 'devfs'
ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
eth0: RealTek RTL-8029 found at 0xc100, IRQ 10, 52:54:00:12:02:00.
Waiting for 5 seconds, press ENTER to obtain a shell.

The differences start at "initrd-tools: 0.1.84.2.ssi4" which comes from 
the initrd.

What version of initrd-tools do you have installed?

You're doing an etherboot here? What version? Is it doing old-style 
etherboot or PXE? Is /tftpboot/initrd the same as the initrd your first 
node is booting off? (initrd.img-2.6.12-ssi-686-smp) If you're doing an 
old-style etherboot is /tftpboot/combined up to date? (I.E. does 
/tftpboot/combined == /tftpboot/kernel + /tftpboot/initrd)

In fact, please post a ls -lR of /tftpboot

Re: [SSI-users] first [actually 2nd] node stuck

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

jhansen wrote:
> The differences start at "initrd-tools: 0.1.84.2.ssi4" which comes from 
> the initrd.
>
> What version of initrd-tools do you have installed?
>       0.1.84.2.ssi4
>
> You're doing an etherboot here? What version? 
>      I used: Etherboot 5.4.4 (2008-09-26) Image Generator at: 
> http://rom-o-matic.net/ rom-o-matic 
>
> Is it doing old-style 
> etherboot or PXE? 
>     ETHERBOOT
>   

(Newer "etherboot"s can do PXE boot as well, which avoids the yucky 
"combined" stuff/

> Is /tftpboot/initrd the same as the initrd your first 
> node is booting off? (initrd.img-2.6.12-ssi-686-smp) If you're doing an 
> old-style etherboot is /tftpboot/combined up to date? (I.E. does 
> /tftpboot/combined == /tftpboot/kernel + /tftpboot/initrd)
>    It looks like the files are different sized so I doubt it.
> In fact, please post a ls -lR of /tftpboot
>
>
> jhansen01:~# ls -lR /tftpboot
> /tftpboot:
> total 8776
> -rw-r--r-- 1 root root 4481536 2009-04-26 12:08 combined
> -rw-r--r-- 1 root root 1982767 2009-04-26 12:08 initrd
> -rw-r--r-- 1 root root 2488663 2009-04-25 23:15 kernel
> lrwxrwxrwx 1 root root      28 2009-04-25 23:15 pxelinux.0 ->
> /usr/lib/syslinux/pxelinux.0
> drwxr-xr-x 2 root root    4096 2009-04-25 23:14 pxelinux.cfg
>
> /tftpboot/pxelinux.cfg:
> total 4
> -rw-r--r-- 1 root root 279 2008-07-24 14:28 default
>
>   
So
    cmp /tftpboot/initrd /boot/initrd.img-2.6.12-ssi-686-smp

says what?

Re: [SSI-users] first [actually 2nd] node stuck

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

So
    cmp /tftpboot/initrd /boot/initrd.img-2.6.12-ssi-686-smp

says what?

jhansen01:~# cmp /tftpboot/initrd  /boot/initrd.img-2.6.12-ssi-686-smp
jhansen01:~#
jhansen01:~# ls -l /tftpboot/initrd
-rw-r--r-- 1 root root 1982767 2009-04-26 12:08 /tftpboot/initrd
jhansen01:~# ls -l /boot/initrd.img-2.6.12-ssi-686-smp
-rw-r--r-- 1 root root 1982767 2009-04-26 12:08
/boot/initrd.img-2.6.12-ssi-686-
smp


-- 
View this message in context: http://www.nabble.com/first-node-stuck-tp23239473p23295879.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] first [actually 2nd] node stuck

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

The differences start at "initrd-tools: 0.1.84.2.ssi4" which comes from 
the initrd.

What version of initrd-tools do you have installed?
      0.1.84.2.ssi4

You're doing an etherboot here? What version? 
     I used: Etherboot 5.4.4 (2008-09-26) Image Generator at: 
http://rom-o-matic.net/ rom-o-matic 

Is it doing old-style 
etherboot or PXE? 
    ETHERBOOT
Is /tftpboot/initrd the same as the initrd your first 
node is booting off? (initrd.img-2.6.12-ssi-686-smp) If you're doing an 
old-style etherboot is /tftpboot/combined up to date? (I.E. does 
/tftpboot/combined == /tftpboot/kernel + /tftpboot/initrd)
   It looks like the files are different sized so I doubt it.
In fact, please post a ls -lR of /tftpboot


jhansen01:~# ls -lR /tftpboot
/tftpboot:
total 8776
-rw-r--r-- 1 root root 4481536 2009-04-26 12:08 combined
-rw-r--r-- 1 root root 1982767 2009-04-26 12:08 initrd
-rw-r--r-- 1 root root 2488663 2009-04-25 23:15 kernel
lrwxrwxrwx 1 root root      28 2009-04-25 23:15 pxelinux.0 ->
/usr/lib/syslinux/pxelinux.0
drwxr-xr-x 2 root root    4096 2009-04-25 23:14 pxelinux.cfg

/tftpboot/pxelinux.cfg:
total 4
-rw-r--r-- 1 root root 279 2008-07-24 14:28 default

-- 
View this message in context: http://www.nabble.com/first-node-stuck-tp23239473p23288979.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] first [actually 2nd] node stuck

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

jhansen wrote:
> 
> So
>     cmp /tftpboot/initrd /boot/initrd.img-2.6.12-ssi-686-smp
> 
> says what?
> 
> jhansen01:~# cmp /tftpboot/initrd  /boot/initrd.img-2.6.12-ssi-686-smp
> jhansen01:~#
> jhansen01:~# ls -l /tftpboot/initrd
> -rw-r--r-- 1 root root 1982767 2009-04-26 12:08 /tftpboot/initrd
> jhansen01:~# ls -l /boot/initrd.img-2.6.12-ssi-686-smp
> -rw-r--r-- 1 root root 1982767 2009-04-26 12:08
> /boot/initrd.img-2.6.12-ssi-686-
> smp
> 
> 
> 
Hi, I any thoughts on what to do now based on my provided answer above?

-- 
View this message in context: http://www.nabble.com/first-node-stuck-tp23239473p23397050.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.

Re: [SSI-users] first [actually 2nd] node stuck

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

jhansen wrote:
>
> jhansen wrote:
>   
>> (initrd seems up to date)
>>     
> Hi, I any thoughts on what to do now based on my provided answer above?
>
>   

Hack the initrd-tools init and linuxrc scripts so you can see what's 
going on:

/usr/share/initrd-tools/init
/usr/share/initrd-tools/linuxrc

Add a "set -x" to turn on shell tracing.

rebuild the initrd and do a ssi-ksync

check that your /boot/initrd-xxxx, /tftpboot/initrd & /tftpboot/combined 
have been updated.

boot the 2nd node.

If you can set up a serial console for the 2nd node it would be great.