|
|||
|
Hi, I'm moving my chat server to a new location and when I try
to run the new installation of version 4 I get this error: Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location and then it gets stuck at: Starting the server ... any idea how to overcome this? |
|
|||
|
when you move the chat server to a new location, you'd better stop the chat server first, becuase the port is listening and you can't start the new chat server.
you can use this command to find the process id of your chat server: ps -ef |grep java find the process id, and kill it kill -9 <process_id> if your "ps" command can't find the process id, you can find the process id from this way: for example, your chat server listening on the default port "51127" login with root first, netstat -ap |grep 51127 then you will get the process id, just kill it and start the new chat server. ![]() |
|
|||
|
Hi that did not work. It's a new server I'm moving the chat to so the chat is not running already. The server is a FreeBSD server, does this pose a problem? The java jre files included in the chat package does that run on FreeBSD servers?
Error: Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location then it gets stuck at a starting server.... |
![]() |
Was this information helpful? Yes No
| Thread Tools | |
| Display Modes | |
|
|