In case anyone is interested. Our problem revolved around one machine having the phpcassa thrift patch, and the other did not. Its resolved now.
On Wed, Mar 2, 2011 at 10:25 AM, David McNelis <dmcne...@agentisenergy.com>wrote: > It looks like we are having an issue with the Thrift installation on the > 'other' machine. We spun up a cassandra instance on that machine and were > unable to connect locally through php, but I was able to connect from the > original cassandra machine with PHP. That sounds convoluted...but in short, > it looks like our main problem is with the Thrift PHP module. > > > On Wed, Mar 2, 2011 at 9:04 AM, David McNelis > <dmcne...@agentisenergy.com>wrote: > >> We are able to telnet to port 9160, and didn't have any issues resolving >> the target along those lines. So at this point, I don't think we're looking >> at a firewall / network topology issue. >> >> >> On Wed, Mar 2, 2011 at 8:54 AM, Sasha Dolgy <sdo...@gmail.com> wrote: >> >>> i had a similar issue on windows and it came down to php not being >>> able to resolve the target ... the solution was to add an entry to the >>> hosts file ... of course, if there is a firewall blocking ... that's >>> your problem. can you telnet from remote server to cassandra server >>> on port 9160? >>> >>> >>> On Wed, Mar 2, 2011 at 3:49 PM, David McNelis >>> <dmcne...@agentisenergy.com> wrote: >>> > Morning folks, >>> > I'm not sure if this is an issue with my setup of Cassandra, or with >>> > phpCassa....there is an open question on StackOverflow that is very >>> similar >>> > to what I am experiencing (1). In short, I can connect using PHP from >>> the >>> > same machine that Cassandra is running on. I can connect with >>> cassandra cli >>> > from both the "Cassandra" box and from externally. However, when I try >>> to >>> > connect using PHP (specifically phpcassa) from an external machine, I >>> get >>> > hit with a Timeout error. >>> > Both machines are running PHP 5.3 on CentOS 5. >>> > In my cassandra.yaml file I tried changing my listen_address to my >>> server's >>> > IP address instead of 127.0.0.1 and that caused me not to be able to >>> connect >>> > in general. My rpc_address is 0.0.0.0. >>> > Has anyone else experienced this or have an inclination where I'm going >>> > wrong? >>> > Thanks, >>> >> >> >> >> -- >> *David McNelis* >> Lead Software Engineer >> Agentis Energy >> www.agentisenergy.com >> o: 630.359.6395 >> c: 219.384.5143 >> >> *A Smart Grid technology company focused on helping consumers of energy >> control an often under-managed resource.* >> >> >> > > > -- > *David McNelis* > Lead Software Engineer > Agentis Energy > www.agentisenergy.com > o: 630.359.6395 > c: 219.384.5143 > > *A Smart Grid technology company focused on helping consumers of energy > control an often under-managed resource.* > > > -- *David McNelis* Lead Software Engineer Agentis Energy www.agentisenergy.com o: 630.359.6395 c: 219.384.5143 *A Smart Grid technology company focused on helping consumers of energy control an often under-managed resource.*
