Camelia, the Perl 6 bug

IRC log for #gluster-dev, 2013-05-07

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:24 nickw joined #gluster-dev
02:38 vshankar joined #gluster-dev
03:52 sahina joined #gluster-dev
03:57 shubhendu joined #gluster-dev
04:02 bala1 joined #gluster-dev
04:03 rastar joined #gluster-dev
04:22 lalatenduM joined #gluster-dev
04:26 rastar1 joined #gluster-dev
04:27 bharata joined #gluster-dev
04:39 deepakcs joined #gluster-dev
04:44 bala1 joined #gluster-dev
04:49 mohankumar__ joined #gluster-dev
05:30 rgustafs joined #gluster-dev
05:55 aravindavk joined #gluster-dev
06:03 nicolasw joined #gluster-dev
06:08 rastar joined #gluster-dev
06:31 yinyin joined #gluster-dev
08:13 a2 joined #gluster-dev
08:41 hagarth joined #gluster-dev
08:51 johnmark hagarth_: hey!
08:55 hagarth johnmark: howdy!
09:02 gbrand_ joined #gluster-dev
09:06 shubhendu joined #gluster-dev
09:06 johnmark hagarth: are you here?
09:10 hagarth johnmark: yes, now
09:10 johnmark hagarth: nice :)
09:12 johnmark hagarth: all on track for beta 1?
09:12 hagarth johnmark: looks like, will let a2 chime in too.
09:14 mohankumar__ hagarth: johnmark: ping
09:14 mohankumar__ avati has some idea about bd_map xlator
09:14 mohankumar__ i am adding multibrick bd xlator, so avati/a2 thinking should bd_map xlator be part of glusterfs
09:15 hagarth mohankumar__:  what do you think?
09:17 johnmark hagarth: I was going to ask the same thing :)
09:17 johnmark mohankumar__: advantages/disadvantages?
09:17 johnmark is it usable by someone without GlusterFS?
09:18 johnmark mohankumar__: or would you prefer to maintain it as a separate, but complementary, project?
09:18 mohankumar__ hagarth: i am not sure :)
09:20 hagarth mohankumar__:  do we have a specific use case for bd_map?
09:20 hagarth which cannot be handled by multibrick bd at all?
09:22 mohankumar__ hagarth: no
09:22 mohankumar__ with bd xlator, bd_map xlator becomes redundant and less feature also
09:24 hagarth mohankumar__: that's what I was thinking also. multibrick bd looks more cleaner in multiple aspects.
09:24 mohankumar__ hagarth: right
09:24 * mohankumar__ will be back after lunch
09:53 shubhendu joined #gluster-dev
09:56 mohankumar__ johnmark: hagarth: whats the decision about bd_map xlator?
10:02 hagarth mohankumar__: we can probably retire it once the multi-brick bd is out
10:02 mohankumar__ hagarth: ok
10:05 johnmark mohankumar__: when will that be?
10:06 mohankumar__ johnmark: i will be posting V2 of bd xlator by end of this week
10:06 mohankumar__ bd xlator works with replication
10:07 mohankumar__ but there are changes needed in dht-rebalance.c for making bd xlator working in 'distributed' environment
10:16 johnmark mohankumar__: aha, ok
10:21 aravindavk joined #gluster-dev
10:30 hagarth joined #gluster-dev
10:32 edward1 joined #gluster-dev
10:48 bala joined #gluster-dev
10:54 kkeithley1 joined #gluster-dev
11:00 hagarth1 joined #gluster-dev
11:19 bala joined #gluster-dev
11:20 shubhendu joined #gluster-dev
11:44 shubhendu joined #gluster-dev
11:50 nicolasw joined #gluster-dev
11:52 inevity joined #gluster-dev
12:00 bala joined #gluster-dev
12:09 aravindavk joined #gluster-dev
12:41 inevity joined #gluster-dev
12:48 bala joined #gluster-dev
12:50 inevity joined #gluster-dev
12:56 inevity2 joined #gluster-dev
13:05 shubhendu joined #gluster-dev
14:01 wushudoin joined #gluster-dev
14:13 deepakcs joined #gluster-dev
14:50 bala joined #gluster-dev
15:14 xavih can everyone contribute changes through gerrit ?
15:14 xavih and if so, is it possible to register without an openid account ?
15:19 Supermathie xavih: Yep, I just started the other day. And how can you *possibly* not have an openid account? :) Steam, Stack Exchange, Google, Wordpress, you must have something.
15:20 xavih Supermathie: I have an openid account, but it is personal and I would like to use another one for this (from my job)
15:21 hagarth1 xavih: you can link your work email to the openid account.
15:22 Supermathie xavih: Check out myopenid.com. Or as hagarth1 says, once you login w/ personal account you can add your work email to the review system.
15:23 Supermathie ... which is exactly what I did. ;)
15:28 xavih hagarth1, Supermathie: if I register with my personal email, will it remain private and only the linked account be visible ?
15:32 hagarth1 xavih: yes, that is possible. Only my linked work email can be added as a reviewer in gerrit.
15:33 xavih hagarth1, Supermathie: thank you very much. I'll try that :)
15:36 Supermathie avati_: Is it clear now what I'm doing with http://review.gluster.org/#/c/4917/?
15:41 wushudoin| joined #gluster-dev
15:41 avati joined #gluster-dev
15:46 bharata joined #gluster-dev
15:48 bharata avati, avati_ ping
15:49 xavih hagarth: I think I screwed up. Maybe I had registered previously, but I don't remember with which account. When I try to link my work email it says it is already in use...
15:49 a2_ joined #gluster-dev
15:49 jbautista- joined #gluster-dev
15:50 Supermathie avati needs screen I think :)
15:51 bharata avati, avati_ a2 ping
16:08 bulde joined #gluster-dev
16:27 xavih who can administrate gerrit ? I've a problem linking my work email to my account
17:29 bulde joined #gluster-dev
17:47 jclift joined #gluster-dev
18:44 kkeithley| johnmark: Re: meeting at 10PM EDT, 7PM PDT, 7:30 AM IST ??? I reminder now might be helpful for some of us!
18:46 kkeithley| s/I reminder/A reminder/
19:22 johnmark eek
19:23 johnmark kkeithley|: hagarth and I will both be presenting at that time. can you guys go ahead?
19:24 johnmark because the alternative is to wait until Wednesday, which is also fine
19:24 * johnmark will do that
20:05 avati_ johnmark: gluster-users@gluster.org email is bouncing
20:31 wushudoin joined #gluster-dev
20:34 wushudoin joined #gluster-dev
20:38 kshlm|AFK joined #gluster-dev
20:38 kshlm|AFK joined #gluster-dev
20:57 JoeJulian Probably because:
20:57 JoeJulian host -t MX gluster.org
20:57 JoeJulian gluster.org has no MX record
21:19 jclift johnmark: ^^^
21:19 jclift JoeJulian: Ugh, that sounds pretty non-optimal
21:19 * jclift raises helpdesk ticket
21:24 jclift Initial ticket submitted.  Asked for it to be Sev 2, as I *think* that's the right level for it. ;)
21:32 portante a2_: ping
21:33 portante avati_: ping
21:43 avati_ portante: pong
22:14 johnmark avati_: gluster-users is bouncing?
22:17 jclift johnmark: JoeJulian pointed out that gluster.org DNS has no MX records atm.
22:17 jclift johnmark: Created INC0049081 about it, ~45-50 mins ago
22:18 JoeJulian Most email servers will fall back to the A record, but still...
22:19 avati_ A record is giving connection refused
22:19 avati_ (connect to gluster.org[198.61.169.132]:25: Connection refused)
22:20 avati_ looks like someone turned off smtp server or addedd a firewall rule on the box?
22:22 jclift avati_: It could also be that the IP address for the A record isn't where the SMTP server is.
22:22 * jclift doesn't know
22:24 avati_ it's been the same box previously
22:24 avati_ it was always working off the A record
22:24 jclift Hmm... I just sent an email to gluster-users, and received it.
22:25 avati_ did you receive the beta1 announcement email from build.gluster.org too?
22:25 avati_ the mail made it to gluster-devel
22:25 avati_ gluster-users is still in the mailq
22:26 avati_ [root@build ~]# mailq
22:26 avati_ -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
22:26 avati_ 5486E63194      730 Tue May  7 13:03:46  jenkins@build.gluster.org
22:26 avati_ (connect to gluster.org[198.61.169.132]:25: Connection refused)
22:26 jclift avati_: Only received that on gluster-devel
22:26 avati_ gluster-users@gluster.org
22:26 avati_ -- 1 Kbytes in 1 Request.
22:26 avati_ yeah.. i suspect it's a bad firewall rule
22:26 jclift Wonder if the reason that I received it, is because of sending via internal RH network?
22:26 JoeJulian nope
22:27 JoeJulian I can telnet to it
22:27 avati_ i can't telnet to it
22:27 avati_ i think it's a bad firewall rule, filtering higher source port numbers blindly
22:28 jclift avati_: What's the IP for the authoratitive nameserver returning gluster.org records for you?
22:28 JoeJulian Should the ssh key have changed?
22:28 * jclift is wondering if there's a geo-location thing happening
22:28 jclift ssh key changed?
22:28 jclift Now that sounds potentially dodgy
22:28 JoeJulian It did
22:28 avati_ jclift: it's a TCP connection refused error
22:29 avati_ currently the source ports are in the 48xxx range
22:29 avati_ on build.gluster.org
22:29 avati_ i'm betting on bad firewall rule :p
22:29 jclift JoeJulian: Ugh.  Maybe this is an intrusion we're dealing with.  Hope not, that would suck.
22:31 avati_ [root@build ipv4]# telnet gluster.org 25
22:31 avati_ Trying 198.61.169.132...
22:31 avati_ telnet: connect to address 198.61.169.132: Connection refused
22:31 avati_ JoeJulian: was your telnet to same IP?
22:31 JoeJulian yes
22:31 jclift I can telnet to that location fine from tokyo.
22:32 jclift It's ok from London too.
22:32 avati_ i cannot telnet from my laptop either
22:32 johnmark avati_: I can telnet to :25
22:32 johnmark telnet gluster.org 25
22:32 avati_ johnmark: it's not going through from build.gluster.org or my laptop
22:33 jclift avati_: Just as a test, try telnetting to some other place on port 25, in case the firewall rule is somewhere in between.
22:33 johnmark huh
22:33 jclift i.e. maybe your isp?
22:33 JoeJulian try 587 avati_
22:33 semiosis avati_: some ISPs block port 25 outbound
22:33 semiosis jclift: +1
22:33 avati_ [root@build ipv4]# telnet gluster.org 587
22:33 avati_ Trying 198.61.169.132...
22:33 avati_ telnet: connect to address 198.61.169.132: Connection refused
22:33 JoeJulian let me make sure we're listening...
22:34 jclift avati_: Try port 22 on the host.
22:34 avati_ 22 works
22:34 hagarth joined #gluster-dev
22:34 jclift Interesting.
22:34 JoeJulian not listening... let me change that.
22:34 johnmark yeah, I can telnet to both IP address and gluster.org
22:34 avati_ oh wait, not anymore
22:34 avati_ it was working a little while ago, even 22 fails now
22:34 semiosis i can connect from my mail server in EC2 to gluster.org port 25
22:34 semiosis its open
22:35 jclift It definitely sounds like connectivity issue somewhere between avati's box and the gluster one.
22:35 jclift Hopefully not widespread. :)
22:35 johnmark oy
22:35 avati_ jclift: it's not just my box
22:35 avati_ jclift: even from build.gluster.org
22:35 johnmark avati_: that much is clear
22:36 avati_ from my laptop:
22:36 avati_ avati@darkstar:~/work/glusterfs$ telnet gluster.org 25
22:36 avati_ Trying 198.61.169.132...
22:36 avati_ telnet: connect to address 198.61.169.132: Connection timed out
22:36 JoeJulian try 587 now
22:36 semiosis http://mxtoolbox.com/SuperTool.aspx?act​ion=smtp%3agluster.org&run=toolpage
22:36 avati_ avati@darkstar:~/work/glusterfs$ telnet gluster.org 22
22:36 avati_ Trying 198.61.169.132...
22:36 avati_ Connected to gluster.org.
22:36 avati_ Escape character is '^]'.
22:36 avati_ SSH-2.0-OpenSSH_5.3
22:36 jclift JoeJulian: Just tried 587.  Port mapped to 25 now?
22:36 johnmark jbrooks: anyway, bits are live - http://download.gluster.org/pub/glust​er/glusterfs/qa-releases/3.4.0beta1/
22:37 avati_ 587 connection refused from build.gluster.org, connects from my laptop
22:37 johnmark jbrooks: feel free to respond to your original mailing list message. I need to head out
22:37 johnmark weird
22:37 JoeJulian jclift: No, just enabled it in postfix
22:37 jclift Ahhh, makes sense.
22:37 avati_ johnmark: RHEL rpms are missing there?
22:37 johnmark avati_: yeah
22:38 avati_ johnmark: who uploads to download.gluster.org?
22:38 johnmark avati_: kkeithley|, usually
22:38 johnmark kkeithley|: ping
22:38 avati_ kkeithley|: did you upload the source tarball?
22:38 johnmark avati_: it was already there when I looked
22:38 johnmark so... I assume he did
22:39 johnmark crap, intel shuttle is coming in 20 minutes... I have to get ready.
22:39 johnmark I'll be back on here in a couple of hours
22:39 jclift JoeJulian: The ssh key change still worries me btw.
22:39 JoeJulian btw, I can't ping build.gluster.org from gluster.org either.
22:39 kkeithley| avati_: yes, I did
22:39 johnmark jclift: what ssh key change? that didn't happen to me
22:40 JoeJulian jclift: I may not have logged in since it was rebuilt.
22:40 jclift *whew*
22:40 kkeithley| I was able to ssh to build.g.o
22:40 jclift JoeJulian: k, hopefully that's it then. :)
22:40 JoeJulian I can ping build from here, can ping gluster.org from here. Can't ping build from gluster.org.
22:41 JoeJulian Traceroute stops replying after te9-4.dr5.mtl.iweb.com (184.107.1.50)
22:41 kkeithley| I'm signed on to build.gluster.org. What's the problem?
22:41 kkeithley| I'm also on download.gluster.org
22:42 kkeithley| I can ping build from download
22:42 * jclift will bow out and let the other guys figure this out
22:42 jclift Am behind schedule on the bits I'm working on, but close to done
22:43 JoeJulian Can you ping gluster.org from build?
22:45 kkeithley| 10.3.129.13?
22:45 JoeJulian hosts?
22:47 JoeJulian What's that 10. address?
22:47 kkeithley| no, 198.16.169.132. No Route to host
22:48 kkeithley| I can ping 198.16.169.132 from download.g.o
22:48 JoeJulian yeah
22:48 kkeithley| from build.g.o I get no route to host
22:48 JoeJulian Which hop's reporting that?
22:49 kkeithley| sorry, Destination Port Unreachable is what I really get
22:49 JoeJulian What about a ping? Are they blocking icmp as well?
22:49 semiosis it's a strange ping that produces port unreachable
22:49 JoeJulian :P
22:50 semiosis gotta run, good luck with that
22:50 kkeithley| from build.g.o, ping 198.61.169.132 gives Dest. Port Unreachable
22:50 avati_ port unrecahable ICMP is typically in combination with TCP in response to a SYN
22:51 kkeithley| from build.g.o ping gluster.org also gives Dest. Port Unreachable, but it's pinging its own addr, 10.3.129.13
22:55 avati_ uh.. WTF added this iptables rule on build.gluster.org -
22:55 avati_ Chain OUTPUT (policy ACCEPT)
22:55 avati_ target     prot opt source               destination
22:55 avati_ REJECT     all  --  0.0.0.0/0            198.61.169.132      reject-with icmp-port-unreachable
22:55 JoeJulian Um... ok...
22:55 avati_ no trace in .bash_history
22:56 kkeithley| no sudo log?
22:56 JoeJulian there you go...
22:56 avati_ guess what.. i remove the iptables rule, mailq flushes successfully!
22:57 JoeJulian Someone should get flogged for some of the security settings on this end too. Glad I'm not administrating gluster.org.
22:57 avati_ too many people have login access here (for debugging core dumps)
22:59 JoeJulian grep /var/log/secure for sudo. Those wouldn't show up in root's bash history.
22:59 kkeithley| no smoking gun in /var/log/secure, although I didn't look at all the sudo cmds from today.
22:59 JoeJulian heh
22:59 JoeJulian I'd suggest audit.log... but I know better.
23:00 avati_ # fgrep iptables * -r
23:00 avati_ [root@build log]#
23:00 avati_ that's /var/log
23:00 kkeithley| mostly jenkins running mock, me deleting old rpm.t scratch dirs (gotta fix that test)
23:01 JoeJulian check sysconfig/iptables
23:01 kkeithley| portante did a sudo su - ???
23:01 JoeJulian would hate for that rule to come back after a reboot.
23:01 avati_ non existent
23:02 avati_ for how long has release announcement emails _not_ been coming to gluster-users?
23:02 avati_ anybody recall?
23:02 jclift What's the timestamp on /etc/sysconfig/iptables  ?
23:03 avati_ jclift: non-existent
23:03 jclift *me sighs*
23:03 jclift Urk.  I shouldn't be looking at this anyway. ;)
23:04 kkeithley| release announcements? I remember seeing the 3.4.0alpha3 announce, and I saw today's 3.4.0beta1 announce in gluster-devel at 4:03 PM EDT
23:04 avati_ kkeithley|: on gluster-users? last email?
23:04 avati_ *last announcementn email?
23:04 JoeJulian No emails in the maillog from build since as far back as April 7.
23:04 avati_ april 7 2013?
23:05 JoeJulian That's as far back as they go.
23:06 avati_ http://www.mail-archive.com/gluste​r-users@gluster.org/msg11207.html
23:07 avati_ it was working on march 6th
23:08 avati_ http://www.mail-archive.com/gluste​r-users@gluster.org/msg11410.html johnmark forwarded the announce mail from gluster-devel to gluster-users (even though the original mail had gluster-users in the to:, which means the mail had not gone through)
23:12 kkeithley| On gluster-users, nothing from Build System since March 6th, the 3.4.0alpha2 announcement
23:13 avati_ yeah, someone/something in the last couple months must have added that rule
23:14 JoeJulian Between March 6 and April 7

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary