Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 46023 invoked from network); 27 Apr 2010 20:34:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Apr 2010 20:34:47 -0000 Received: (qmail 34661 invoked by uid 500); 27 Apr 2010 20:34:46 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 34636 invoked by uid 500); 27 Apr 2010 20:34:46 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 34628 invoked by uid 99); 27 Apr 2010 20:34:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 20:34:46 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ryan@twitter.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pw0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 20:34:40 +0000 Received: by pwj2 with SMTP id 2so9814588pwj.31 for ; Tue, 27 Apr 2010 13:34:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.141.22.19 with SMTP id z19mr6718828rvi.250.1272400458661; Tue, 27 Apr 2010 13:34:18 -0700 (PDT) Received: by 10.140.133.1 with HTTP; Tue, 27 Apr 2010 13:34:18 -0700 (PDT) In-Reply-To: References: Date: Tue, 27 Apr 2010 13:34:18 -0700 Message-ID: Subject: Re: ThriftTransportException using Ruby Gem 0.8.2 against Cassandra 0.6.1 From: Ryan King To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Apr 27, 2010 at 1:31 PM, Lucas Di Pentima wrote: > Thanks Ryan for the fast response! Can you explain to me why binding against 127.0.0.1 causes the problem? Maybe it's useful to point this out in the documentation to avoid users deploy this kind of setups. Are you trying to talk to the cassandra host from somewhere other than the host its running on? -ryan