FYI, you're still missing a few :)

http://accumulo.apache.org/1.7/accumulo_user_manual#_network

I don't think that we're missing any though (the few I don't recognize look like other services on your system, HDFS, ZK, etc)

David Boyd wrote:
Boy I feel stupid.  I thought I had opened up all the required ports in
IPTables for this to work.

Thanks Sven and Michael

The following is what I put in IP tables to make everything accessible:

# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 2181 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 4560 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9000 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9997 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9999 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 50010 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 50020 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 50070 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 50075 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 50090 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 50091 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 50095 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT


On 5/19/16 10:50 AM, Michael Wall wrote:
David,

If you are still having problems, can you take a jstack of the process
while it is hung and send it?

Mike

On Thu, May 19, 2016 at 9:59 AM, Sven Hodapp
<[email protected]
<mailto:[email protected]>> wrote:

    Hi David,

    I had the same issue. I've found out to modify table configuration
    in client code the master server must be available.
    You have said, that you already altered the configuration, but
    maybe the master is nevertheless inaccessible for the client?

    Regards,
    Sven

    --
    Sven Hodapp, M.Sc.,
    Fraunhofer Institute for Algorithms and Scientific Computing SCAI,
    Department of Bioinformatics
    Schloss Birlinghoven, 53754 Sankt Augustin, Germany
    [email protected] <mailto:[email protected]>
    www.scai.fraunhofer.de <http://www.scai.fraunhofer.de>

    ----- Ursprüngliche Mail -----
    > Von: "David Boyd" <[email protected]
    <mailto:[email protected]>>
    > An: "user" <[email protected]
    <mailto:[email protected]>>
    > CC: "Jing Yang" <[email protected]
    <mailto:[email protected]>>
    > Gesendet: Donnerstag, 19. Mai 2016 15:22:26
    > Betreff: tableOperations().create hangs

    > Hello:
    >
    >     I have the following code in one of my methods:
    >
    > if(!dbConnector.tableOperations().exists(coalesceTable)) {
    >                 System.err.println("creating table " +
    coalesceTable);
    > dbConnector.tableOperations().create(coalesceTable);
    >                 System.err.println("created table " +
    coalesceTable);
    >             }
    >
    > The exists call works just fine.  If the table exists (e.g. I
    created it
    > from the accumulo shell)
    > the code moves on and writes to the table just fine.
    >
    > If the table does not exist the create call is called and the entire
    > process hangs.
    >
    > This same code works just fine using MiniAccumuloCluster in my
    junit test.
    >
    > My accumlo is a single node 1.6.1 instance running in a separate
    VM on
    > my laptop.
    >
    > I saw a similar thread
    >
    
(http://mail-archives.apache.org/mod_mbox/accumulo-dev/201310.mbox/%[email protected]%3E)
    > where the user set all the accumulo conf entries to the IP versus
    > localhost, but I had already done that.  I reverified that
    nothing in my
    > accumulo configuration
    > uses localhost.
    >
    > Any help would be appreciated.
    >
    >
    >
    > --
    > ========= mailto:[email protected]
    <mailto:[email protected]> ============
    > David W. Boyd
    > VP,  Data Solutions
    > 10432 Balls Ford, Suite 240
    > Manassas, VA 20109
    > office: +1-703-552-2862 <tel:%2B1-703-552-2862>
    > cell: +1-703-402-7908 <tel:%2B1-703-402-7908>
    > ============== http://www.incadencecorp.com/ ============
    > ISO/IEC JTC1 WG9, editor ISO/IEC 20547 Big Data Reference
    Architecture
    > Chair ANSI/INCITS TC Big Data
    > Co-chair NIST Big Data Public Working Group Reference Architecture
    > First Robotic Mentor - FRC, FTC -
    <http://www.iliterobotics.org>www.iliterobotics.org
    > Board Member- USSTEM Foundation -
    <http://www.usstem.org>www.usstem.org
    >
    > The information contained in this message may be privileged
    > and/or confidential and protected from disclosure.
    > If the reader of this message is not the intended recipient
    > or an employee or agent responsible for delivering this message
    > to the intended recipient, you are hereby notified that any
    > dissemination, distribution or copying of this communication
    > is strictly prohibited.  If you have received this communication
    > in error, please notify the sender immediately by replying to
    > this message and deleting the material from any computer.



--
=========mailto:[email protected]  ============
David W. Boyd
VP,  Data Solutions
10432 Balls Ford, Suite 240
Manassas, VA 20109
office:   +1-703-552-2862
cell:     +1-703-402-7908
==============http://www.incadencecorp.com/  ============
ISO/IEC JTC1 WG9, editor ISO/IEC 20547 Big Data Reference Architecture
Chair ANSI/INCITS TC Big Data
Co-chair NIST Big Data Public Working Group Reference Architecture
First Robotic Mentor - FRC, FTC -www.iliterobotics.org
Board Member- USSTEM Foundation -www.usstem.org

The information contained in this message may be privileged
and/or confidential and protected from disclosure.
If the reader of this message is not the intended recipient
or an employee or agent responsible for delivering this message
to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication
is strictly prohibited.  If you have received this communication
in error, please notify the sender immediately by replying to
this message and deleting the material from any computer.



Reply via email to