- This topic has 18 replies, 4 voices, and was last updated 19 years ago by
.
-
Topic
-
No matter what I’ve tried I can’t seem to be able to close one of my Processes. within it are 3 inbound threads (all stuck on “Initializing” and an Outgoing(stuck on “Initializing”). These are HL7 TCP/IP. When I try to execute an”hcicmd -p meta_1 -c “InMetaRde pstop” I get the error: “Unable to contach process “meta_1” on port 4175
No Connection could be made because the target machine actively refused it”.
“hcicmd failed”
“Now trying SIGINT”
This isn’t using port 4175 (or even close)
I just want to force it closed, I’ve even bounced the service, no good.
HELP!!!
Win2Ksp4, Qdx 5.3 rev3
Doug
-
Replies
-
-
-
This is a WINSOCK error : WSAEHOSTDOWN It simply means you are tring to connect to a server on a socket but that server is not listening on that port.
You can verify this by running netstat -an and looking for that port to see if there is a listen on it.
For the engine problem, it looks like the TCP/IP connection was lost. Stop the engine, not the thread: hcienginestop -p
It may take a while as it may have to kick it to death.
-
No Luck, Running netstat -an showed me not listening on that port.
this is the response from running hcienginestop:
C:quovadxqdx5.3integratorsupport>hcienginestop -p meta_1
Trying hcicmd…
Can’t contact process meta_1 on port 4175: No connection could be made because the target machine actively refused it.
hcicmd failed!
Now trying SIGINT…
Unable to send SIGINT: No such file or directory
HELP!!
-
Doug, I’m not familiar with Cloverleaf on Windows, but do you have a firewall or something similar running on the Windows box? If you do, try creating some rules to allow Cloverleaf to use any port.
My guess for the first error is that the server is not up since is not connecting, but the second error (cannot bring down the process) is an indication of something stopping the socket communication (the command to stop the process is sent using a port) …that is why I think that there is a firewall or something stopping that type of communications.
Some versions of Windows have a built in firewall, check if that is your problem.
-
There must be some file or something I can modify to force close a connection. I have to get this closed. I can recreate the threads and process if its deleted, no problem. But the ports are in use I need to listen on.
Give me a command that will absolutely kill a process. I want to delete from existance. rebuild it from scratch and launch it, but i need it closed. Work has stopped in that department until i get something going HHEELLPP!!!
-
-
-
-
-
-
-
-
In Unix we have a file called “pid” under the process directory. If for some reason the process dies and the file is still there, Cloverleaf may get confused and think that the process is still up. Deleting that file may solve the problem ./site/exec/processes/proces_name/pid
You may want to call Quovadx support if this is a production issue. They should be able to help you faster over the phone.
-
retyped from the command and engine output “command output” I did find the “4175” in the “cmd_port” within the meta_1 directory
hcicmd -p meta_1 -c “META_IN,InMetaRde,META_OUT,InMetaMfn purgex”
error was: No such file or directory
Try to connect with OLEAN_CLOVERLEA
Unable to contact process ‘meta_1’on port 4175
Unable to contact process ‘meta_1’on port 4175
Error was: No connection could be made because the target machine actively refused it.
hcicmd -p meta_1 -c”META_IN,InMetaRde,META_OUT,InMetaMfn eo_alias enable_all”
error was: No such file or directory
Try to connect with OLEAN_CLOVERLEA
Unable to contact process ‘meta_1’ on port 4175
Unable to contact process ‘meta_1’ on port 4175
Error was: No connection could be made because the target machine actively refused it.
hcienginestop -p meta_1
Trying hcicmd…
Now trying SIGINT…
Now trying SIGKILL…
Unable to stop process ‘meta_1’!
hcienginerun -p meta_1
Engine process ‘meta_1’ is already running.
-
-
-
Hi Doug, I’ve seen this problem a number of times and appears to be due to the process not closing down properly – possibly a Windows thing. This leaves the pid file in the processes directory. I think all the GUI does is check for the presence of this file and if it finds it shows the process as ‘up’ even though it is definitely dead.
I usually check for this file and the cmd_port (in the same directory) if I have this type of problem and delete them once I’ve confirmed using task manager that no hciengine is running for the process.
Regards
Garry
-
hi Doug, engine will not allow you to let connect to a port that is being referenced by a thread that went down abnormally.
1. You ought to be very cautious on this. I am not familiar on QDX running Win2k.
You need to clean up the engine.
If the issue lies within only one process, you can do the following:
hcilmclear -p
This should cleanup the engine at the process level.
2. In the netconfig, go to the thread you were having problems, disable the auto start option and save it.
After the cleanup done in step 1, you should be able to start the threads manually.
-Reggie-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
