Daryl C. W. O'Shea writes: > Justin Mason wrote: > > Here's a log from a mass-check session. It again gets stuck nearly at > > 100% with a set of 676 and 728 messages. > > Any logs from the client at 140.211.11.138 to go with this? The client > logs will likely provide a better clue to why this is happening than the > server logs.
unfortunately it's started without any noisy settings. should --progress --noisy do it? It may be best if you just re-run the mass-check yourself ;) the client is started via SSH from the 'masses/rule-qa/nightly-slave-start' script, so edit that if you like. --j.
