Eg, from a seamonkey box cvs -q checkout -P -r MOZILLA_1_8_BRANCH -D "10/09/2008 03:58 +0000" mozilla/client.mk Fatal error, aborting. cvsuser: no such system user but also affecting Talos and other systems using cvs.m.o to checkout. Perhaps not everything, although it's not clear since they're not checking out most of the time. Some reports from firebot's tree watcher: Firefox: 'Linux talos mozilla-central qm-plinux-trunk02' has changed state from Success to Burning. Firefox: 'Linux talos mozilla-central fast qm-plinux-fast03' has changed state from Success to Burning. Firefox: 'WINNT 6.0 talos mozilla-central nochrome qm-pvista-trunk04' has changed state from Success to Burning. Firefox3.0: 'Linux talos trunk fast qm-plinux-fast01' has changed state from Success to Burning. Mozilla1.8-SeaMonkey: 'Linux hoshi Depend (1.1)' has changed state from Success to Burning. Mozilla1.8-SeaMonkey: 'MacOSX Darwin 8.11.0 phlox Depend (1.1, Uni)' has changed state from Success to Burning. Firefox3.0: 'MacOSX Darwin 8.8.1 talos trunk qm-pmac01' has changed state from Success to Burning.
Sorry, cvs-mirror. Reed says that one of the two machines went bad, and has already been pulled off duty.
Summary: cvs.m.o responds with "cvsuser: no such system user" → cvs-mirror.m.o responds with "cvsuser: no such system user"
how long ago did you do that? the broken server was supposedly pulled from the netscaler about 10 or 15 minutes ago (it was doing that for about 5 minutes before it was caught - bug 456988 comment 10 for background.
Assignee: server-ops → justdave
Looks like firebot reports started about 21:25 PDT, the last about 21:50. There may be some lag in that due to timeouts/reporting. They're also going green again.
ok, resolved. Apparently the chroot jail configuration was set up to grab a few required libraries out of /lib64 except dn-vcs01 is not a 64-bit machine, so those libraries didn't exist and got skipped when populating the jail. Probably means the jail configuration was copied over from dm-cvs01 at some point (I don't remember doing that recently - it would have had to have been done over at some point since the last time we repopulated the jail). Fixed that to grab the 32-bit versions, repopulated the jail again, and now it all seems to work.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.