#weavenetwork

hi squaremo

how are you doing mate

hey guys

back to that old issue with some zookeeper instances not seeing each other..

Query: {Name:zoo1.weave.local. Qtype:1 Qclass:1}

[dns msgid 50224] Returning reply from cache: NXDOMAIN/0 answers

Query: {Name:zoo1.weave.local. Qtype:28 Qclass:1}

[dns msgid 6092] Unsuported query type AAAA

[cache msgid 6092] replacing response in cache

[dns msgid 19059] Fallback query: {Name:zoo1. Qtype:1 Qclass:1} [UDP, max:512 bytes]

... etc

zoo1 can ping zoo 1..3

zoo2 can only ping zoo 2..3

zoo3 can only ping itself..

by ip - they can all ping each other just fine...

hi yaronr

hi awh

yaronr: seems like what you are describing is https://github.com/zettio/weave/issues/494

I'm just in a process of opening an issue :)

let me vc

c

yes, I think it has to do with #494

yaronr: can you confirm the version weavedns

not sure, the 'stop the container' part never happened in my case

i.e. `sudo weave version`

hi ilya

weave script (unreleased version)

weave router git-245f74774513

weave DNS git-2500bc210aeb

weave exec git-245f74774513

yaronr: you haven't been around in a while, btw

yes. fundraising

programming presentations :)

ok, that's the same version i got

..and adding support for GCE

i.e. not 0.9.0

ah, cool

since we're all friends, if it helps - I don't mind giving you guys access to these 3 servers

yaronr: is there any reason you cannot use 0.9.0 (latest realeased version)

let me check why I didn't get the latest

yaronr: that would help, but let's verify that your issue is not related to dns cache that had been introduced recently

i have:

ExecStartPre=-/opt/weave/weave reset

ExecStartPre=-/opt/weave/weave setup

yaronr: you do have the latest pre-released version of weave

I'm not specifying a version anywhere

yaronr: what url do you get weave script from?

sec

is this incorrect?

or rather, has this changed?

yaronr: right, that's a url if you want pre-released version

for released versions you wanna use https://github.com/zettio/weave/releases/downlo...

we have introduced dns cache recently, but that hasn't been released yet

you need to curl -L https://github.com/zettio/weave/releases/downlo...

as there is one redirect to follow from that url

ok, let me tear down the cluster and start another one

thanks!

thank you :)

errordeveloper: getting '403: forbidden' from wget.

sorry, not forbidden. it's stuck - Connecting to github.com|192.30.252.128|:443.

oh it was a github issue. it's resolved now

maybe you guys should host the binaries on s3... github refusing to serve files would mean potential downtime to your users..

errordeveloper: wget with the -N flag fails on 403:forbidden (from Amazon s3!) if weave already exists

this is either a bug of github, or some new 'feature'

github is under a ddos attack now

yaronr: not that s3 never goes down...

has it?

well, one might observe that github is down a bit more often then s3

however, in fact, github release artefacts are stored in s3

github just serves redirects

you can also obtain weave script from github in the first place, but you then can put it on each of your machines in whichever way you like right?

as in, whichever is the way you trust most

because when you are obtaining remote resources it comes down to the availability of the resource

and anyhow, even if you find the best way of delivering the weave script to your machines

you still have to rely on docker registry availability

another approach to consider is distributed peer-to-peer distribution system for free software

anyhow, todays downtime of github is not really the point in time anyone is going to solve world's problems, right?

peer-to-peer has potential

errordeveloper: I'm doing: /usr/bin/wget --retry-connrefused -t 5 -N -P /opt/weave/ https://github.com/zettio/weave/releases/downlo...

and getting: HTTP request sent, awaiting response... 403 Forbidden

only from gce

works form my laptop..

errordeveloper: github issue aside, it looks like working on the latest stable release (0.9) solved the issue.

I'll let it run for a while and see if something comes up

thank you!

anyone else having trouble hitting raw.github.com?

my systemd units are trying to yank down weave and are timing out from us-west-2 @ aws

err

inconsistently

stlalpha_: https://status.github.com/

moonfish: well hell

thank you