Status

P3
blocker
RESOLVED FIXED
19 years ago
4 years ago

People

(Reporter: BenB, Assigned: drew.streib)

Tracking

Details

(Reporter)

Description

19 years ago
I'm getting things like

cvs [server aborted]: cannot open /tmp/cvsPr9s6F: No space left on device

and partly garbage data from cvs-mirror. Assuming I can trust |df|, I have
enough space.

Also,

$ nslookup 198.186.203.47
Server:  ns.de.uu.net
Address:  192.76.144.66
Name:    cvs-mirror.mozilla.org
Address:  198.186.203.47

looks odd to me, as mozilla.org servers
- used to have name of lizards
- are usually in the 207.200.73.0/255.255.255.0 net

Comment 1

19 years ago
Same here, but I get all sorts of 'cvs [server aborted]: cannot open
CVS/Entries.Log: No space left on device' messages. Definitively something fishy
going on.
(Reporter)

Comment 2

19 years ago
cvs-mirror being at sourceforge seems to be OK. REASSIGNing to
<dtype@sourceforge.net>.
Assignee: rko → dtype

Comment 3

19 years ago
I'm rebooting the server. Hopefully it comes back up. The load average was > 40 
but didn't quickly see much else wrong except some kernel panic messages.

Comment 4

19 years ago
Ok, looks good now.

Comment 5

19 years ago
I also run rsync with -c (runs every night anyway) to make sure files are 
identical.

Drew, I'm leaving this open - please close when you've seen it and ack'd.
(Reporter)

Comment 6

19 years ago
What was the problem (to make sure it doesn't happen again)?

Comment 7

19 years ago
I don't know. Load was > 40. I bounced inetd, no help. I killed all cvs 
processes, no help. I'm leaving it to Sourceforge/Drew to determine because it's 
their server.
(Reporter)

Comment 8

19 years ago
BTW: rko, thanks for the fast hotfix. At least I could co now :).
(Assignee)

Comment 9

19 years ago
Not quite sure what happened, but I'm analyzing log files now. Kernel version is
2.2.16+ (which is current). I'll monitor this closely. -drew
Status: NEW → RESOLVED
Last Resolved: 19 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.