# Aerospike - WARN Socket write error: 111

**URL:** <https://discuss.aerospike.com/t/aerospike-warn-socket-write-error-111/1118>\
**Category:** General Discussion\
**Created:** [March 31, 2015, 12:41pm UTC](https://discuss.aerospike.com/t/aerospike-warn-socket-write-error-111/1118 "2015-03-31T12:41:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wahaha](https://avatars.discourse-cdn.com/v4/letter/w/90ced4/32.png) [@wahaha](https://discuss.aerospike.com/u/wahaha)\
**Post date:** [March 31, 2015, 12:41pm UTC](https://discuss.aerospike.com/t/aerospike-warn-socket-write-error-111/1118/1 "2015-03-31T12:41:57Z")

</div>

Aerospike Query Copyright 2013 Aerospike. All rights reserved.

aql\> 2015-03-31 20:40:43 WARN Socket write error: 111 2015-03-31 20:40:44 WARN Socket write error: 111 2015-03-31 20:40:45 WARN Socket write error: 111 2015-03-31 20:40:46 WARN Socket write error: 111 2015-03-31 20:40:47 WARN Socket write error: 111 2015-03-31 20:40:48 WARN Socket write error: 111 2015-03-31 20:40:49 WARN Socket write error: 111

---

<div class="post-metadata">

**Author:** ![wahaha](https://avatars.discourse-cdn.com/v4/letter/w/90ced4/32.png) [@wahaha](https://discuss.aerospike.com/u/wahaha)\
**Post date:** [March 31, 2015, 1:04pm UTC](https://discuss.aerospike.com/t/aerospike-warn-socket-write-error-111/1118/2 "2015-03-31T13:04:40Z")

</div>

i find aql exit have some bug ~! may be it doesn’t release the connection

---

<div class="post-metadata">

**Author:** ![dave](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/dave/32/162_2.png) [@dave](https://discuss.aerospike.com/u/dave)\
**Post date:** [April 1, 2015, 11:39pm UTC](https://discuss.aerospike.com/t/aerospike-warn-socket-write-error-111/1118/3 "2015-04-01T23:39:08Z")

</div>

Hi wahaha- What is the port number where your node is listening?

I got the following error when trying to connect:

“[dm@localhost ~]$ aql 2015-04-01 16:33:36 WARN Socket write error: 111 Error -1: Failed to seed cluster”

In my case, this error is to be expected because my node is not using the default port of 3000. When I specify the proper port number (3020, in this case), all is well:

[dm@localhost ~]$ aql -p 3020 Aerospike Query Copyright 2013 Aerospike. All rights reserved.

aql\> show bins 0 rows in set (0.001 secs) 0 rows in set (0.000 secs) OK

aql\> show sets 0 rows in set (0.000 secs) 0 rows in set (0.000 secs) OK

(yes, I know that I have no bins and no sets. This is in a test environment, and it is intentional.)

I hope this helps!

-DM