Hello,
I'd like to post a follow-up to an older message, to aid troubleshooting
in the future:
http://www.supercluster.org/pipermail/mauiusers/2006-November/002430.html
Symptoms: all commands (such as showq, diagnose, ...) fail with the
following message:
ERROR: lost connection to server
ERROR: cannot request service (status)
maui.log collects the following information (with LOGLEVEL 3):
04/30 20:27:14 INFO: connect request from 10.0.0.254
04/30 20:27:14 INFO: received service request from host
'xxxxx'
04/30 20:27:14 INFO: client socket from
'xxxxx' accepted
04/30 20:27:14 UIProcessCommand(S)
04/30 20:27:14 MSURecvData(S,5000000,TRUE,SC,EMsg)
04/30 20:27:14 MSURecvPacket(8,BufP,9,NULL,5000000,SC)
04/30 20:27:14 MSURecvPacket(8,BufP,57,NULL,5000000,SC)
04/30 20:27:14 ALERT: cannot locate timestamp
04/30 20:27:14 ALERT: cannot read client packet
04/30 20:27:14 MSUDisconnect(S)
With LOGLEVEL 1, the only logged message is "ALERT: cannot locate
timestamp".
The cause of this behavior can be described as follows:
MSU.c:1424 contains a sprintf statement which will destroy the contents
of TSLine (removing the contained, required timestamp) if compiled with
the option -D_FORTIFY_SOURCE=2. This option is added by rpmbuild on
SLES10 (and possibly other systems).
Possible workarounds:
1) Do not install from RPM, compile from source instead.
or
2) Install source RPMs and build the RPMs from them yourself. However,
first temporarily comment out the -D_FORTIFY_SOURCE=2 option in
/usr/lib/rpm/rpmrc (then build RPMs with "cd /usr/src/packages/SPECS;
rpmbuild -bb maui.spec").
I hope this will save someone some time and maybe motivate developers to
fix this issue in the source code. ;-)
-JPL
_______________________________________________
mauiusers mailing list
[email protected]
http://www.supercluster.org/mailman/listinfo/mauiusers
