Elmar Pruesse wrote:
Bob Doolittle wrote:
The fact that you have "M" listed as the flag on 10.234.23.2 indicates
that it's been configured with "utadm -a", whereas the lack of "M" on
10.234.23.1 indicates that it was configured with "utadm -A". You need
to bring these into sync. I don't know if that's the root cause of your
issue but it's a place to start.
Thanks a lot, Bob!
That interface was a relic from the time the switch on the primary
network didn't want to forward multicast packets. I removed it on both
machines and now it's working again. :))
Just out of curiosity though: What does that system capacity error
message signify?
It's extremely irritating that those messages have no identifying tag so
that we know immediately where they came from.
However, it appears to be a Group Manager message that occurs when, on
Linux machines, utauthd is unable to read /proc/cpuinfo (or if it
returns more than 10k of data) to determine things like number of
processors and clock speeds in order to estimate the power of the
machine, for use in the load balancing heuristics.
/proc/cpuinfo exists on both RHEL5 and SLES10 machines I have at hand.
Does it exist on your machine? If you run "cat /proc/cpuinfo > /tmp/t;
ls -l /tmp/t" what size do you see? What kind of machine are you
running on (number of CPUs, etc)?
-Bob
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
