Thanks! I really appreciate you looking into this. Now that you've
confirmed the problem isn't with the VM, that makes it a lot easier to
start finding the problem.
On Wed, Dec 9, 2015 at 9:15 PM, Josh Elser wrote:
> Seems like it has something to do with you, because it worked fine for me.
>
>
Seems like it has something to do with you, because it worked fine for me.
I adapted
http://stackoverflow.com/questions/11504197/groovy-configuring-logging-properties-depending-on-environment
and it connected to Accumulo just fine.
https://paste.apache.org/egVb is the outline of the modificat
FWIW, I tried this VM as well and it failed. I forwarded the accumulo ports
with Vagrant and still nothing so it might be our corporate environment.
https://github.com/MammothData/accumulo-vagrant
On Tue, Dec 8, 2015 at 3:16 PM, Josh Elser wrote:
> Oh, well then. I didn't try running that groov
Oh, well then. I didn't try running that groovy script. I can do that
tonight :)
Mike Thomsen wrote:
The odd part is that I can do that too, but I can't connect via the
Groovy script that is in /vagrant_data (accumulo.groovy; Groovy
distribution in /vagrant_data/groovy) from outside the VM. Ins
The odd part is that I can do that too, but I can't connect via the Groovy
script that is in /vagrant_data (accumulo.groovy; Groovy distribution in
/vagrant_data/groovy) from outside the VM. Inside the VM, it works just
fine.
On Mon, Dec 7, 2015 at 11:40 PM, Josh Elser wrote:
> Mike sent me a ta
Mike sent me a tarball of his Vagrant VM.
Following my own advice (via the --debug option on the shell):
2015-12-07 23:35:50,969 [rpc.ThriftUtil] TRACE: Opening normal transport
2015-12-07 23:35:50,969 [rpc.ThriftUtil] WARN : Failed to open transport
to vagrant-ubuntu-vivid-64:9997
2015-12-07 2
Interesting. What version of Accumulo are you using?
Also, can you jstack your client application, maybe we can get a hint
where it's stuck. You could also try increase the Log4j level in your
client application for the 'org.apache.accumulo.core' package to DEBUG
or TRACE.
Even better, if th
This is the output from netstat:
vagrant@vagrant-ubuntu-vivid-64:/opt/accumulo$ netstat -nape | fgrep |
fgrep LISTEN
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp0 0 10.0.2.15: 0.0.0.0
Each line in the Accumulo "hosts" files (masters, slaves, etc) denote a
host which the process should be run on, FYI.
What does netstat show for ports and 9997? Those are the two ports
that your client should ever need to talk to for Accumulo, IIRC.
Mike Thomsen wrote:
I stopped all of
I stopped all of the services, removed localhost and even reinitialized the
node. When I brought it back up, that Groovy script hangs at the line right
after it says it's attempting to get a connection. Even Ubuntu's firewall
is turned off.
On Fri, Dec 4, 2015 at 10:50 AM, Adam Fuchs wrote:
> Mi
Mike,
I suspect if you get rid of the "localhost" line and restart Accumulo then
you will get services listening on the non-loopback IPs. Right now you have
some of your processes accessible outside your VM and others only
accessible from inside, and you probably have two tablet servers when you
s
I tried adding some read/write examples and ran into a problem. It would
hang at the first scan or write operation I tried. I checked the master
port () and it was only listening on 127.0.0.1:. netstat had two
entries for 9997. This is what conf/masters has for my VM:
# limitations under t
Thanks! That was all that I needed to do.
On Thu, Dec 3, 2015 at 3:33 PM, Josh Elser wrote:
> Could be that the Accumulo services are only listening on localhost and
> not the "external" interface for your VM. To get a connector, that's a call
> to a TabletServer which run on 9997 by default (an
Could be that the Accumulo services are only listening on localhost and
not the "external" interface for your VM. To get a connector, that's a
call to a TabletServer which run on 9997 by default (and you have open).
Do a `netstat -nape | fgrep 9997 | fgrep LISTEN` in your VM and see what
inter
14 matches
Mail list logo
