Closed Bug 423983 Opened 16 years ago Closed 16 years ago

symbol upload failed for 20080319 builds

Categories

(mozilla.org Graveyard :: Server Operations, task, P1)

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: samuel.sidler+old, Assigned: justdave)

References

Details

It appears all symbol uploading failed for the 20080319 builds. Now that I finally have spike up and running, I see this with Talkback and Martijn noticed it with Breakpad/Socorro as well. (e.g.: http://crash-stats.mozilla.com/report/index/8904435c-f5d1-11dc-ade2-001a4bd46e84 )
Oh, I should note, I don't see symbols for Firefox2 or Thunderbird2 for Talkback on Win32. Haven't checked other platforms but I assume this is the same (and is likely all due to the outage).
Ugh... more cleanup... Oh well. Thanks for spotting that, Sam.
Blocks: 423809
Priority: -- → P1
From the win32 build log:
Transferring symbols... /e/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/../2008031905/crashreporter-symbols-firefox-3.0b5pre-WINNT-2008031905.zip
ssh: connect to host dm-symbolpush01.mozilla.org port 22: Bad file number
lost connection
so dm-symbolpush01.m.o is down from the outage. 

Server ops, please reboot/fsck/whatever and assign back to us so that we can repush the symbols from today's nightlies.

Filed bug 423994 to add nagios checks.
Assignee: nobody → server-ops
Component: Build & Release → Server Operations
QA Contact: build → justin
"Bad file number" sounds like an error on the client end.  The server seems to be up and running, and I can connect to it fine.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
(In reply to comment #3)
> From the win32 build log:
> Transferring symbols...
> /e/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/../2008031905/crashreporter-symbols-firefox-3.0b5pre-WINNT-2008031905.zip
> ssh: connect to host dm-symbolpush01.mozilla.org port 22: Bad file number
> lost connection
> so dm-symbolpush01.m.o is down from the outage. 
> 
> Server ops, please reboot/fsck/whatever and assign back to us so that we can
> repush the symbols from today's nightlies.

Reopening, and reassigning back to us, so we can repush the symbols.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee: server-ops → nobody
Status: REOPENED → NEW
Component: Server Operations → Release Engineering: Maintenance
QA Contact: justin → release
(In reply to comment #4)
> "Bad file number" sounds like an error on the client end.  The server seems to
> be up and running, and I can connect to it fine.

Well sure, but you didn't test it from inside the build part of the network. Here's what a linux tinderbox says:

[cltbld@fx-linux-tbox ~]$ ssh -v ffxbld@dm-symbolpush01.mozilla.org
OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to dm-symbolpush01.mozilla.org [10.2.74.40] port 22.
<hang>

The firewall rule granting access must have gone away.
Assignee: nobody → server-ops
Component: Release Engineering: Maintenance → Server Operations
QA Contact: release → justin
Firefox boxes will push to stage-old so that we get symbols for the baking b5 nightlies.
Assignee: server-ops → justdave
access-list build-outbound extended permit tcp any host 10.2.74.40 eq ssh

Think that should do it.
Status: NEW → RESOLVED
Closed: 16 years ago → 16 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.