Last modified: 2012-12-12 18:56:30 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 T45016, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43016 - bastion.wmflabs.org down
bastion.wmflabs.org down
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Highest critical
: ---
Assigned To: Ryan Lane
http://lists.wikimedia.org/pipermail/...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-12 15:54 UTC by Nemo
Modified: 2012-12-12 18:56 UTC (History)
5 users (show)

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


Attachments

Description Nemo 2012-12-12 15:54:25 UTC
I'm now getting:

ssh: Could not resolve hostname bastion.wmflabs.org: Name or service not known
ssh_exchange_identification: Connection closed by remote host

Looks like it started this morning and is on/off since then, according to labs-l.
Comment 1 Chad H. 2012-12-12 15:55:43 UTC
Worksforme, and has all morning since I saw that e-mail.
Comment 2 Nemo 2012-12-12 16:00:42 UTC
(In reply to comment #1)
> Worksforme, and has all morning since I saw that e-mail.

So maybe it's something like bug 37710 and it depends on the instance? I tried those in dumps projects as nemobis.
Comment 3 Antoine "hashar" Musso (WMF) 2012-12-12 16:03:17 UTC
I cant either:


$ ssh bastion.wmflabs.org 

If you are having access problems, please see: https://labsconsole.wikimedia.org/wiki/Access#Accessing_public_and_private_instances
Permission denied (publickey).

$
Comment 4 Ryan Lane 2012-12-12 18:55:08 UTC
Seems labs-ns1 wasn't returning results. We rebooted labs-ns0 yesterday, which would have caused queries to fail over to labs-ns1. I've fixed labs-ns1, so resolving should work again, though you probably have a negative cache for the bastion now. In an hour or so that negative cache should be gone.
Comment 5 Antoine "hashar" Musso (WMF) 2012-12-12 18:56:30 UTC
My issue with permission denied in Comment 3 was unrelated to the DNS issue. My local public key had wrong perms :(

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


Navigation
Links