You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Tom Kwong <tk...@gmail.com> on 2019/05/23 06:35:20 UTC
quick start does not work...
Hi,
I’m getting the following error (NoNode for /brokers) on a fresh new install of kafka. There are more similar errors after that. Is there any specific requirements to run Kafka?
[2019-05-23 06:13:58,199] INFO Accepted socket connection from /127.0.0.1:47078 (org.apache.zookeeper.server.NIOServerCnxnFactory)
[2019-05-23 06:13:58,210] INFO Client attempting to establish new session at /127.0.0.1:47078 (org.apache.zookeeper.server.ZooKeeperServer)
[2019-05-23 06:13:58,213] INFO Creating new log file: log.1 (org.apache.zookeeper.server.persistence.FileTxnLog)
[2019-05-23 06:13:58,228] INFO Established session 0x1025f9887e00000 with negotiated timeout 6000 for client /127.0.0.1:47078 (org.apache.zookeeper.server.ZooKeeperServer)
[2019-05-23 06:13:58,322] INFO Got user-level KeeperException when processing sessionid:0x1025f9887e00000 type:create cxid:0x2 zxid:0x3 txntype:-1 reqpath:n/a Error Path:/brokers Error:KeeperErrorCode = NoNode for /brokers (org.apache.zookeeper.server.PrepRequestProcessor)
I’m on AWS Linux
Linux ip-172-31-4-54 4.14.88-72.76.amzn1.x86_64 #1 SMP Mon Jan 7 19:47:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Re: quick start does not work...
Posted by Tom Kwong <tk...@gmail.com>.
Typical command prompt is $ sign. That would be better than >.
Sent from my iPhone
On May 25, 2019, at 12:01 PM, Jonathan Santilli <jo...@gmail.com> wrote:
Hello Tom, It is great that you figure it out.
About the ">" is what is used to represent the prompt where the user will
type the command. Am not sure is a good idea to remove it, however there is
always room for improvement.
Cheers,
--
Jonathan
> On Sat, May 25, 2019, 6:51 PM Tom Kwong <tk...@gmail.com> wrote:
>
> OK, I've figured it out. It's a dumb mistake, and I think it may help
> others if I post how I messed it up.
>
> When I tried to copy the the instruction, it included the leading ">"
> prompt character. That's bad because it just zeroes out the
> kafka-topics.sh script!
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ > bin/kafka-topics.sh
> --create --bootstrap-server localhost:9092 --replication-factor 1
> --partitions 1 --topic test
>
> --create: command not found
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ ls -l bin/kafka-topics.sh
>
> -rwxr-xr-x 1 ubuntu ubuntu 0 May 25 17:47 *bin/kafka-topics.sh*
>
> I wasn't paying attention to the side effect and a zero-byte shell script
> is a valid script that happily does nothing.
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ bin/kafka-topics.sh --list
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$
>
> I strongly suggest the Kafka dev team remove the ">" character from the
> instruction.
>
Re: quick start does not work...
Posted by Jonathan Santilli <jo...@gmail.com>.
Hello Tom, It is great that you figure it out.
About the ">" is what is used to represent the prompt where the user will
type the command. Am not sure is a good idea to remove it, however there is
always room for improvement.
Cheers,
--
Jonathan
On Sat, May 25, 2019, 6:51 PM Tom Kwong <tk...@gmail.com> wrote:
> OK, I've figured it out. It's a dumb mistake, and I think it may help
> others if I post how I messed it up.
>
> When I tried to copy the the instruction, it included the leading ">"
> prompt character. That's bad because it just zeroes out the
> kafka-topics.sh script!
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ > bin/kafka-topics.sh
> --create --bootstrap-server localhost:9092 --replication-factor 1
> --partitions 1 --topic test
>
> --create: command not found
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ ls -l bin/kafka-topics.sh
>
> -rwxr-xr-x 1 ubuntu ubuntu 0 May 25 17:47 *bin/kafka-topics.sh*
>
> I wasn't paying attention to the side effect and a zero-byte shell script
> is a valid script that happily does nothing.
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ bin/kafka-topics.sh --list
>
> *ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$
>
> I strongly suggest the Kafka dev team remove the ">" character from the
> instruction.
>
Re: quick start does not work...
Posted by Tom Kwong <tk...@gmail.com>.
OK, I've figured it out. It's a dumb mistake, and I think it may help
others if I post how I messed it up.
When I tried to copy the the instruction, it included the leading ">"
prompt character. That's bad because it just zeroes out the
kafka-topics.sh script!
*ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ > bin/kafka-topics.sh
--create --bootstrap-server localhost:9092 --replication-factor 1
--partitions 1 --topic test
--create: command not found
*ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ ls -l bin/kafka-topics.sh
-rwxr-xr-x 1 ubuntu ubuntu 0 May 25 17:47 *bin/kafka-topics.sh*
I wasn't paying attention to the side effect and a zero-byte shell script
is a valid script that happily does nothing.
*ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$ bin/kafka-topics.sh --list
*ubuntu@ip-172-31-44-82*:*~/kafka_2.12-2.2.0*$
I strongly suggest the Kafka dev team remove the ">" character from the
instruction.
Re: quick start does not work...
Posted by Tom Kwong <tk...@gmail.com>.
I was unable to create the test topic. No error message though...
$ bin/kafka-topics.sh --create --bootstrap-server localhost:9092 --replication-factor 1 --partitions 1 --topic test
$ bin/kafka-topics.sh --list --bootstrap-server localhost:9092
$
I was curious what happens if I continue with step 4. The result: LEADER_NOT_AVAILABLE errors…
$ bin/kafka-console-producer.sh --broker-list localhost:9092 --topic test
123
>[2019-05-24 03:03:55,765] WARN [Producer clientId=console-producer] Error while fetching metadata with correlation id 1 : {test=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-05-24 03:03:55,866] WARN [Producer clientId=console-producer] Error while fetching metadata with correlation id 3 : {test=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-05-24 03:03:55,973] WARN [Producer clientId=console-producer] Error while fetching metadata with correlation id 4 : {test=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
[2019-05-24 03:03:56,080] WARN [Producer clientId=console-producer] Error while fetching metadata with correlation id 5 : {test=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
> On May 23, 2019, at 8:34 AM, Jonathan Santilli <jo...@gmail.com> wrote:
>
> Hello Tom,
>
> did you follow all the steps as instructed in the quickstart? the log is an
> INFO, while doing it, you will notice logs with the message
> "Error:KeeperErrorCode = NoNode" in different places, this is normal, is
> the way it works or how have been designed the interaction from the Broker
> to Zookeeper.
> After finishing the instructions, were you able to send and produce
> messages from the created topic?
>
> Cheers!
>
>
>
> On Thu, May 23, 2019 at 1:50 PM Tom Kwong <tk...@gmail.com> wrote:
>
>> Yes, i first noticed that it failed at step 3 (creating topic) but when I
>> reviewed the log, the error already happened by step 2.
>>
>> https://kafka.apache.org/quickstart
>>
>> On May 23, 2019, at 1:52 AM, Robin Moffatt <ro...@confluent.io> wrote:
>>
>> Hi Tom,
>>
>> Can you link to which quickstart instructions you're following?
>>
>> thanks.
>>
>>
>> --
>>
>> Robin Moffatt | Developer Advocate | robin@confluent.io | @rmoff
>>
>>
>>> On Thu, 23 May 2019 at 07:35, Tom Kwong <tk...@gmail.com> wrote:
>>>
>>> Hi,
>>> I’m getting the following error (NoNode for /brokers) on a fresh new
>>> install of kafka. There are more similar errors after that. Is there
>> any
>>> specific requirements to run Kafka?
>>>
>>> [2019-05-23 06:13:58,199] INFO Accepted socket connection from /
>>> 127.0.0.1:47078 (org.apache.zookeeper.server.NIOServerCnxnFactory)
>>> [2019-05-23 06:13:58,210] INFO Client attempting to establish new session
>>> at /127.0.0.1:47078 (org.apache.zookeeper.server.ZooKeeperServer)
>>> [2019-05-23 06:13:58,213] INFO Creating new log file: log.1
>>> (org.apache.zookeeper.server.persistence.FileTxnLog)
>>> [2019-05-23 06:13:58,228] INFO Established session 0x1025f9887e00000 with
>>> negotiated timeout 6000 for client /127.0.0.1:47078
>>> (org.apache.zookeeper.server.ZooKeeperServer)
>>> [2019-05-23 06:13:58,322] INFO Got user-level KeeperException when
>>> processing sessionid:0x1025f9887e00000 type:create cxid:0x2 zxid:0x3
>>> txntype:-1 reqpath:n/a Error Path:/brokers Error:KeeperErrorCode = NoNode
>>> for /brokers (org.apache.zookeeper.server.PrepRequestProcessor)
>>>
>>> I’m on AWS Linux
>>> Linux ip-172-31-4-54 4.14.88-72.76.amzn1.x86_64 #1 SMP Mon Jan 7 19:47:07
>>> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>>
>
>
> --
> Santilli Jonathan
Re: quick start does not work...
Posted by Jonathan Santilli <jo...@gmail.com>.
Hello Tom,
did you follow all the steps as instructed in the quickstart? the log is an
INFO, while doing it, you will notice logs with the message
"Error:KeeperErrorCode = NoNode" in different places, this is normal, is
the way it works or how have been designed the interaction from the Broker
to Zookeeper.
After finishing the instructions, were you able to send and produce
messages from the created topic?
Cheers!
On Thu, May 23, 2019 at 1:50 PM Tom Kwong <tk...@gmail.com> wrote:
> Yes, i first noticed that it failed at step 3 (creating topic) but when I
> reviewed the log, the error already happened by step 2.
>
> https://kafka.apache.org/quickstart
>
> On May 23, 2019, at 1:52 AM, Robin Moffatt <ro...@confluent.io> wrote:
>
> Hi Tom,
>
> Can you link to which quickstart instructions you're following?
>
> thanks.
>
>
> --
>
> Robin Moffatt | Developer Advocate | robin@confluent.io | @rmoff
>
>
> > On Thu, 23 May 2019 at 07:35, Tom Kwong <tk...@gmail.com> wrote:
> >
> > Hi,
> > I’m getting the following error (NoNode for /brokers) on a fresh new
> > install of kafka. There are more similar errors after that. Is there
> any
> > specific requirements to run Kafka?
> >
> > [2019-05-23 06:13:58,199] INFO Accepted socket connection from /
> > 127.0.0.1:47078 (org.apache.zookeeper.server.NIOServerCnxnFactory)
> > [2019-05-23 06:13:58,210] INFO Client attempting to establish new session
> > at /127.0.0.1:47078 (org.apache.zookeeper.server.ZooKeeperServer)
> > [2019-05-23 06:13:58,213] INFO Creating new log file: log.1
> > (org.apache.zookeeper.server.persistence.FileTxnLog)
> > [2019-05-23 06:13:58,228] INFO Established session 0x1025f9887e00000 with
> > negotiated timeout 6000 for client /127.0.0.1:47078
> > (org.apache.zookeeper.server.ZooKeeperServer)
> > [2019-05-23 06:13:58,322] INFO Got user-level KeeperException when
> > processing sessionid:0x1025f9887e00000 type:create cxid:0x2 zxid:0x3
> > txntype:-1 reqpath:n/a Error Path:/brokers Error:KeeperErrorCode = NoNode
> > for /brokers (org.apache.zookeeper.server.PrepRequestProcessor)
> >
> > I’m on AWS Linux
> > Linux ip-172-31-4-54 4.14.88-72.76.amzn1.x86_64 #1 SMP Mon Jan 7 19:47:07
> > UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>
--
Santilli Jonathan
Re: quick start does not work...
Posted by Tom Kwong <tk...@gmail.com>.
Yes, i first noticed that it failed at step 3 (creating topic) but when I reviewed the log, the error already happened by step 2.
https://kafka.apache.org/quickstart
On May 23, 2019, at 1:52 AM, Robin Moffatt <ro...@confluent.io> wrote:
Hi Tom,
Can you link to which quickstart instructions you're following?
thanks.
--
Robin Moffatt | Developer Advocate | robin@confluent.io | @rmoff
> On Thu, 23 May 2019 at 07:35, Tom Kwong <tk...@gmail.com> wrote:
>
> Hi,
> I’m getting the following error (NoNode for /brokers) on a fresh new
> install of kafka. There are more similar errors after that. Is there any
> specific requirements to run Kafka?
>
> [2019-05-23 06:13:58,199] INFO Accepted socket connection from /
> 127.0.0.1:47078 (org.apache.zookeeper.server.NIOServerCnxnFactory)
> [2019-05-23 06:13:58,210] INFO Client attempting to establish new session
> at /127.0.0.1:47078 (org.apache.zookeeper.server.ZooKeeperServer)
> [2019-05-23 06:13:58,213] INFO Creating new log file: log.1
> (org.apache.zookeeper.server.persistence.FileTxnLog)
> [2019-05-23 06:13:58,228] INFO Established session 0x1025f9887e00000 with
> negotiated timeout 6000 for client /127.0.0.1:47078
> (org.apache.zookeeper.server.ZooKeeperServer)
> [2019-05-23 06:13:58,322] INFO Got user-level KeeperException when
> processing sessionid:0x1025f9887e00000 type:create cxid:0x2 zxid:0x3
> txntype:-1 reqpath:n/a Error Path:/brokers Error:KeeperErrorCode = NoNode
> for /brokers (org.apache.zookeeper.server.PrepRequestProcessor)
>
> I’m on AWS Linux
> Linux ip-172-31-4-54 4.14.88-72.76.amzn1.x86_64 #1 SMP Mon Jan 7 19:47:07
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Re: quick start does not work...
Posted by Robin Moffatt <ro...@confluent.io>.
Hi Tom,
Can you link to which quickstart instructions you're following?
thanks.
--
Robin Moffatt | Developer Advocate | robin@confluent.io | @rmoff
On Thu, 23 May 2019 at 07:35, Tom Kwong <tk...@gmail.com> wrote:
> Hi,
> I’m getting the following error (NoNode for /brokers) on a fresh new
> install of kafka. There are more similar errors after that. Is there any
> specific requirements to run Kafka?
>
> [2019-05-23 06:13:58,199] INFO Accepted socket connection from /
> 127.0.0.1:47078 (org.apache.zookeeper.server.NIOServerCnxnFactory)
> [2019-05-23 06:13:58,210] INFO Client attempting to establish new session
> at /127.0.0.1:47078 (org.apache.zookeeper.server.ZooKeeperServer)
> [2019-05-23 06:13:58,213] INFO Creating new log file: log.1
> (org.apache.zookeeper.server.persistence.FileTxnLog)
> [2019-05-23 06:13:58,228] INFO Established session 0x1025f9887e00000 with
> negotiated timeout 6000 for client /127.0.0.1:47078
> (org.apache.zookeeper.server.ZooKeeperServer)
> [2019-05-23 06:13:58,322] INFO Got user-level KeeperException when
> processing sessionid:0x1025f9887e00000 type:create cxid:0x2 zxid:0x3
> txntype:-1 reqpath:n/a Error Path:/brokers Error:KeeperErrorCode = NoNode
> for /brokers (org.apache.zookeeper.server.PrepRequestProcessor)
>
> I’m on AWS Linux
> Linux ip-172-31-4-54 4.14.88-72.76.amzn1.x86_64 #1 SMP Mon Jan 7 19:47:07
> UTC 2019 x86_64 x86_64 x86_64 GNU/Linux