[xcat-user] Debugging communication to xCAT server
Lindsay Todd
rltodd.ml1 at gmail.com
Wed Dec 10 15:53:41 MST 2008
This didn't work.
On Tue, Dec 9, 2008 at 8:59 AM, Lissa Valletta <lissav at us.ibm.com> wrote:
> I wonder if removing this line in /etc/hosts "::1 localhost6.localdomain6
> localhost6" might help, I think htat is used for ipv6.
>
> Lissa K. Valletta
> 414/3-8
> Poughkeepsie, NY 12601
> (tie 293) 433-3102
>
>
> "Lindsay Todd" <rltodd.ml1 at gmail.com>
>
>
> "Lindsay Todd" <rltodd.ml1 at gmail.com>
> Sent by: xcat-user-bounces at lists.xcat.org
>
> 12/08/2008 05:31 PM
>
> Please respond to
> xCAT Users Mailing list <xcat-user at lists.xcat.org>
>
> To
> "xCAT Users Mailing list" <xcat-user at lists.xcat.org>
> cc
> xcat-user-bounces at lists.xcat.org
> Subject
> Re: [xcat-user] Debugging communication to xCAT server
> I've tried various things, but still no success. I'll show the
> contents of several files and tables.
>
> /etc/hosts:
>
> 127.0.0.1 localhost localhost.cluster.nic.rpi.edu
> localhost.nic.rpi.edu localhost.localdomain
> ::1 localhost6.localdomain6 localhost6
> # public
> 128.113.28.159 cemgt cemgt.cluster.nic.rpi.edu cemgt.nic.rpi.edu
> 128.113.28.173 fen-pub fen-pub.nic.rpi.edu cefen cefen.nic.rpi.edu
> # compute nodes
> 172.20.101.1 compute01 compute01.cluster.nic.rpi.edu
> 172.20.101.2 compute02 compute02.cluster.nic.rpi.edu
> 172.20.101.3 compute03 compute03.cluster.nic.rpi.edu
> 172.20.101.4 compute04 compute04.cluster.nic.rpi.edu
> 172.20.101.5 compute05 compute05.cluster.nic.rpi.edu
> 172.20.101.6 compute06 compute06.cluster.nic.rpi.edu
> 172.20.101.7 compute07 compute07.cluster.nic.rpi.edu
> 172.20.101.8 compute08 compute08.cluster.nic.rpi.edu
> 172.20.101.200 mgt mgt.cluster.nic.rpi.edu
> 172.20.101.201 fen fen.cluster.nic.rpi.edu
> 172.20.101.202 vm1dat vm1.cluster.nic.rpi.edu
> # Control network
> # bmc
> 172.29.101.200 mgt-ctl mgt-ctl.cluster.nic.rpi.edu
> 172.29.101.201 bmcmgt bmcmgt.cluster.nic.rpi.edu
> 172.29.101.1 bmc01 bmc01.cluster.nic.rpi.edu
> 172.29.101.2 bmc02 bmc02.cluster.nic.rpi.edu
> 172.29.101.3 bmc03 bmc03.cluster.nic.rpi.edu
> 172.29.101.4 bmc04 bmc04.cluster.nic.rpi.edu
> 172.29.101.5 bmc05 bmc05.cluster.nic.rpi.edu
> 172.29.101.6 bmc06 bmc06.cluster.nic.rpi.edu
> 172.29.101.7 bmc07 bmc07.cluster.nic.rpi.edu
> 172.29.101.8 bmc08 bmc08.cluster.nic.rpi.edu
> #switch
> 172.30.0.1 mgt-sw mgt-sw.cluster.nic.rpi.edu
> 172.30.0.253 pc5324 pc5324.cluster.nic.rpi.edu
>
>
> /etc/resolv.conf:
>
> nameserver 127.0.0.1
> search cluster.nic.rpi.edu nic.rpi.edu
> domain cluster.nic.rpi.edu
>
>
> site table:
>
> #key,value,comments,disable
> "xcatdport","3001",,
> "xcatiport","3002",,
> "tftpdir","/tftpboot",,
> "master","172.20.101.200",,
> "domain","cluster.nic.rpi.edu",,
> "installdir","/install",,
> "timezone","America/New_York",,
> "nameservers","172.20.101.200",,
> "ntpservers","mgt",,
> "dhcpinterfaces","mgt|eth1",,
>
>
> policy table:
>
> #priority,name,host,commands,noderange,parameters,time,rule,comments,disable
> "1","root",,,,,,"allow",,
> "2",,,"getbmcconfig",,,,"allow",,
> "3",,,"nextdestiny",,,,"allow",,
> "4",,,"getdestiny",,,,"allow",,
> "4.4",,,"getpostscript",,,,"allow",,
> "4.5",,,"getcredentials",,,,"allow",,
> "7","mgt",,,,,,"allow",,
>
>
> Currently, hostname is "mgt.cluster.nic.rpi.edu". We resolve hosts
> forward and back:
>
> # host mgt
> mgt.cluster.nic.rpi.edu has address 172.20.101.200
> [root at mgt ~]# host 172.20.101.200
> 200.101.20.172.in-addr.arpa domain name pointer mgt.
> [root at mgt ~]# hostname
> mgt.cluster.nic.rpi.edu
> [root at mgt ~]# host mgt.cluster.nic.rpi.edu
> mgt.cluster.nic.rpi.edu has address 172.20.101.200
>
>
> Finally, the network interfaces are a bit complex, as we have VLANs,
> an aliased interface, and bridges for XEN. I'll finish with the
> output of ifconfig:
>
> # ifconfig
> eth0 Link encap:Ethernet HWaddr 00:19:B9:E2:8A:A7
> inet addr:128.113.28.159 Bcast:128.113.28.255 Mask:255.255.255.0
> inet6 addr: fe80::219:b9ff:fee2:8aa7/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2176 errors:0 dropped:0 overruns:0 frame:0
> TX packets:444 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:294118 (287.2 KiB) TX bytes:65217 (63.6 KiB)
>
> eth1 Link encap:Ethernet HWaddr 00:19:B9:E2:8A:A9
> inet addr:172.20.101.200 Bcast:172.20.101.255 Mask:255.255.255.0
> inet6 addr: fe80::219:b9ff:fee2:8aa9/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:71 errors:0 dropped:0 overruns:0 frame:0
> TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:5258 (5.1 KiB) TX bytes:14459 (14.1 KiB)
>
> eth1.20 Link encap:Ethernet HWaddr 00:19:B9:E2:8A:A9
> inet addr:172.29.101.200 Bcast:172.29.101.255 Mask:255.255.255.0
> inet6 addr: fe80::219:b9ff:fee2:8aa9/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:20096 (19.6 KiB)
>
> eth1:1 Link encap:Ethernet HWaddr 00:19:B9:E2:8A:A9
> inet addr:172.30.0.1 Bcast:172.30.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> 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:5611 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5611 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1985616 (1.8 MiB) TX bytes:1985616 (1.8 MiB)
>
> peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:2506 errors:0 dropped:0 overruns:0 frame:0
> TX packets:440 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:323672 (316.0 KiB) TX bytes:66801 (65.2 KiB)
> Interrupt:18 Memory:ec000000-ec012100
>
> peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:377 errors:0 dropped:0 overruns:0 frame:0
> TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:25126 (24.5 KiB) TX bytes:19089 (18.6 KiB)
> Interrupt:18 Memory:ea000000-ea012100
>
> vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:498 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2222 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:73885 (72.1 KiB) TX bytes:297154 (290.1 KiB)
>
> vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:101 errors:0 dropped:0 overruns:0 frame:0
> TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:14459 (14.1 KiB) TX bytes:5258 (5.1 KiB)
>
> virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:8712 (8.5 KiB)
>
> xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:1639 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:227131 (221.8 KiB) TX bytes:0 (0.0 b)
>
> xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
> UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
> RX packets:46 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:10191 (9.9 KiB) TX bytes:0 (0.0 b)
>
>
>
>
> On Mon, Dec 8, 2008 at 8:52 AM, Lissa Valletta <lissav at us.ibm.com> wrote:
>> Maybe you need nameserver to be "nameserver","172.20.101.200". And also
>> is
>> DNS setup and running on your management node. I am assuming you intended
>> the management node to be your nameserver. Set domain in the site table
>> to
>> cluster.nic.rpi.edu also. I am interested that this was not setup for
>> you
>> when you installed. I have the feeling we need to see your /etc/hosts
>> and
>> /etc/resolv.conf files.
>>
>> Lissa K. Valletta
>> 414/3-8
>> Poughkeepsie, NY 12601
>> (tie 293) 433-3102
>>
>>
>> Ling Gao/Poughkeepsie/IBM at IBMUS
>>
>>
>> Ling Gao/Poughkeepsie/IBM at IBMUS
>> Sent by: xcat-user-bounces at lists.xcat.org
>>
>> 12/05/2008 03:37 PM
>>
>> Please respond to
>> xCAT Users Mailing list <xcat-user at lists.xcat.org>
>>
>> To
>> xCAT Users Mailing list <xcat-user at lists.xcat.org>
>> cc
>>
>> Subject
>> Re: [xcat-user] Debugging communication to xCAT server
>> I am not sure if this is related, but when I check my system, we use short
>> hostname (xcat20mn) for the managment node. The /etc/hosts files has an
>> entry like this:
>> 9.114.47.227 xcat20mn.clusters.com xcat20mn
>>
>> And on the site table the key for "domain' is set to ".clusters.com"
>> #tandump site
>> #key,value,comments,disable
>> "dhcpinterfaces","xcat20mn|eth0,eth1;cu03sv|eth0,eth1",,
>> "ntpservers","9.114.47.227",,
>> "nameservers","9.114.47.227,9.114.8.1,9.114.8.2",,
>> "xcatdport","3001",,
>> "xcatiport","3002",,
>> "tftpdir","/tftpboot",,
>> "installdir","/install",,
>> "master","9.114.47.227",,
>> "domain","clusters.com",,
>> "timezone","America/New_York",,
>>
>> Could you setup your the same? To change the domain name in the site
>> table,
>> run
>> chtab key=domain site.value="cluster.nic.rpi.edu"
>>
>> Also add the policy 7 back to the policy table as I mentioned before
>> chtab priority=7 policy.name="mgt" policy.rule=allow
>>
>> Then restart xcatd and see if it works.
>>
>> Ling
>>
>>
>> ---------"Lindsay Todd" <rltodd.ml1 at gmail.com> --------------------------
>>
>> Ling,
>>
>> The chtab command is accepted, even without the XCATBYPASS
>> environment -- I assume it always bypasses the server? But sadly
>> there is no change in behaviour, even after restarting xcatd, or
>> running "xcatd -f".
>>
>> Out of curiousity, I also tried "chtab priority=7
>> policy.rule=allow" after removing the previous priority 7 line -- as I
>> understand, this would allow anyone to do anything from anywhere. But
>> I still see the broken communication behaviour.
>>
>> /Lindsay
>>
>>
>>
>> On Fri, Dec 5, 2008 at 1:51 PM, Ling Gao <linggao at us.ibm.com> wrote:
>>> Could you run the following command to add a row in your policy table to
>>> see
>>> if it works.
>>> chtab priority=7 policy.name="xxxx" policy.rule=allow
>>> where xxxx is the hostname of your management node.
>>>
>>> Ling
>>>
>>> ----------------------"Lindsay Todd" <rltodd.ml1 at gmail.com>
>>> -----------------
>>>
>>> OK, here are the requested tables:
>>>
>>> # XCATBYPASS=1 tabdump site
>>> #key,value,comments,disable
>>> "xcatdport","3001",,
>>> "xcatiport","3002",,
>>> "tftpdir","/tftpboot",,
>>> "master","172.20.101.200",,
>>> "domain",,,
>>> "installdir","/install",,
>>> "timezone","America/New_York",,
>>> "nameservers","127.0.0.1",,
>>> "ntpservers","mgt",,
>>> "dhcpinterfaces","mgt|eth1",,
>>>
>>>
>>> # XCATBYPASS=1 tabdump policy
>>>
>>>
>>> #priority,name,host,commands,noderange,parameters,time,rule,comments,disable
>>> "1","root",,,,,,"allow",,
>>> "2",,,"getbmcconfig",,,,"allow",,
>>> "3",,,"nextdestiny",,,,"allow",,
>>> "4",,,"getdestiny",,,,"allow",,
>>> "4.4",,,"getpostscript",,,,"allow",,
>>> "4.5",,,"getcredentials",,,,"allow",,
>>>
>>>
>>>
>>>
>>> On Fri, Dec 5, 2008 at 12:11 PM, Ling Gao <linggao at us.ibm.com> wrote:
>>>> -------startMonitoring: product_names=
>>>> This is a debug message from monitoring code, it just means no
>>>> monitoirng
>>>> plug-in is turned on. It's a normal messages. So do not worry about this
>>>> line.
>>>>
>>>> It's line that after it that we are chasing now.
>>>>
>>>> "Bad arg length for Socket6::unpack_sockaddr_in6, length is 16, should
>>>> be
>>>> 28
>>>> at
>>>> /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Socket6.pm
>>>> line 280."
>>>>
>>>> Can you show us what's your policy table and site table look like?
>>>> tabdump policy
>>>> tabdump site
>>>>
>>>> Ling
>>>>
>>>> Ling Gao
>>>> Poughkeepsie Unix Development Lab
>>>> IBM Systems and Technology Group
>>>> Internal: T/L 293-5692
>>>> External: linggao at us.ibm.com, 845-433-5692
>>>>
>>>> "I never worry about the future. It comes soon enough." --- Albert
>>>> Einstein
>>>>
>>>> -------Lissa Valletta/Poughkeepsie/IBM at IBMUS -------------
>>>>
>>>>
>>>> There is not a more verbose logging, than you are getting. What do you
>>>> see
>>>> when you run service xcatd start . If you do not have service just start
>>>> xcatd without the -f flag. Also could you send run rpm -qa | grep xCAT
>>>> so
>>>> we
>>>> can see your level.
>>>>
>>>> The line -------startMonitoring: product_names= wich no name after
>>>> product_name bother me also.
>>>>
>>>> Lissa K. Valletta
>>>> 414/3-8
>>>> Poughkeepsie, NY 12601
>>>> (tie 293) 433-3102
>>>>
>>>> -----------Lindsay Todd" <rltodd.ml1 at gmail.com> -----------
>>>>
>>>> OK, that sounds like a promising lead. As a matter of fact, I am
>>>> using dnsmasq rather than named -- simpler configuration, so far more
>>>> likely to be configured correctly.
>>>>
>>>> On my management server, it's hostname is set to
>>>> "mgt.cluster.nic.rpi.edu", resolves to 172.20.101.200, and when I
>>>> reverse-lookup that address, I again get "mgt.cluster.nic.rpi.edu".
>>>> There are entries in /etc/host, with "mgt" listed first.
>>>> "cluster.nic.rpi.edu" is on the domain search path in
>>>> /etc/resolv.conf. Our production xCAT 1.3 cluster (which does use
>>>> named) gives similar results.
>>>>
>>>> What is xCAT 2 expecting? Is there anyway to coerce xcatd to log more
>>>> verbosely?
>>>>
>>>>
>>>> On Wed, Dec 3, 2008 at 5:51 PM, Linda Mellor <mellor at us.ibm.com> wrote:
>>>>> So, I'm wondering if you have a problem with hostname resolution. I
>>>>> seem
>>>>> to
>>>>> remember getting down that path on a different OS when the internal
>>>>> xcatd
>>>>> call to gethostbyaddr didn't return expected results. If that really is
>>>>> your
>>>>> problem, then we need to fix our code to handle the situation more
>>>>> gracefully (we had taken care of the incident I had run into, but maybe
>>>>> this
>>>>> is cropping up again in another place...).
>>>>>
>>>>> BTW, if the Socket6.pm exists, it gets called for both IPv4 and IPv6
>>>>> since
>>>>> it supports both.
>>>>>
>>>>> Linda
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -----------------------------------------------------------------------------
>>>>> Linda Mellor
>>>>> UNIX Cluster Development
>>>>> Poughkeepsie UNIX Development Lab
>>>>> mellor at us.ibm.com 845-433-7732 (tieline 293-7732)
>>>>>
>>>>> "Lindsay Todd" <rltodd.ml1 at gmail.com>
>>>>>
>>>>>
>>>>> "Lindsay Todd" <rltodd.ml1 at gmail.com>
>>>>> Sent by: xcat-user-bounces at lists.xcat.org
>>>>>
>>>>> 12/03/2008 01:55 PM
>>>>>
>>>>> Please respond to
>>>>> xCAT Users Mailing list <xcat-user at lists.xcat.org>
>>>>>
>>>>> To
>>>>> "xCAT Users Mailing list" <xcat-user at lists.xcat.org>
>>>>> cc
>>>>>
>>>>> Subject
>>>>> Re: [xcat-user] Debugging communication to xCAT server
>>>>> Looks like xcatd has a -f (foreground) switch -- I'll use that.
>>>>>
>>>>> So when I start xcatd, and do the tabdump, I see:
>>>>>
>>>>> # /opt/xcat/sbin/xcatd -f
>>>>> Shutting down vsftpd: [ OK ]
>>>>> Starting vsftpd for vsftpd: [ OK ]
>>>>> -------startMonitoring: product_names=
>>>>> Bad arg length for Socket6::unpack_sockaddr_in6, length is 16, should
>>>>> be 28 at
>>>>> /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Socket6.pm
>>>>> line 280.
>>>>>
>>>>>
>>>>> And from the command line where I do the tabdump, I see:
>>>>>
>>>>> # tabdump
>>>>> ERROR/WARNING: communication with the xCAT server seems to have been
>>>>> ended prematurely
>>>>>
>>>>> (Everything here is IPv4, by the way.)
>>>>>
>>>>> /Lindsay
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Dec 3, 2008 at 12:54 PM, Ling Gao <linggao at us.ibm.com> wrote:
>>>>>> It does not look like a certificate problem. Otherwise, you'll get a
>>>>>> different error before this.
>>>>>>
>>>>>> Now to hlep us debugging, can you run "vi /opt/xcat/sbin/xcatd",
>>>>>> (please
>>>>>> save a copy of xcatd before you doing this). search for function
>>>>>> "daemonize", then comment out the following 3 lines.
>>>>>> open STDIN, '/dev/null' or die "Can't read /dev/null: $!";
>>>>>> open STDOUT, '>/dev/null';
>>>>>> open STDERR, '>/dev/null';
>>>>>>
>>>>>> Then restart the xcatd using "service xcatd restart" command.
>>>>>> Then do tabdump command to see what errors it prints out.
>>>>>>
>>>>>> Please send us all the output includeing the ones for restarting
>>>>>> xcatd.
>>>>>>
>>>>>> Make sure undo the change after this by copying the original xcatd
>>>>>> back
>>>>>> and
>>>>>> restart the xcatd.
>>>>>>
>>>>>> Ling
>>>>>>
>>>>>> ------------"Lindsay Todd" <rltodd.ml1 at gmail.com> -----------------
>>>>>>
>>>>>> I've added a *.* /var/log/syslog line to my syslog.conf, to make sure
>>>>>> everything is caught. After restarting everything, and trying again,
>>>>>> I see that this is logged:
>>>>>>
>>>>>> Dec 3 11:26:32 mgt xCAT: xCATd: service starting
>>>>>>
>>>>>> That is it, unless there is some way to make logging more verbose. Is
>>>>>> there any way to diagnose the communication client-side as well?
>>>>>>
>>>>>> Seeing as some people had certificate issues, I re-ran xcatconfig
>>>>>> --force and I still see this problem. If I set XCATBYPASS, I can get
>>>>>> some things working again (which is reassuring, since I could dump my
>>>>>> tables this way).
>>>>>>
>>>>>> It might be worth noting that my management server is CentOS 5.2 on
>>>>>> AMD64. I maintain xCAT with the yum repositories.
>>>>>>
>>>>>> On Tue, Dec 2, 2008 at 1:55 PM, Ling Gao <linggao at us.ibm.com> wrote:
>>>>>>> The errors are logged into the syslog. Please check it.
>>>>>>> (/var/log/messages).
>>>>>>>
>>>>>>> There has been a post on this, please see if it is related.
>>>>>>> http://www.xcat.org/pipermail/xcat-user/2008-May/006372.html
>>>>>>>
>>>>>>> Ling Gao
>>>>>>> Poughkeepsie Unix Development Lab
>>>>>>> IBM Systems and Technology Group
>>>>>>> Internal: T/L 293-5692
>>>>>>> External: linggao at us.ibm.com, 845-433-5692
>>>>>>>
>>>>>>> "I never worry about the future. It comes soon enough." --- Albert
>>>>>>> Einstein
>>>>>>>
>>>>>>> -----------------"Lindsay Todd" <rltodd.ml1 at gmail.com>
>>>>>>> ------------------------
>>>>>>>
>>>>>>>
>>>>>>> Folks: I had a working xCAT 2.0 installation on a test cluster this
>>>>>>> summer.
>>>>>>>
>>>>>>> But there have been some networking changes, and updates to xCAT
>>>>>>> 2.1... At some point in time, xCAT commands stopped working. We get
>>>>>>> error messages like:
>>>>>>>
>>>>>>> # tabdump
>>>>>>> ERROR/WARNING: communication with the xCAT server seems to have been
>>>>>>> ended prematurely
>>>>>>>
>>>>>>> Where is the xCAT server logging? I don't know exactly when this
>>>>>>> stopped working, but I'd bet it is something simple, if only I knew
>>>>>>> what the server's view of the problem was...
>>>>>>> _______________________________________________
>>>>>>> xcat-user mailing list
>>>>>>> xcat-user at lists.xcat.org
>>>>>>> http://www.xcat.org/mailman/listinfo/xcat-user
>>>
>>>
>>> _______________________________________________
>>> xcat-user mailing list
>>> xcat-user at lists.xcat.org
>>> http://www.xcat.org/mailman/listinfo/xcat-user
>>>
>>>
>> _______________________________________________
>> xcat-user mailing list
>> xcat-user at lists.xcat.org
>> http://www.xcat.org/mailman/listinfo/xcat-user
>> _______________________________________________
>> xcat-user mailing list
>> xcat-user at lists.xcat.org
>> http://www.xcat.org/mailman/listinfo/xcat-user
>>
>>
>> _______________________________________________
>> xcat-user mailing list
>> xcat-user at lists.xcat.org
>> http://www.xcat.org/mailman/listinfo/xcat-user
>>
>>
> _______________________________________________
> xcat-user mailing list
> xcat-user at lists.xcat.org
> http://www.xcat.org/mailman/listinfo/xcat-user
>
>
> _______________________________________________
> xcat-user mailing list
> xcat-user at lists.xcat.org
> http://www.xcat.org/mailman/listinfo/xcat-user
>
>
More information about the xcat-user
mailing list