-
KDB Tick with ‘conn error
The connection reset by peer log is continuously left when requested from the HDB process to the unix domain socket from the HDB process, and the RDB process is constantly experiencing a ‘conn error.
What information should be identified to determine this cause? We need help from KX experts.
And this is an additional question related to KDB Ticker.
Does the RDB process need to shut down and run again to initialize the max connection limit(1022)?
Is there a good way to reconnect when the connection with the RDB process is lost after running the ticker?
-
3 Replies
-
https://code.kx.com/q/basics/errors/#:~:text=conn,connections%20(1022%20max)
The conn error happens when the limit of 1022 open connections is hit.
Some process(es) must be continuously opening handles but not closing them after use.
You can count .z.W at any time to see how many open handles there are.
-38! can give you information on the type of each open handle.
At any time you can force close handles using hclose.
To trace the source of the problem you can add logging and monitoring to the port open and close call-backs, .z.po and .z.pc.
One example is the dotz library which you can customise to your needs.
-
How to determine max connections in q process?
If a daemon process and a new connection is not possible due to the above reasons, what should I do?
-
lsofandnetstatcan give you information about the open handles even if you cannot connect yourself
Log in to reply.