[Moabusers] Moab 4.2.2 on a heterogeneous cluster
Laurence P Dawson
larry.dawson at vanderbilt.edu
Fri Aug 5 16:04:52 MDT 2005
We have added powerpc nodes to our previously purely x86 cluster. Moab
4.2.0p3 is currently running on an x86 machine along with torque 1.2.0p5
- it works fine.
When I tried to use 4.2.2p3, the powerpc machines could not talk to the
schedule server. Here is a section from the log that shows what went
wrong in response to a showq:
08/01 09:51:55 INFO: connect request from 10.0.51.1
08/01 09:51:55 INFO: received service request from host 'b1n1.vampire'
08/01 09:51:55 INFO: client socket from 'b1n1.vampire' accepted
08/01 09:51:55 MSysProcessRequest(S,FALSE)
08/01 09:51:55 MSURecvData(S,5000000,TRUE,SC,EMsg)
08/01 09:51:55 MSURecvPacket(9,BufP,9,NULL,5000000)
08/01 09:51:55 MSURecvPacket(9,BufP,359,NULL,5000000)
08/01 09:51:55 ALERT: signatures do not match
08/01 09:51:55 ALERT: cannot read client packet
08/01 09:51:55 MSUSendData(S,5000000,TRUE,TRUE)
08/01 09:51:55 INFO: packet sent (386 bytes of 386)
08/01 09:51:55 MSUDisconnect(S)
Could this be a endian issue that was introduced in 4.2.2? Any other ideas?
More information about the moabusers