Can I get SSH or some other kind of direct file access to wp10.wordpress.net? Jen needs me to make some theme and plugin changes for connecting it to the meetup api’s, for displaying maps and party info and photos and the like.
Recent Updates Toggle Comment Threads | Keyboard Shortcuts
-
Samuel Wood (Otto)
-
John James Jacoby
Botched the commit message for: http://bbpress.trac.wordpress.org/changeset/4914/
Can it be changed to:
In bbp_search_query(), change default value of $new_args to empty array()
-
Andrew Nacin
-
Barry
This sounds like a good idea. Going to mark this one resolved.
-
-
-
Andrew Nacin
Can we please have all Trac installs updated from 1.0 to 1.0.1? In r4654-deploy, I’ve updated the wporg-svn 0005 tag and migration script.
(In particular, http://trac.edgewall.org/changeset/11319 is needed to fix the rendering of attachments ending in *.diff.)
-
Barry
Done.
-
-
Andrew Nacin
This Trac ticket is not loading: http://core.trac.wordpress.org/ticket/15058. Unicode error.
-
Barry
Looks to be some Genshi 0.7 weirdness. I downgraded to 0.6.1 and it’s working now.
-
-
Samuel Wood (Otto)
Somebody saying that their IP is “blocked from plugin and update repository”: http://wordpress.org/support/topic/ip-blocked
Don’t know if it is or not, but thought somebody could check for him.
-
Barry
Not blocked.
-
-
Andrew Nacin
We need a new VM on xen1.lax for archive.wordpress.org, which should have nginx-base but not PHP. A new wporg-archive role should have the bare minimum – just an nginx config that listens on archive.wordpress.org (SSL not needed) and serves up static files in /home/archive/public_html.
The SSH keys for coffee2code, otto42, and myself should be installed for the archive user. Ideally the user should have the ability do to the following:
- sudo /usr/bin/vim /usr/local/etc/conf.d/archive.wordpress.org.conf
- sudo /etc/init.d/nginx reload
(This has been discussed with and signed off by @barry)
-
Andrew Nacin
To move this along I started the role, see r4661-deploy.
-
Barry
https://*.wordpress.org/ now supports SPDY.
-
Robert Lilly
Awesome!
-
-
Nikolay Bachiyski
The GlotPress Trac isn’t picking up new SVN commits. It’s stuck on r745, the latest one is r746. Thanks!
-
stankea
I don’t see your commit in http://glotpress.svn.wordpress.org/
When did you commit it? Where did you commit it from?
Also, what does glotpress.svn.wordpress.org resolve to from the place you commited? -
Andrew Nacin
You can find r746 at http://svn.glotpress.org/.
These should be the same:
dig svn.glotpress.org +short 72.233.56.141 dig glotpress.svn.wordpress.org +short 66.155.40.247
Even after the DNS is updated, I think we need to make sure that all repos in LUV are forced to read-only (or push all traffic to LAX, etc.), otherwise this could happen again via bad DNS or a host header, correct?
-
Andrew Nacin
Resolved by Barry.
-
-
Ipstenu (Mika Epstein)
We’ve got an IP that can’t reach api.wordpress.org
208.113.186.134 (ours) can ping wordpress.org but not api.wordpress.org, so our poor user cannot have updates. Is there something I can do for him on our end? Or some place I can report random errors like that?
-
Barry
Hi – here is good for reports. Can you please provide traceroutes? I can reach 208.113.186.134 from api.wordpress.org without issue and there aren’t any blocks on our end.
-
Ipstenu (Mika Epstein)
Of course it’s on a shared host where traceroute is disabled. I’m getting an admin to run this for me *siiigh*
-
Ipstenu (Mika Epstein)
traceroute -T api.wordpress.org traceroute to api.wordpress.org (66.155.40.250), 30 hops max, 52 byte packets 1 ip-208-113-172-1.dreamhost.com (208.113.172.1) 3.663 ms 3.699 ms 3.713 ms 2 ip-208-113-156-13.dreamhost.com (208.113.156.13) 2.041 ms 2.088 ms 2.042 ms 3 apache2-kant.firestone.dreamhost.com (208.113.156.5) 8.904 ms 8.911 ms 8.899 ms 4 border10.tge9-1.dreamhost-2.wdc002.pnap.net (216.52.125.73) 0.370 ms 0.395 ms 0.425 ms 5 core2.te5-2-bbnet2.wdc002.pnap.net (216.52.127.72) 0.535 ms core2.te5-1-bbnet1.wdc002.pnap.net (216.52.127.8) 0.580 ms core2.te5-2-bbnet2.wdc002.pnap.net (216.52.127.72) 0.675 ms 6 * * * 7 * * * 8 * * * …
-
Barry
Here is the reverse traceroute –
traceroute -T 208.113.186.134 traceroute to 208.113.186.134 (208.113.186.134), 30 hops max, 60 byte packets 1 wordpress.org (66.155.40.2) 7.160 ms 7.640 ms 7.144 ms 2 10ge-xe-0-1-0.lax-600w-sbcor-1.peer1.net (216.187.88.37) 0.204 ms 0.216 ms 0.202 ms 3 10ge-ten3-4.la-600w-cor-1.peer1.net (216.187.88.33) 0.353 ms 0.365 ms 0.399 ms 4 10ge-ten6-1.sj-mkp2-dis-1.peer1.net (216.187.88.129) 8.506 ms 8.534 ms 8.565 ms 5 10ge.ten1-1.sj-eqx-dis-1.peer1.net (216.187.89.102) 8.867 ms 8.880 ms 8.880 ms 6 mpr1.sjc7.us (206.223.116.86) 9.641 ms 9.562 ms 9.543 ms 7 xe-0-3-0.cr1.sjc2.us.above.net (64.125.24.1) 10.115 ms 10.104 ms 10.087 ms 8 xe-1-2-0.cr1.lax112.us.above.net (64.125.29.2) 18.256 ms 25.526 ms 25.486 ms 9 xe-3-2-0.cr1.iah1.us.above.net (64.125.26.121) 74.421 ms 74.271 ms 74.222 ms 10 xe-2-1-0.cr1.dca2.us.above.net (64.125.25.113) 74.378 ms 74.784 ms 74.743 ms 11 xe-0-0-1.er1.iad10.us.above.net (64.125.31.206) 74.492 ms 74.480 ms 74.709 ms 12 xe-1-0-0.er5.iad10.us.above.net (64.125.24.133) 74.264 ms 74.845 ms 74.799 ms 13 208.185.23.134.t00867-03.above.net (208.185.23.134) 73.559 ms 73.296 ms 73.228 ms 14 ip-208-113-156-6.dreamhost.com (208.113.156.6) 75.153 ms 75.258 ms 75.233 ms 15 ip-208-113-156-14.dreamhost.com (208.113.156.14) 75.264 ms 75.106 ms 75.972 ms 16 apache2-linus.hancock.dreamhost.com (208.113.186.134) 73.779 ms 73.658 ms 73.419 ms
Are you able to reach 66.155.40.250 from any servers with an IP similar to 208.113.186.134 ? I am curious what the hop after core2.te5-2-bbnet2.wdc002.pnap.net is from a working traceroute. That will tell us where the problem is.
-
Ipstenu (Mika Epstein)
Here’s from the server next door.
# ping 66.155.40.250 -I 208.113.186.133 -n PING 66.155.40.250 (66.155.40.250) from 208.113.186.133 : 56(84) bytes of data. 64 bytes from 66.155.40.250: icmp_req=1 ttl=49 time=74.0 ms 64 bytes from 66.155.40.250: icmp_req=2 ttl=49 time=73.7 ms 64 bytes from 66.155.40.250: icmp_req=3 ttl=49 time=74.1 ms 64 bytes from 66.155.40.250: icmp_req=4 ttl=49 time=74.0 ms 64 bytes from 66.155.40.250: icmp_req=5 ttl=49 time=73.9 ms ^C --- 66.155.40.250 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4015ms rtt min/avg/max/mdev = 73.764/73.980/74.102/0.114 ms # traceroute 66.155.40.250 -I 208.113.186.133 traceroute to 66.155.40.250 (66.155.40.250), 30 hops max, 208 byte packets 1 ip-208-113-172-1.dreamhost.com (208.113.172.1) 2.220 ms 2.260 ms 2.286 ms 2 ip-208-113-156-13.dreamhost.com (208.113.156.13) 2.071 ms 2.105 ms 2.121 ms 3 apache2-kant.firestone.dreamhost.com (208.113.156.5) 0.209 ms 0.241 ms 0.239 ms 4 border10.tge9-1.dreamhost-2.wdc002.pnap.net (216.52.125.73) 0.342 ms 0.534 ms 0.534 ms 5 core2.te5-2-bbnet2.wdc002.pnap.net (216.52.127.72) 0.430 ms 0.491 ms 0.548 ms 6 12.90.32.9 (12.90.32.9) 1.261 ms 1.250 ms 1.280 ms 7 cr2.wswdc.ip.att.net (12.123.10.138) 4.384 ms 4.335 ms cr1.wswdc.ip.att.net (12.123.10.18) 4.368 ms 8 wswdc02jt.ip.att.net (12.122.88.173) 46.370 ms wswdc02jt.ip.att.net (12.122.84.81) 1.406 ms 1.426 ms 9 192.205.37.194 (192.205.37.194) 2.781 ms 2.068 ms 1.919 ms 10 xe-4-2-0.lax20.ip4.tinet.net (89.149.184.153) 68.236 ms 68.307 ms 68.305 ms 11 peer1-gw.ip4.tinet.net (77.67.70.206) 73.361 ms 73.380 ms 73.354 ms^[[A^[[A^[[A 12 * * * 13 * * * 14 wordpress.org (66.155.40.250) 73.987 ms 73.767 ms 73.731 ms
-
Barry
Ok – so it looks like the problem is at the AT&T/Internap handoff. Since you guys are an Internap customer you should reach out to their network support and ask them whats up (assuming you aren’t filtering the traffic on your end). We are not an Internap customer, so it won’t do much good for us to contact them.
-
-
Ipstenu (Mika Epstein)
Thank you, Barry. I’ll go add this to the damnit-AT&T fire.
-
Barry
Hi @ipstenu – were you able to resolve this?
-
-
-
-
Ipstenu (Mika Epstein)
Marking resolved. It looks like the DNS change caused stupidity. We dumped our cache and now it’s working for everyone (except the one guy who can’t ping anyone, but that’s clearly him-not-you)
-
-
-
Andrew Nacin
Can I have a new repository created, meta.svn.wordpress.org?
This will serve as a fresh, public repo for dotorg.svn. WP.org would eventually begin to leverage externals of meta, until eventually meta is the main checkout and dotorg is the extra stuff (like config, hyperdb, security, etc.). Its directory structure will ideally mimic dotorg.
-
Barry
Do you need a trac set up as well?
-
Andrew Nacin
Nope. It will be added to core.trac for the time being.
-
Andrew Nacin
Thus, it’s post-commit hook should be:
/usr/local/bin/trac-admin /home/trac/trac-environs/wp-core/ changeset added “meta” $2
No svnnotify at this time.
-
-
Barry
Sorry for the delay. https://meta.svn.wordpress.org/ is ready now.
-
stankea are discussing. 
What usually happens in core when there is a mistake is the cross-referenced ticket can be updated with proper information. We have *.svn.wordpress.org set up to reject property changes.