failed to read command - EOF

[ssuda]

Hi,
The following message is printed by nsqd
ERROR: client - failed to read command - EOF

I see the same issue with other client libraries
nsqio/nsq#521

[casertap]

+1
I am following the instruction of this blog (it is very easy to reproduce): http://tleyden.github.io/blog/2014/11/12/an-example-of-using-nsq-from-go/

I get the same error.
here is my verbose trace:

vagrant@vagrant-ubuntu-trusty-64:~$ nsqd --verbose --lookupd-tcp-address=127.0.0.1:4160 &                     
[3] 2485
vagrant@vagrant-ubuntu-trusty-64:~$ [nsqd] 2015/09/25 13:29:13.940646 nsqd v0.3.5 (built w/go1.4.2)
[nsqd] 2015/09/25 13:29:13.941248 ID: 258
[nsqd] 2015/09/25 13:29:13.943995 TOPIC(votes): created
[nsqd] 2015/09/25 13:29:13.944763 DISKQUEUE(votes): readOne() opened votes.diskqueue.000000.dat
[nsqd] 2015/09/25 13:29:13.947648 TOPIC(write_test): created
[nsqd] 2015/09/25 13:29:13.947963 NSQ: persisting topic/channel metadata to nsqd.258.dat
[nsqd] 2015/09/25 13:29:13.947856 DISKQUEUE(write_test): readOne() opened write_test.diskqueue.000000.dat
[nsqd] 2015/09/25 13:29:13.950499 TCP: listening on [::]:4150
[nsqd] 2015/09/25 13:29:13.950940 HTTP: listening on [::]:4151                                                                                                                                     [13/1061]
[nsqd] 2015/09/25 13:29:13.952265 LOOKUP: adding peer 127.0.0.1:4160
[nsqd] 2015/09/25 13:29:13.953927 LOOKUP connecting to 127.0.0.1:4160
[nsqlookupd] 2015/09/25 13:29:13.957743 TCP: new client(127.0.0.1:57226)
[nsqlookupd] 2015/09/25 13:29:13.958545 CLIENT(127.0.0.1:57226): desired protocol magic '  V1'
[nsqlookupd] 2015/09/25 13:29:13.966164 CLIENT(127.0.0.1:57226): IDENTIFY Address:vagrant-ubuntu-trusty-64 TCP:4150 HTTP:4151 Version:0.3.5
[nsqlookupd] 2015/09/25 13:29:13.967096 DB: client(127.0.0.1:57226) REGISTER category:client key: subkey:
[nsqd] 2015/09/25 13:29:13.972373 LOOKUPD(127.0.0.1:4160): peer info {TCPPort:4160 HTTPPort:4161 Version:0.3.5 BroadcastAddress:vagrant-ubuntu-trusty-64}
[nsqd] 2015/09/25 13:29:13.973591 LOOKUPD(127.0.0.1:4160): topic REGISTER votes
[nsqlookupd] 2015/09/25 13:29:13.974467 DB: client(127.0.0.1:57226) REGISTER category:topic key:votes subkey:
[nsqd] 2015/09/25 13:29:13.974751 LOOKUPD(127.0.0.1:4160): topic REGISTER write_test
[nsqlookupd] 2015/09/25 13:29:13.975051 DB: client(127.0.0.1:57226) REGISTER category:topic key:write_test subkey:
[nsqd] 2015/09/25 13:29:13.975332 LOOKUPD(127.0.0.1:4160): REGISTER write_test
[nsqd] 2015/09/25 13:29:13.975628 LOOKUPD(127.0.0.1:4160): REGISTER votes                                                                                                                           [0/1061]
[nsqd] 2015/09/25 13:29:22.358399 TCP: new client(127.0.0.1:46688)
[nsqd] 2015/09/25 13:29:22.358428 CLIENT(127.0.0.1:46688): desired protocol magic '  V2'
[nsqd] 2015/09/25 13:29:22.360734 PROTOCOL(V2): [127.0.0.1:46688] [IDENTIFY]
[nsqd] 2015/09/25 13:29:22.362212 PROTOCOL(V2): [127.0.0.1:46688] {ShortID:vagrant-ubuntu-trusty-64 LongID:vagrant-ubuntu-trusty-64 ClientID:vagrant-ubuntu-trusty-64 Hostname:vagrant-ubuntu-trusty-64 Hear
tbeatInterval:30000 OutputBufferSize:16384 OutputBufferTimeout:250 FeatureNegotiation:true TLSv1:false Deflate:false DeflateLevel:6 Snappy:false SampleRate:0 UserAgent:go-nsq/1.0.5 MsgTimeout:0}
[nsqd] 2015/09/25 13:29:22.362558 [127.0.0.1:46688] IDENTIFY: {ShortID:vagrant-ubuntu-trusty-64 LongID:vagrant-ubuntu-trusty-64 ClientID:vagrant-ubuntu-trusty-64 Hostname:vagrant-ubuntu-trusty-64 Heartbea
tInterval:30000 OutputBufferSize:16384 OutputBufferTimeout:250 FeatureNegotiation:true TLSv1:false Deflate:false DeflateLevel:6 Snappy:false SampleRate:0 UserAgent:go-nsq/1.0.5 MsgTimeout:0}
[nsqd] 2015/09/25 13:29:22.364152 PROTOCOL(V2): [127.0.0.1:46688] [PUB write_test]
[nsqd] 2015/09/25 13:29:22.366293 PROTOCOL(V2): [127.0.0.1:46688] exiting ioloop
[nsqd] 2015/09/25 13:29:22.366412 ERROR: client(127.0.0.1:46688) - failed to read command - EOF
[nsqd] 2015/09/25 13:29:22.366685 PROTOCOL(V2): [127.0.0.1:46688] exiting messagePump

nsqd v0.3.5 (built w/go1.4.2)
nsqlookupd v0.3.5 (built w/go1.4.2)
go version go1.4 linux/amd64

[dudleycarr]

nsqjs closes the socket without sending the NSQ cls command. The end result is an error in the nsqd logs. Aside from the fact that it's being impolite, I'm not sure what other ill effects there are for not using the cls command. @mreiferson ?

[casertap]

Sorry, I wrote my comment thinking I was on the main nsqio/nsq project :-/
I am not using nsqjs, sorry to have commented here.
Should I delete this comment?

[dudleycarr]

No worries. No need to delete.

On Fri, Sep 25, 2015 at 6:47 AM casertap [email protected] wrote:

Sorry, I write my comment thinking I was on the main nsqio/nsq project :-/
I am not using nsqjs, sorry to have commented here.
Should I delete this comment?

—
Reply to this email directly or view it on GitHub
#80 (comment).