[xcat-user] Debugging communication to xCAT server

Ling Gao linggao at us.ibm.com
Wed Dec 3 10:54:58 MST 2008


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.xcat.org/pipermail/xcat-user/attachments/20081203/df5b6c2b/attachment.htm


More information about the xcat-user mailing list