# hopen just hangs **URL:** \ **Category:** Community Support\ **Tags:** kdb-and-q\ **Created:** [July 30, 2018, 3:07am UTC](https://forum.kx.com/t/hopen-just-hangs/11798 "2018-07-30T03:07:00Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![sudhakar1](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@sudhakar1](https://forum.kx.com/u/sudhakar1)\ **Post date:** [July 30, 2018, 3:07am UTC](https://forum.kx.com/t/hopen-just-hangs/11798/1 "2018-07-30T03:07:00Z")
I am connected to a q server session (v 3.4 on linux) and playing with .z.pg. All of a sudden, that session was not accepting new connections. ie hopen just hangs without any error. But I am still connected to that q session and communicating with it. We had to restart that session to make it accept new connections. Anyone knows why this happened? I dont think my changing of .z.pg is the cause. Also, 20 is perhaps the max # of connections to that server. If this were to happen again, what can an existing q session do to find out why it is not accepting new connections? ---
**Author:** ![TerryLynch1](https://avatars.discourse-cdn.com/v4/letter/t/9e8a1a/32.png) [@TerryLynch1](https://forum.kx.com/u/TerryLynch1)\ **Post date:** [July 31, 2018, 12:18pm UTC](https://forum.kx.com/t/hopen-just-hangs/11798/2 "2018-07-31T12:18:00Z")
A few things could have caused the hopen to hang:  1. you were running a query that caused the instance to be busy (hopen has to wait until your query finishes) 2. you were working in debug mode on the instance. The instance will not accept hopens or queries until you exit debug mode.  3. You altered .z.pw or .z.po As for how you could try to catch this issue in future - modify .z.pw and .z.po to capture/log the incoming hopen request.  Terry ---
**Author:** ![sudhakar1](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@sudhakar1](https://forum.kx.com/u/sudhakar1)\ **Post date:** [August 1, 2018, 12:54am UTC](https://forum.kx.com/t/hopen-just-hangs/11798/3 "2018-08-01T00:54:00Z")
None of those things were true when it happened.  I was actively communicating with that q server session until it was restarted. If it happens again, I will modify .z.pw & .z.po as you suggested.  Thanks.