clusterworx imaging problem
6 views
Skip to first unread message
Arcadian
Apr 2, 2009, 2:59:09 PM4/2/09
to Linux Networx Users Group
While imaging a few nodes using clusterworx, we are unable to get past
the "Loading x-slam" step. It seems to take forever with only "..."
being added to the console output. Does anybody know what the problem
could be?
Here is the console output (original IPs not shown):
ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
(GPL) http://etherboot.org Tagged ELF64 ELF with TFTP SLAM LACP for
[EEPRO100][E1000][3C90X][TG3][IDE]
Relocating _text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
from (N)etwork (D)isk or (Q)uit?
Probing pci nic...
[eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
(DHCP)...
..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
10002 ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Thanks.
the "Loading x-slam" step. It seems to take forever with only "..."
being added to the console output. Does anybody know what the problem
could be?
Here is the console output (original IPs not shown):
ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
(GPL) http://etherboot.org Tagged ELF64 ELF with TFTP SLAM LACP for
[EEPRO100][E1000][3C90X][TG3][IDE]
Relocating _text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
from (N)etwork (D)isk or (Q)uit?
Probing pci nic...
[eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
(DHCP)...
..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
10002 ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Thanks.
Joshua McDowell
Apr 2, 2009, 3:10:26 PM4/2/09
to lnx...@googlegroups.com
Do u see ....... Dots, about 1 ecery second or so?
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 11:59:09
To: Linux Networx Users Group<lnx...@googlegroups.com>
Subject: [lnxiug] clusterworx imaging problem
While imaging a few nodes using clusterworx, we are unable to get past
the "Loading x-slam" step. It seems to take forever with only "..."
being added to the console output. Does anybody know what the problem
could be?
Here is the console output (original IPs not shown):
ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
(GPL) http://etherboot.org Tagged ELF64 ELF with TFTP SLAM LACP for
[EEPRO100][E1000][3C90X][TG3][IDE]
Relocating_text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 11:59:09
To: Linux Networx Users Group<lnx...@googlegroups.com>
Subject: [lnxiug] clusterworx imaging problem
While imaging a few nodes using clusterworx, we are unable to get past
the "Loading x-slam" step. It seems to take forever with only "..."
being added to the console output. Does anybody know what the problem
could be?
Here is the console output (original IPs not shown):
ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
(GPL) http://etherboot.org Tagged ELF64 ELF with TFTP SLAM LACP for
[EEPRO100][E1000][3C90X][TG3][IDE]
Joshua McDowell
Apr 2, 2009, 3:11:14 PM4/2/09
to lnx...@googlegroups.com
Sorry. Sending from blackberry..
Do you see .... Dots around every second or so?
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 11:59:09
To: Linux Networx Users Group<lnx...@googlegroups.com>
Subject: [lnxiug] clusterworx imaging problem
Do you see .... Dots around every second or so?
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 11:59:09
To: Linux Networx Users Group<lnx...@googlegroups.com>
Subject: [lnxiug] clusterworx imaging problem
While imaging a few nodes using clusterworx, we are unable to get past
the "Loading x-slam" step. It seems to take forever with only "..."
being added to the console output. Does anybody know what the problem
could be?
Here is the console output (original IPs not shown):
ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
(GPL) http://etherboot.org Tagged ELF64 ELF with TFTP SLAM LACP for
[EEPRO100][E1000][3C90X][TG3][IDE]
Relocating_text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
the "Loading x-slam" step. It seems to take forever with only "..."
being added to the console output. Does anybody know what the problem
could be?
Here is the console output (original IPs not shown):
ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
(GPL) http://etherboot.org Tagged ELF64 ELF with TFTP SLAM LACP for
[EEPRO100][E1000][3C90X][TG3][IDE]
Siekas, Greg
Apr 2, 2009, 3:01:58 PM4/2/09
to lnx...@googlegroups.com
Did you lose your multicast settings on the headnode?
What does netstat -rn show?
What's in /opt/cwx/etc/DistributionService.profile?
Greg
-----Original Message-----
From: Arcadian [mailto:bharath.ra...@gmail.com]
Sent: Thursday, April 02, 2009 11:59 AM
To: Linux Networx Users Group
Subject: [lnxiug] clusterworx imaging problem
What does netstat -rn show?
What's in /opt/cwx/etc/DistributionService.profile?
Greg
-----Original Message-----
From: Arcadian [mailto:bharath.ra...@gmail.com]
Sent: Thursday, April 02, 2009 11:59 AM
To: Linux Networx Users Group
Subject: [lnxiug] clusterworx imaging problem
Arcadian
Apr 2, 2009, 3:29:11 PM4/2/09
to Linux Networx Users Group
I see Dots about every 10 seconds.
On Apr 2, 12:11 pm, "Joshua McDowell" <JMcDow...@ISSISolutions.com>
wrote:
>
> Thanks.- Hide quoted text -
>
> - Show quoted text -
On Apr 2, 12:11 pm, "Joshua McDowell" <JMcDow...@ISSISolutions.com>
wrote:
> Sorry. Sending from blackberry..
> Do you see .... Dots around every second or so?
>
> Joshua McDowell
>
>
>
> -----Original Message-----
> From: Arcadian <bharath.ramachand...@gmail.com>
>
> Date: Thu, 2 Apr 2009 11:59:09
> To: Linux Networx Users Group<lnx...@googlegroups.com>
> Subject: [lnxiug] clusterworx imaging problem
>
> While imaging a few nodes using clusterworx, we are unable to get past
> the "Loading x-slam" step. It seems to take forever with only "..."
> being added to the console output. Does anybody know what the problem
> could be?
>
> Here is the console output (original IPs not shown):
>
> ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
> (GPL)http://etherboot.orgTagged ELF64 ELF with TFTP SLAM LACP for
> Do you see .... Dots around every second or so?
>
> Joshua McDowell
>
>
>
> -----Original Message-----
> From: Arcadian <bharath.ramachand...@gmail.com>
>
> Date: Thu, 2 Apr 2009 11:59:09
> To: Linux Networx Users Group<lnx...@googlegroups.com>
> Subject: [lnxiug] clusterworx imaging problem
>
> While imaging a few nodes using clusterworx, we are unable to get past
> the "Loading x-slam" step. It seems to take forever with only "..."
> being added to the console output. Does anybody know what the problem
> could be?
>
> Here is the console output (original IPs not shown):
>
> ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
> [EEPRO100][E1000][3C90X][TG3][IDE]
> Relocating_text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
> from (N)etwork (D)isk or (Q)uit?
> Probing pci nic...
> [eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
> (DHCP)...
> ..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
> xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
> 10002 ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
> Relocating_text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
> from (N)etwork (D)isk or (Q)uit?
> Probing pci nic...
> [eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
> (DHCP)...
> ..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
> xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
>
> Thanks.- Hide quoted text -
>
> - Show quoted text -
Arcadian
Apr 2, 2009, 3:32:05 PM4/2/09
to Linux Networx Users Group
~ 1019> netstat -rn Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface
10.220.2.0 0.0.0.0 255.255.255.0 U 0 0
0 eth1
239.192.0.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
192.168.13.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo
0.0.0.0 10.220.2.200 0.0.0.0 UG 0 0
0 eth1
~ 1020> ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:81:2D:EE:0A
inet addr:192.168.13.250 Bcast:192.168.13.255 Mask:
255.255.255.0
inet6 addr: fe80::2e0:81ff:fe2d:ee0a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30446526 errors:0 dropped:0 overruns:0 frame:0
TX packets:22600358 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3606250962 (3439.1 Mb) TX bytes:3483576444 (3322.1
Mb)
Interrupt:24
eth1 Link encap:Ethernet HWaddr 00:0A:5E:53:C1:3E
inet addr:10.220.2.73 Bcast:10.220.2.255 Mask:
255.255.255.0
inet6 addr: fe80::20a:5eff:fe53:c13e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3050061 errors:0 dropped:0 overruns:0 frame:0
TX packets:2967306 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:442221007 (421.7 Mb) TX bytes:2689086570 (2564.5
Mb)
Interrupt:16 Memory:ff3f4000-0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2939237 errors:0 dropped:0 overruns:0 frame:0
TX packets:2939237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2976045408 (2838.1 Mb) TX bytes:2976045408 (2838.1
Mb)
~ 1021> cat /opt/cwx/etc/DistributionService.profile
channels.provisioning-00.file : {system.home}/
distribution/provisioning-00
channels.provisioning-00.interface : {host.name}
channels.provisioning-00.registrar.address : {host.address}
channels.provisioning-00.registrar.port : 10000
channels.provisioning-00.multicast.address : 239.192.0.128
channels.provisioning-00.multicast.port : 10000
channels.provisioning-00.multicast.size : 1446
channels.provisioning-00.multicast.ttl : 1
channels.provisioning-00.multicast.throttle : 10000000
channels.provisioning-00.multicast.wastegate : 100000
channels.provisioning-01.file : {system.home}/
distribution/provisioning-01
channels.provisioning-01.interface : {host.name}
channels.provisioning-01.registrar.address : {host.address}
channels.provisioning-01.registrar.port : 10001
channels.provisioning-01.multicast.address : 239.192.0.128
channels.provisioning-01.multicast.port : 10001
channels.provisioning-01.multicast.size : 4096
channels.provisioning-01.multicast.ttl : 1
channels.provisioning-01.multicast.throttle : 10000000
channels.provisioning-01.multicast.wastegate : 100000
channels.provisioning-02.file : {system.home}/
distribution/provisioning-02
channels.provisioning-02.interface : {host.name}
channels.provisioning-02.registrar.address : {host.address}
channels.provisioning-02.registrar.port : 10002
channels.provisioning-02.multicast.address : 239.192.0.129
channels.provisioning-02.multicast.port : 10002
channels.provisioning-02.multicast.size : 1446
channels.provisioning-02.multicast.ttl : 1
channels.provisioning-02.multicast.throttle : 10000000
channels.provisioning-02.multicast.wastegate : 100000
channels.provisioning-03.file : {system.home}/
distribution/provisioning-03
channels.provisioning-03.interface : {host.name}
channels.provisioning-03.registrar.address : {host.address}
channels.provisioning-03.registrar.port : 10003
channels.provisioning-03.multicast.address : 239.192.0.129
channels.provisioning-03.multicast.port : 10003
channels.provisioning-03.multicast.size : 4096
channels.provisioning-03.multicast.ttl : 1
channels.provisioning-03.multicast.throttle : 10000000
channels.provisioning-03.multicast.wastegate : 100000
channels.provisioning-04.file : {system.home}/
distribution/provisioning-04
channels.provisioning-04.interface : {host.name}
channels.provisioning-04.registrar.address : {host.address}
channels.provisioning-04.registrar.port : 10004
channels.provisioning-04.multicast.address : 239.192.0.130
channels.provisioning-04.multicast.port : 10004
channels.provisioning-04.multicast.size : 1446
channels.provisioning-04.multicast.ttl : 1
channels.provisioning-04.multicast.throttle : 10000000
channels.provisioning-04.multicast.wastegate : 100000
channels.provisioning-05.file : {system.home}/
distribution/provisioning-05
channels.provisioning-05.interface : {host.name}
channels.provisioning-05.registrar.address : {host.address}
channels.provisioning-05.registrar.port : 10005
channels.provisioning-05.multicast.address : 239.192.0.130
channels.provisioning-05.multicast.port : 10005
channels.provisioning-05.multicast.size : 4096
channels.provisioning-05.multicast.ttl : 1
channels.provisioning-05.multicast.throttle : 10000000
channels.provisioning-05.multicast.wastegate : 100000
channels.provisioning-06.file : {system.home}/
distribution/provisioning-06
channels.provisioning-06.interface : {host.name}
channels.provisioning-06.registrar.address : {host.address}
channels.provisioning-06.registrar.port : 10006
channels.provisioning-06.multicast.address : 239.192.0.131
channels.provisioning-06.multicast.port : 10006
channels.provisioning-06.multicast.size : 1446
channels.provisioning-06.multicast.ttl : 1
channels.provisioning-06.multicast.throttle : 10000000
channels.provisioning-06.multicast.wastegate : 100000
channels.provisioning-07.file : {system.home}/
distribution/provisioning-07
channels.provisioning-07.interface : {host.name}
channels.provisioning-07.registrar.address : {host.address}
channels.provisioning-07.registrar.port : 10007
channels.provisioning-07.multicast.address : 239.192.0.131
channels.provisioning-07.multicast.port : 10007
channels.provisioning-07.multicast.size : 4096
channels.provisioning-07.multicast.ttl : 1
channels.provisioning-07.multicast.throttle : 10000000
channels.provisioning-07.multicast.wastegate : 100000
channels.provisioning-08.file : {system.home}/
distribution/provisioning-08
channels.provisioning-08.interface : {host.name}
channels.provisioning-08.registrar.address : {host.address}
channels.provisioning-08.registrar.port : 10008
channels.provisioning-08.multicast.address : 239.192.0.132
channels.provisioning-08.multicast.port : 10008
channels.provisioning-08.multicast.size : 1446
channels.provisioning-08.multicast.ttl : 1
channels.provisioning-08.multicast.throttle : 10000000
channels.provisioning-08.multicast.wastegate : 100000
channels.provisioning-09.file : {system.home}/
distribution/provisioning-09
channels.provisioning-09.interface : {host.name}
channels.provisioning-09.registrar.address : {host.address}
channels.provisioning-09.registrar.port : 10009
channels.provisioning-09.multicast.address : 239.192.0.132
channels.provisioning-09.multicast.port : 10009
channels.provisioning-09.multicast.size : 4096
channels.provisioning-09.multicast.ttl : 1
channels.provisioning-09.multicast.throttle : 10000000
channels.provisioning-09.multicast.wastegate : 100000
channels.provisioning-10.file : {system.home}/
distribution/provisioning-10
channels.provisioning-10.interface : {host.name}
channels.provisioning-10.registrar.address : {host.address}
channels.provisioning-10.registrar.port : 10010
channels.provisioning-10.multicast.address : 239.192.0.133
channels.provisioning-10.multicast.port : 10010
channels.provisioning-10.multicast.size : 1446
channels.provisioning-10.multicast.ttl : 1
channels.provisioning-10.multicast.throttle : 10000000
channels.provisioning-10.multicast.wastegate : 100000
channels.provisioning-11.file : {system.home}/
distribution/provisioning-11
channels.provisioning-11.interface : {host.name}
channels.provisioning-11.registrar.address : {host.address}
channels.provisioning-11.registrar.port : 10011
channels.provisioning-11.multicast.address : 239.192.0.133
channels.provisioning-11.multicast.port : 10011
channels.provisioning-11.multicast.size : 4096
channels.provisioning-11.multicast.ttl : 1
channels.provisioning-11.multicast.throttle : 10000000
channels.provisioning-11.multicast.wastegate : 100000
channels.provisioning-12.file : {system.home}/
distribution/provisioning-12
channels.provisioning-12.interface : {host.name}
channels.provisioning-12.registrar.address : {host.address}
channels.provisioning-12.registrar.port : 10012
channels.provisioning-12.multicast.address : 239.192.0.134
channels.provisioning-12.multicast.port : 10012
channels.provisioning-12.multicast.size : 1446
channels.provisioning-12.multicast.ttl : 1
channels.provisioning-12.multicast.throttle : 10000000
channels.provisioning-12.multicast.wastegate : 100000
channels.provisioning-13.file : {system.home}/
distribution/provisioning-13
channels.provisioning-13.interface : {host.name}
channels.provisioning-13.registrar.address : {host.address}
channels.provisioning-13.registrar.port : 10013
channels.provisioning-13.multicast.address : 239.192.0.134
channels.provisioning-13.multicast.port : 10013
channels.provisioning-13.multicast.size : 4096
channels.provisioning-13.multicast.ttl : 1
channels.provisioning-13.multicast.throttle : 10000000
channels.provisioning-13.multicast.wastegate : 100000
channels.provisioning-14.file : {system.home}/
distribution/provisioning-14
channels.provisioning-14.interface : {host.name}
channels.provisioning-14.registrar.address : {host.address}
channels.provisioning-14.registrar.port : 10014
channels.provisioning-14.multicast.address : 239.192.0.135
channels.provisioning-14.multicast.port : 10014
channels.provisioning-14.multicast.size : 1446
channels.provisioning-14.multicast.ttl : 1
channels.provisioning-14.multicast.throttle : 10000000
channels.provisioning-14.multicast.wastegate : 100000
channels.provisioning-15.file : {system.home}/
distribution/provisioning-15
channels.provisioning-15.interface : {host.name}
channels.provisioning-15.registrar.address : {host.address}
channels.provisioning-15.registrar.port : 10015
channels.provisioning-15.multicast.address : 239.192.0.135
channels.provisioning-15.multicast.port : 10015
channels.provisioning-15.multicast.size : 4096
channels.provisioning-15.multicast.ttl : 1
channels.provisioning-15.multicast.throttle : 10000000
channels.provisioning-15.multicast.wastegate : 100000
channels.provisioning-16.file : {system.home}/
distribution/provisioning-16
channels.provisioning-16.interface : {host.name}
channels.provisioning-16.registrar.address : {host.address}
channels.provisioning-16.registrar.port : 10016
channels.provisioning-16.multicast.address : 239.192.0.136
channels.provisioning-16.multicast.port : 10016
channels.provisioning-16.multicast.size : 1446
channels.provisioning-16.multicast.ttl : 1
channels.provisioning-16.multicast.throttle : 10000000
channels.provisioning-16.multicast.wastegate : 100000
channels.provisioning-17.file : {system.home}/
distribution/provisioning-17
channels.provisioning-17.interface : {host.name}
channels.provisioning-17.registrar.address : {host.address}
channels.provisioning-17.registrar.port : 10017
channels.provisioning-17.multicast.address : 239.192.0.136
channels.provisioning-17.multicast.port : 10017
channels.provisioning-17.multicast.size : 4096
channels.provisioning-17.multicast.ttl : 1
channels.provisioning-17.multicast.throttle : 10000000
channels.provisioning-17.multicast.wastegate : 100000
channels.provisioning-18.file : {system.home}/
distribution/provisioning-18
channels.provisioning-18.interface : {host.name}
channels.provisioning-18.registrar.address : {host.address}
channels.provisioning-18.registrar.port : 10018
channels.provisioning-18.multicast.address : 239.192.0.137
channels.provisioning-18.multicast.port : 10018
channels.provisioning-18.multicast.size : 1446
channels.provisioning-18.multicast.ttl : 1
channels.provisioning-18.multicast.throttle : 10000000
channels.provisioning-18.multicast.wastegate : 100000
channels.provisioning-19.file : {system.home}/
distribution/provisioning-19
channels.provisioning-19.interface : {host.name}
channels.provisioning-19.registrar.address : {host.address}
channels.provisioning-19.registrar.port : 10019
channels.provisioning-19.multicast.address : 239.192.0.137
channels.provisioning-19.multicast.port : 10019
channels.provisioning-19.multicast.size : 4096
channels.provisioning-19.multicast.ttl : 1
channels.provisioning-19.multicast.throttle : 10000000
channels.provisioning-19.multicast.wastegate : 100000
On Apr 2, 12:01 pm, "Siekas, Greg" <greg.sie...@boeing.com> wrote:
> Did you lose your multicast settings on the headnode?
>
> What does netstat -rn show?
> What's in /opt/cwx/etc/DistributionService.profile?
>
> Greg
>
>
>
> -----Original Message-----
> From: Arcadian [mailto:bharath.ramachand...@gmail.com]
> Sent: Thursday, April 02, 2009 11:59 AM
> To: Linux Networx Users Group
> Subject: [lnxiug] clusterworx imaging problem
>
> While imaging a few nodes using clusterworx, we are unable to get past
> the "Loading x-slam" step. It seems to take forever with only "..."
> being added to the console output. Does anybody know what the problem
> could be?
>
> Here is the console output (original IPs not shown):
>
> ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
> (GPL)http://etherboot.orgTagged ELF64 ELF with TFTP SLAM LACP for
Destination Gateway Genmask Flags MSS Window
irtt Iface
10.220.2.0 0.0.0.0 255.255.255.0 U 0 0
0 eth1
239.192.0.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
192.168.13.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo
0.0.0.0 10.220.2.200 0.0.0.0 UG 0 0
0 eth1
~ 1020> ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:81:2D:EE:0A
inet addr:192.168.13.250 Bcast:192.168.13.255 Mask:
255.255.255.0
inet6 addr: fe80::2e0:81ff:fe2d:ee0a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30446526 errors:0 dropped:0 overruns:0 frame:0
TX packets:22600358 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3606250962 (3439.1 Mb) TX bytes:3483576444 (3322.1
Mb)
Interrupt:24
eth1 Link encap:Ethernet HWaddr 00:0A:5E:53:C1:3E
inet addr:10.220.2.73 Bcast:10.220.2.255 Mask:
255.255.255.0
inet6 addr: fe80::20a:5eff:fe53:c13e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3050061 errors:0 dropped:0 overruns:0 frame:0
TX packets:2967306 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:442221007 (421.7 Mb) TX bytes:2689086570 (2564.5
Mb)
Interrupt:16 Memory:ff3f4000-0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2939237 errors:0 dropped:0 overruns:0 frame:0
TX packets:2939237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2976045408 (2838.1 Mb) TX bytes:2976045408 (2838.1
Mb)
~ 1021> cat /opt/cwx/etc/DistributionService.profile
channels.provisioning-00.file : {system.home}/
distribution/provisioning-00
channels.provisioning-00.interface : {host.name}
channels.provisioning-00.registrar.address : {host.address}
channels.provisioning-00.registrar.port : 10000
channels.provisioning-00.multicast.address : 239.192.0.128
channels.provisioning-00.multicast.port : 10000
channels.provisioning-00.multicast.size : 1446
channels.provisioning-00.multicast.ttl : 1
channels.provisioning-00.multicast.throttle : 10000000
channels.provisioning-00.multicast.wastegate : 100000
channels.provisioning-01.file : {system.home}/
distribution/provisioning-01
channels.provisioning-01.interface : {host.name}
channels.provisioning-01.registrar.address : {host.address}
channels.provisioning-01.registrar.port : 10001
channels.provisioning-01.multicast.address : 239.192.0.128
channels.provisioning-01.multicast.port : 10001
channels.provisioning-01.multicast.size : 4096
channels.provisioning-01.multicast.ttl : 1
channels.provisioning-01.multicast.throttle : 10000000
channels.provisioning-01.multicast.wastegate : 100000
channels.provisioning-02.file : {system.home}/
distribution/provisioning-02
channels.provisioning-02.interface : {host.name}
channels.provisioning-02.registrar.address : {host.address}
channels.provisioning-02.registrar.port : 10002
channels.provisioning-02.multicast.address : 239.192.0.129
channels.provisioning-02.multicast.port : 10002
channels.provisioning-02.multicast.size : 1446
channels.provisioning-02.multicast.ttl : 1
channels.provisioning-02.multicast.throttle : 10000000
channels.provisioning-02.multicast.wastegate : 100000
channels.provisioning-03.file : {system.home}/
distribution/provisioning-03
channels.provisioning-03.interface : {host.name}
channels.provisioning-03.registrar.address : {host.address}
channels.provisioning-03.registrar.port : 10003
channels.provisioning-03.multicast.address : 239.192.0.129
channels.provisioning-03.multicast.port : 10003
channels.provisioning-03.multicast.size : 4096
channels.provisioning-03.multicast.ttl : 1
channels.provisioning-03.multicast.throttle : 10000000
channels.provisioning-03.multicast.wastegate : 100000
channels.provisioning-04.file : {system.home}/
distribution/provisioning-04
channels.provisioning-04.interface : {host.name}
channels.provisioning-04.registrar.address : {host.address}
channels.provisioning-04.registrar.port : 10004
channels.provisioning-04.multicast.address : 239.192.0.130
channels.provisioning-04.multicast.port : 10004
channels.provisioning-04.multicast.size : 1446
channels.provisioning-04.multicast.ttl : 1
channels.provisioning-04.multicast.throttle : 10000000
channels.provisioning-04.multicast.wastegate : 100000
channels.provisioning-05.file : {system.home}/
distribution/provisioning-05
channels.provisioning-05.interface : {host.name}
channels.provisioning-05.registrar.address : {host.address}
channels.provisioning-05.registrar.port : 10005
channels.provisioning-05.multicast.address : 239.192.0.130
channels.provisioning-05.multicast.port : 10005
channels.provisioning-05.multicast.size : 4096
channels.provisioning-05.multicast.ttl : 1
channels.provisioning-05.multicast.throttle : 10000000
channels.provisioning-05.multicast.wastegate : 100000
channels.provisioning-06.file : {system.home}/
distribution/provisioning-06
channels.provisioning-06.interface : {host.name}
channels.provisioning-06.registrar.address : {host.address}
channels.provisioning-06.registrar.port : 10006
channels.provisioning-06.multicast.address : 239.192.0.131
channels.provisioning-06.multicast.port : 10006
channels.provisioning-06.multicast.size : 1446
channels.provisioning-06.multicast.ttl : 1
channels.provisioning-06.multicast.throttle : 10000000
channels.provisioning-06.multicast.wastegate : 100000
channels.provisioning-07.file : {system.home}/
distribution/provisioning-07
channels.provisioning-07.interface : {host.name}
channels.provisioning-07.registrar.address : {host.address}
channels.provisioning-07.registrar.port : 10007
channels.provisioning-07.multicast.address : 239.192.0.131
channels.provisioning-07.multicast.port : 10007
channels.provisioning-07.multicast.size : 4096
channels.provisioning-07.multicast.ttl : 1
channels.provisioning-07.multicast.throttle : 10000000
channels.provisioning-07.multicast.wastegate : 100000
channels.provisioning-08.file : {system.home}/
distribution/provisioning-08
channels.provisioning-08.interface : {host.name}
channels.provisioning-08.registrar.address : {host.address}
channels.provisioning-08.registrar.port : 10008
channels.provisioning-08.multicast.address : 239.192.0.132
channels.provisioning-08.multicast.port : 10008
channels.provisioning-08.multicast.size : 1446
channels.provisioning-08.multicast.ttl : 1
channels.provisioning-08.multicast.throttle : 10000000
channels.provisioning-08.multicast.wastegate : 100000
channels.provisioning-09.file : {system.home}/
distribution/provisioning-09
channels.provisioning-09.interface : {host.name}
channels.provisioning-09.registrar.address : {host.address}
channels.provisioning-09.registrar.port : 10009
channels.provisioning-09.multicast.address : 239.192.0.132
channels.provisioning-09.multicast.port : 10009
channels.provisioning-09.multicast.size : 4096
channels.provisioning-09.multicast.ttl : 1
channels.provisioning-09.multicast.throttle : 10000000
channels.provisioning-09.multicast.wastegate : 100000
channels.provisioning-10.file : {system.home}/
distribution/provisioning-10
channels.provisioning-10.interface : {host.name}
channels.provisioning-10.registrar.address : {host.address}
channels.provisioning-10.registrar.port : 10010
channels.provisioning-10.multicast.address : 239.192.0.133
channels.provisioning-10.multicast.port : 10010
channels.provisioning-10.multicast.size : 1446
channels.provisioning-10.multicast.ttl : 1
channels.provisioning-10.multicast.throttle : 10000000
channels.provisioning-10.multicast.wastegate : 100000
channels.provisioning-11.file : {system.home}/
distribution/provisioning-11
channels.provisioning-11.interface : {host.name}
channels.provisioning-11.registrar.address : {host.address}
channels.provisioning-11.registrar.port : 10011
channels.provisioning-11.multicast.address : 239.192.0.133
channels.provisioning-11.multicast.port : 10011
channels.provisioning-11.multicast.size : 4096
channels.provisioning-11.multicast.ttl : 1
channels.provisioning-11.multicast.throttle : 10000000
channels.provisioning-11.multicast.wastegate : 100000
channels.provisioning-12.file : {system.home}/
distribution/provisioning-12
channels.provisioning-12.interface : {host.name}
channels.provisioning-12.registrar.address : {host.address}
channels.provisioning-12.registrar.port : 10012
channels.provisioning-12.multicast.address : 239.192.0.134
channels.provisioning-12.multicast.port : 10012
channels.provisioning-12.multicast.size : 1446
channels.provisioning-12.multicast.ttl : 1
channels.provisioning-12.multicast.throttle : 10000000
channels.provisioning-12.multicast.wastegate : 100000
channels.provisioning-13.file : {system.home}/
distribution/provisioning-13
channels.provisioning-13.interface : {host.name}
channels.provisioning-13.registrar.address : {host.address}
channels.provisioning-13.registrar.port : 10013
channels.provisioning-13.multicast.address : 239.192.0.134
channels.provisioning-13.multicast.port : 10013
channels.provisioning-13.multicast.size : 4096
channels.provisioning-13.multicast.ttl : 1
channels.provisioning-13.multicast.throttle : 10000000
channels.provisioning-13.multicast.wastegate : 100000
channels.provisioning-14.file : {system.home}/
distribution/provisioning-14
channels.provisioning-14.interface : {host.name}
channels.provisioning-14.registrar.address : {host.address}
channels.provisioning-14.registrar.port : 10014
channels.provisioning-14.multicast.address : 239.192.0.135
channels.provisioning-14.multicast.port : 10014
channels.provisioning-14.multicast.size : 1446
channels.provisioning-14.multicast.ttl : 1
channels.provisioning-14.multicast.throttle : 10000000
channels.provisioning-14.multicast.wastegate : 100000
channels.provisioning-15.file : {system.home}/
distribution/provisioning-15
channels.provisioning-15.interface : {host.name}
channels.provisioning-15.registrar.address : {host.address}
channels.provisioning-15.registrar.port : 10015
channels.provisioning-15.multicast.address : 239.192.0.135
channels.provisioning-15.multicast.port : 10015
channels.provisioning-15.multicast.size : 4096
channels.provisioning-15.multicast.ttl : 1
channels.provisioning-15.multicast.throttle : 10000000
channels.provisioning-15.multicast.wastegate : 100000
channels.provisioning-16.file : {system.home}/
distribution/provisioning-16
channels.provisioning-16.interface : {host.name}
channels.provisioning-16.registrar.address : {host.address}
channels.provisioning-16.registrar.port : 10016
channels.provisioning-16.multicast.address : 239.192.0.136
channels.provisioning-16.multicast.port : 10016
channels.provisioning-16.multicast.size : 1446
channels.provisioning-16.multicast.ttl : 1
channels.provisioning-16.multicast.throttle : 10000000
channels.provisioning-16.multicast.wastegate : 100000
channels.provisioning-17.file : {system.home}/
distribution/provisioning-17
channels.provisioning-17.interface : {host.name}
channels.provisioning-17.registrar.address : {host.address}
channels.provisioning-17.registrar.port : 10017
channels.provisioning-17.multicast.address : 239.192.0.136
channels.provisioning-17.multicast.port : 10017
channels.provisioning-17.multicast.size : 4096
channels.provisioning-17.multicast.ttl : 1
channels.provisioning-17.multicast.throttle : 10000000
channels.provisioning-17.multicast.wastegate : 100000
channels.provisioning-18.file : {system.home}/
distribution/provisioning-18
channels.provisioning-18.interface : {host.name}
channels.provisioning-18.registrar.address : {host.address}
channels.provisioning-18.registrar.port : 10018
channels.provisioning-18.multicast.address : 239.192.0.137
channels.provisioning-18.multicast.port : 10018
channels.provisioning-18.multicast.size : 1446
channels.provisioning-18.multicast.ttl : 1
channels.provisioning-18.multicast.throttle : 10000000
channels.provisioning-18.multicast.wastegate : 100000
channels.provisioning-19.file : {system.home}/
distribution/provisioning-19
channels.provisioning-19.interface : {host.name}
channels.provisioning-19.registrar.address : {host.address}
channels.provisioning-19.registrar.port : 10019
channels.provisioning-19.multicast.address : 239.192.0.137
channels.provisioning-19.multicast.port : 10019
channels.provisioning-19.multicast.size : 4096
channels.provisioning-19.multicast.ttl : 1
channels.provisioning-19.multicast.throttle : 10000000
channels.provisioning-19.multicast.wastegate : 100000
On Apr 2, 12:01 pm, "Siekas, Greg" <greg.sie...@boeing.com> wrote:
> Did you lose your multicast settings on the headnode?
>
> What does netstat -rn show?
> What's in /opt/cwx/etc/DistributionService.profile?
>
> Greg
>
>
>
> -----Original Message-----
> From: Arcadian [mailto:bharath.ramachand...@gmail.com]
> Sent: Thursday, April 02, 2009 11:59 AM
> To: Linux Networx Users Group
> Subject: [lnxiug] clusterworx imaging problem
>
> While imaging a few nodes using clusterworx, we are unable to get past
> the "Loading x-slam" step. It seems to take forever with only "..."
> being added to the console output. Does anybody know what the problem
> could be?
>
> Here is the console output (original IPs not shown):
>
> ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
> [EEPRO100][E1000][3C90X][TG3][IDE]
> Relocating _text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
> from (N)etwork (D)isk or (Q)uit?
> Probing pci nic...
> [eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
> (DHCP)...
> ..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
> xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
> 10002
> ........................................................................
> ........................................................................
> ........................................................................
> ........................................................................
> ........................................................................
> ........................................................................
> ................................................
>
> Relocating _text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
> from (N)etwork (D)isk or (Q)uit?
> Probing pci nic...
> [eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
> (DHCP)...
> ..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
> xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
> 10002
> ........................................................................
> ........................................................................
> ........................................................................
> ........................................................................
> ........................................................................
> ........................................................................
> ................................................
>
Joshua McDowell
Apr 2, 2009, 3:42:49 PM4/2/09
to lnx...@googlegroups.com
Greg is probably right, it's either the multi-cast address. Which can be temp corrected by executing "route add 239.192.0.0 ethx". Eth1 should be ethx. It could also be a provisioning cash problem too.
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 12:29:11
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 12:29:11
To: Linux Networx Users Group<lnx...@googlegroups.com>
Subject: [lnxiug] Re: clusterworx imaging problem
Siekas, Greg
Apr 2, 2009, 3:38:28 PM4/2/09
to lnx...@googlegroups.com
Simple question but is clusterworx still running? Have you tried restarting? /etc/init.d/cwx restart.
-----Original Message-----
From: Arcadian [mailto:bharath.ra...@gmail.com]
Sent: Thursday, April 02, 2009 12:29 PM
To: Linux Networx Users Group
-----Original Message-----
From: Arcadian [mailto:bharath.ra...@gmail.com]
Sent: Thursday, April 02, 2009 12:29 PM
To: Linux Networx Users Group
Subject: [lnxiug] Re: clusterworx imaging problem
Joshua McDowell
Apr 2, 2009, 3:43:52 PM4/2/09
to lnx...@googlegroups.com
Your route is in place, assuming that the internal cluster network in
on eth0 then it's OK. So either a provisioning cache problem has
struck, or something has crashed.
Joshua
on eth0 then it's OK. So either a provisioning cache problem has
struck, or something has crashed.
Joshua
Chris Slaughter
Apr 2, 2009, 3:11:09 PM4/2/09
to lnx...@googlegroups.com
I also find that restarting ClusterWorx fixes this problem as well.
It seems to go out to lunch at times.
It seems to go out to lunch at times.
Arcadian
Apr 2, 2009, 7:16:11 PM4/2/09
to Linux Networx Users Group
Restarted cwx, but that did not help. cwx status shows messages about
the service DNA.<host IP address> not responding. Any ideas?
------------------------------------------
2009-04-02 14:20:26 000-00:18:12.125 AuthenticationService
2009-04-02 14:20:26 000-00:18:12.164 DHCPService The service 'DNA.
10.220.2.73' is not responding.
The service 'DNA.127.0.0.1' is not responding.
2009-03-26 10:40:22 007-03:58:15.825 DNA.192.168.13.1
2009-03-26 09:58:12 007-04:40:25.838 DNA.192.168.13.10
2009-03-26 10:50:39 007-03:47:58.632 DNA.192.168.13.11 [....]
On Apr 2, 12:11 pm, Chris Slaughter <slaug...@slaughts.net> wrote:
> I also find that restarting ClusterWorx fixes this problem as well.
> It seems to go out to lunch at times.
>
>
>
> On Thu, Apr 2, 2009 at 3:01 PM, Siekas, Greg <greg.sie...@boeing.com> wrote:
>
> > Did you lose your multicast settings on the headnode?
>
> > What does netstat -rn show?
> > What's in /opt/cwx/etc/DistributionService.profile?
>
> > Greg
>
> > -----Original Message-----
> > From: Arcadian [mailto:bharath.ramachand...@gmail.com]
> > Sent: Thursday, April 02, 2009 11:59 AM
> > To: Linux Networx Users Group
> > Subject: [lnxiug] clusterworx imaging problem
>
> > While imaging a few nodes using clusterworx, we are unable to get past
> > the "Loading x-slam" step. It seems to take forever with only "..."
> > being added to the console output. Does anybody know what the problem
> > could be?
>
> > Here is the console output (original IPs not shown):
>
> > ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
> > (GPL)http://etherboot.orgTagged ELF64 ELF with TFTP SLAM LACP for
the service DNA.<host IP address> not responding. Any ideas?
------------------------------------------
2009-04-02 14:20:26 000-00:18:12.125 AuthenticationService
2009-04-02 14:20:26 000-00:18:12.164 DHCPService The service 'DNA.
10.220.2.73' is not responding.
The service 'DNA.127.0.0.1' is not responding.
2009-03-26 10:40:22 007-03:58:15.825 DNA.192.168.13.1
2009-03-26 09:58:12 007-04:40:25.838 DNA.192.168.13.10
2009-03-26 10:50:39 007-03:47:58.632 DNA.192.168.13.11 [....]
On Apr 2, 12:11 pm, Chris Slaughter <slaug...@slaughts.net> wrote:
> I also find that restarting ClusterWorx fixes this problem as well.
> It seems to go out to lunch at times.
>
>
>
> On Thu, Apr 2, 2009 at 3:01 PM, Siekas, Greg <greg.sie...@boeing.com> wrote:
>
> > Did you lose your multicast settings on the headnode?
>
> > What does netstat -rn show?
> > What's in /opt/cwx/etc/DistributionService.profile?
>
> > Greg
>
> > -----Original Message-----
> > From: Arcadian [mailto:bharath.ramachand...@gmail.com]
> > Sent: Thursday, April 02, 2009 11:59 AM
> > To: Linux Networx Users Group
> > Subject: [lnxiug] clusterworx imaging problem
>
> > While imaging a few nodes using clusterworx, we are unable to get past
> > the "Loading x-slam" step. It seems to take forever with only "..."
> > being added to the console output. Does anybody know what the problem
> > could be?
>
> > Here is the console output (original IPs not shown):
>
> > ROM segment 0xc800 length 0x4000 reloc 0x00020000 Etherboot 5.2.4js1
> > [EEPRO100][E1000][3C90X][TG3][IDE]
> > Relocating _text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
> > from (N)etwork (D)isk or (Q)uit?
> > Probing pci nic...
> > [eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
> > (DHCP)...
> > ..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
> > xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
> > 10002
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ................................................
>
> > Relocating _text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
> > from (N)etwork (D)isk or (Q)uit?
> > Probing pci nic...
> > [eepro100]Ethernet addr: xx:xx:xx:xx:xx:xx Searching for server
> > (DHCP)...
> > ..Me: xxx.xxx.xx.xx, Server: xxx.xxx.xx.xxx Loading x-slam://
> > xxx.xxx.xx.xxx:10002/xxx.xxx.x.xxx:
> > 10002
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ........................................................................
> > ................................................
>
Joshua McDowell
Apr 2, 2009, 7:28:48 PM4/2/09
to lnx...@googlegroups.com
killall -9 RNA
killall -9 DNA
Then restart cwx... But if you are restarting it and it doesn't respond it should get killed. What version of clusterworx are you running?
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 16:16:11
To: Linux Networx Users Group<lnx...@googlegroups.com>
> > Relocating_text from: [00029c10,00064320) to [fbec58f0,fbf00000) Boot
killall -9 DNA
Then restart cwx... But if you are restarting it and it doesn't respond it should get killed. What version of clusterworx are you running?
Joshua McDowell
-----Original Message-----
From: Arcadian <bharath.ra...@gmail.com>
Date: Thu, 2 Apr 2009 16:16:11
To: Linux Networx Users Group<lnx...@googlegroups.com>
Subject: [lnxiug] Re: clusterworx imaging problem
Chris Slaughter
Apr 2, 2009, 7:17:45 PM4/2/09
to lnx...@googlegroups.com
Did you recently change the name of the master node?
Joshua Aune
Apr 2, 2009, 10:37:04 PM4/2/09
to lnx...@googlegroups.com
Sometimes the IGMP querier switch (if in a multi switch configuration)
goes out or one of the edge switches in a multi switch configuration
gets elected as IGMP querier.
goes out or one of the edge switches in a multi switch configuration
gets elected as IGMP querier.
If you have procurv switches ensure that the central most switch from
a wiring perspective is the igmp master by changing the priority
setting to ensure it gets elected to be the master. Then try
restarting the master switch and then all the other switches.
Sometimes it takes a few minutes to resync.
Josh
Joshua McDowell
Apr 3, 2009, 10:57:17 AM4/3/09
to lnx...@googlegroups.com
can you look in the /etc/hosts file and search for "cwxhost", it should
only be assigned to one ip. Which in most cases is 192.168.0.250, you
case it probably different. If it's assigned to anything other than the
correct IP for cwxhost ( the head node ) then that could cause problems.
Also, can you do a "tcpdump -vvv -i ethx" ethx being the interface for
the local cluster. Capture a couple of minutes of that and attach it in
a file.
Thanks,
Joshua
only be assigned to one ip. Which in most cases is 192.168.0.250, you
case it probably different. If it's assigned to anything other than the
correct IP for cwxhost ( the head node ) then that could cause problems.
Also, can you do a "tcpdump -vvv -i ethx" ethx being the interface for
the local cluster. Capture a couple of minutes of that and attach it in
a file.
Thanks,
Joshua
Reply all
Reply to author
Forward
0 new messages