-
Notifications
You must be signed in to change notification settings - Fork 71
Qlik failing to connect to sse plugin #40
Comments
Hi, |
Hi tobiaslindulf, Thank you for the quick reply! I actually have three analytic connections that both point to the sse server (the sse server was insecurely connected to the R serve at the time of writing) with my settings.ini completely empty this whole time. The whole log actually produces this for all 3 of my analytic connections:
2.New SSEPlugin added (non-secure connection). Name: test2
All three analytic connections are failing. Thank you for the help! Kind Regards, Phealey Hang |
Does anyone also know whether 'error code 14' within the SSE engine log(found within the trace folder for qlik directory) is produced by the sse server or qlik server? I have been told that the SSE server generates this error when a connection has failed to establish and is then logged by the qlik engine. So does the SSE server relay this failure back to qlik and then logged into the sse engine log file as 'error code 14'? Kind Regards, |
Hi @phealeyh ! Error messages in the logs can come both from within Qlik (as in the case above) but also from the plugin. In the Writing an SSE plugin using Python guide there is a short section about error handling from the plugin side. You can also look in the system engine log file to get more information about the specific event. For instance, in the event described above, you will have a log message saying "GetCapabilities: Failed for <host>:<port> error code : 14" I hope this helped you, let me know if you have any further questions! Kind regards, |
If I understand this correctly, GetCapabilities returns all of the functions that qlik can use for the R plugin? Can you suggest reasons why the connection is failing? I'm really stumped on what could be causing this problem. Kind Regards, Phealey Hang |
Yes, that's correct. GetCapabilites also returns a boolean for enabling script evaluation as well as an identifier and version of the plugin (see the Capabilities section in the documentation). I would say the most common mistake for a failing connection is that the configuration does not align with the settings in the plugin (or where the plugin is run). The first thing you should do is to:
Also, every plugin you configure should have its own unique port. I noticed all three plugins in your comment further up, are configured to use the same port 50051. With this configuration, only the first plugin connecting to the port will get the GetCapabilities call(given the configuration is correct). For simplicity, I would suggest you start with one plugin and make sure you get that to work before adding more. |
Hi again @phealeyh ! Kind regards, |
Hi @phealeyh , i am facing the same issue. Kindly let me know whether this issue has been resolved for you. Regards, |
How would I resolve this "GetCapabilities: Failed for : error code : 14? Is there another version of the sse-r-plugin-master? I attempted to run the SSEtoServe in Visual Studion to compile it. I am not running the plugin securely in the QMC so no certificates. Do you have any other suggestion in order to get this resolved? |
Description
Qlik sense server is failing to connect to the SSE server on the same machine.
Steps to Reproduce
Expected behavior
[What you expected to happen]
I expected the Qlik server to successfully connect to the SSE-R server.
Actual behavior
[What actually happened]
Qlik fails to connect to the SSE server and produces an error within the trace log folder. The file is SSE_ENGINE and produces an error code 14 when trying to establish to the SSE server.
'New SSEPlugin added (secure connection). Name: R, address: 127.0.0.1:50051 0'
then produces a warning:
'Failed for 127.0.0.1:50051 error code : 14 0 Internal Engine'
then produces another warning:
'Failed to initialize gRPC communication for SSEPlugin R 0 Internal'
Environment
Operating system where the SSE plugin is deployed
[ ] Server
The text was updated successfully, but these errors were encountered: