cancel
Showing results for 
Search instead for 
Did you mean: 

What caused kdb 64bit can't startup

hzadonis
New Contributor
Hi, Dear all:
  I got a error message once I startup a kdb 64bit  session with "q tp.q" command. tp.q is a script that I'm sure it can work. The message is:
  '8099. OS reports: Only one usage of each socket address (protocol/network address/port) is normally permitted.
  [0]  (<load>)
  
  Do you konw the reason?

Regards
Zheng
2 REPLIES 2

stephen_mcdonal
New Contributor
Hi,

A q session requires that when it binds to a network port that the port is free and unused. From the error it looks like another application is already listening on the port you requested (8099). 
You can ascertain the process id of the application using netstat or similar tool. The error you are getting is a Windows error so using netstat -a -n -o | find "8099" will let you find the process currently running on that port. 

You must either kill this process or move your q session to a different port.


Regards,
Stephen

Hi, Stephen:
  I rerun my q session after the server reboot. 
  Next time if I meet this problem, I'll have a check as you mentioned. Thanks!

Zheng