Last modified: 2013-11-05 13:03:40 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58594, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56594 - wikitech.wikimedia.org is inaccessible
wikitech.wikimedia.org is inaccessible
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
wmf-deployment
All All
: Highest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://wikitech.wikimedia.org/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-04 23:45 UTC by MZMcBride
Modified: 2013-11-05 13:03 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description MZMcBride 2013-11-04 23:45:45 UTC
https://wikitech.wikimedia.org/ is currently inaccessible.
Comment 1 Greg Grossmeier 2013-11-04 23:56:24 UTC
cc'ing Ryan Lane, as he's the one I know who knows how to deal with wikitech issues
Comment 2 Daniel Zahn 2013-11-05 00:21:58 UTC
works for me again. it just started working again, we don't know yet why
Comment 3 Rob Halsell 2013-11-05 00:24:59 UTC
So a few folks worked this issue, and I cannot speak for what they saw or did, only what I saw and worked on.

Virt0 reported a bunch of icinga alerts and was unresponsive.  Supposedly it was reporting a ton of packet loss before the reboot.  Then system was rebooted.

It failed to come back online properly, with alerts.  I was NOT logged into the serial console.  (Daniel would have to speak to that.)

I saw on the bonded ports (2 of them on switch) that eth0 had traffic flowing, but nothing on eth1.  Checking out more than that on the switch is beyond me ;]  (Set vlans, setup basic stuff, check very basic non bonded stuff sure, this, nope.)

Once folks reported virt0 was back, I could see traffic on both ports.
Comment 4 Daniel Zahn 2013-11-05 00:30:19 UTC
It just had about 95% packet loss and then the packet loss disappeard. That resulted in first thinking it's frozen, which it actually wasn't. It had uptime and running opendj, just puppetmaster wasn't running. And the reboot didn't change anything apparently. The problem disappeared way after that.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links