I have a fairly simple UCCX script that is supposed to call a subflow. I'm using the UCCX editor to actively debug the script. When it gets to the step where it is supposed to call the subflow it throws a script exception with the text:
Uknown host: host.docker.internal; nested exception is:
java.net.UnknownHostException: host.docker.internal; nested exception is:
java.rmi.UnknownHostException: Unknown host: host.docker.internal; nested exception is:
java.net.UnknownHostException: host.docker.internal
I've tested on a different computer and it works fine, the subflow is called with no error. I do have docker installed on my computer but I'm unsure how/why it would be interfering with a subflow call. I use docker for completely different development work so I don't want to uninstall it. The script also works fine when uploaded to the CCX server and executed through the triggering application. It only seems to give this exception when debugging on my workstation.
Any ideas how to resolve this issue?
UCCX Version 12.0.1.10000-24
UCCX Editor Version 12.0(1.00)
I'm running the editor on Windows 10 Enterprise 20H2
Related
WEB CLIENT EXCEPTION Error in python
In Some system my python project working ok but in some system i am getting following error."An excption has been caught by the web client". at middles of proggram.
i am suing selenium module for and crome driver.
i need to change programme
Everytime I try to poll network drive on linux machine, it gets failed. I've tried both the options giving the absolute path and the mount path of the network drive. It is specifically giving errors when my Mule Runtime is also on Linux, on Windows it is working perfectly fine. Here is my flow:
I've also tried path="/ihr_dev_test/Dev/Ingest_Storage/Practitioner", since ihr_dev_test is mounted on my linux server, but every time I get the same error:
I'm running my Mule workflow on linux Machine, following is the Stacktrace:
2017-12-18 06:08:47,639 [qtp100710435-9788] INFO org.mule.transport.file.FileConnector - Registering listener: filepollerFlow on endpointUri: file:///nasv0053.uhc.com/ihr_dev_test/Dev/Ingest_Storage/Practitioner
2017-12-18 06:08:47,640 [qtp100710435-9788] INFO org.mule.lifecycle.AbstractLifecycleManager - Initialising: 'null'. Object is: FileMessageReceiver
Message : Failed to start inbound endpoint "endpoint.file.nasv0053.uhc.com.ihr.dev.test.Dev.Ingest.Storage.Practitioner"
Element : /endpoint.file.nasv0053.uhc.com.ihr.dev.test.Dev.Ingest.Storage.Practitioner # app:filepoller.xml:10 (File)
Exception stack is:
Failed to start inbound endpoint "endpoint.file.nasv0053.uhc.com.ihr.dev.test.Dev.Ingest.Storage.Practitioner" (org.mule.api.lifecycle.LifecycleException)
org.mule.util.FileUtils.openDirectory(FileUtils.java:128)
org.mule.transport.file.FileMessageReceiver.doConnect(FileMessageReceiver.java:155)
org.mule.transport.AbstractMessageReceiver.connectHandler(AbstractMessageReceiver.java:448)
I have two curls, one that comes with the OS, and another that comes with an application I installed. When I try run the one that comes with the application, I get "`curl: (2) Failed initialization", what is the problem here?
I have followed the install instructions and gone over them multiple times with a fine comb and I am still unable to determine why I cannot resolve the NameService. I have the omniNames service running, but when I run omniEvents I get the following
omniEvents: [32190]: Warning - failed to resolve initial reference 'NameService'. Exception NO_RESOURCES
I receive this same error message when I attempt to connect within the Sandbox in the IDE, but I am still able to run components and connect them while running in the IDE Sandbox.
I ran nameclt list and received the following output
Cannot resolve the root context.
Have you set up the configuration file properly?
my config file contains the following
InetRef = NameService=corbaname::127.0.0.1
InetRef = EventService=corbaloc::127.0.0.1:11169/omniEvents
I have also verified that the services are being started on the correct ports using netstat.
What am i missing to get connected to the name service?
It appears that your error might be due to a typo in /etc/omniORB.cfg. In your example you use "InetRef" when it should be "InitRef".
Double check the settings and then restart omniNames and omniEvents and try nameclt again. If you get an error such as this:
$ nameclt list
Caught a TRANSIENT exception when trying to validate the type of the
NamingContext. Is the naming service running?
Double check that omniNames is indeed running (i.e. ps -ef | grep omniNames).
I'm using web.py 0.3 / apache2 / mod_wsgi and the cgitb module doesn't seem to work out of the box (I still just get 'internal server error' from web.py and the usual output goes to apache's error_log). The web.py install guide suggested a workaround which didn't work for me - I could probably hack it into working, but is there something better (perhaps designed for web.py or wsgi) that I should use instead?
Set web.config.debug = True before creating your app. That enables debug error, which contains the stack trace of exception along with values of locals.
When debugging apache2 and web.py, it's usually good to catch errors in the apache error log. When you get an internal server error, for instance, it means nothing was returned for whatever reason by your app.
On Linux, I just watch the error log in a separate terminal...
tail -f /var/log/apache2/error_log
or
tail -f /var/log/httpd/error_log
or something depending on your distribution. If there's a typo or error message or what not, you'll get the typical python stack trace in your error log even if you get an internal server error in your browser.
Lack of cgitb was really slowing me down, too. This did it for me:
try:
Output+=TroublesomeScript(etc)
except:
import traceback;
Output+=str(traceback.format_exc())
You can beautify the output if you like but this should give you the information you need for debugging. You can also just output sys.exc_info(), but the traceback module seems to be recommended.