These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
VISIT OUR DIFFERENT FORUMS:
Announcements > | |
CloudShell > | TestShell > |
Developers > | BI (Business Inteligence) > |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide > | Configuration Management > |
Getting started with Shells > | Extending CloudShell with Cloud Providers > |
Getting started with Orchestration > | API Guide > |
To share your integration, follow the instructions in this guide >.
Hi,
The L1 driver uses port '4000' by default while executing. Not sure where this is set. Since I have multiple L1 drivers, I want to set the port to any other available port as it comes up with the socket error:
2019-11-26 15:59:33,178 [INFO]: COMMANDS.cytecrf_commands main - run_driver Starting driver cytecrf on port 4000, PID: 3956 2019-11-26 15:59:33,190 [DEBUG]: COMMANDS.cytecrf_commands driver_listener - _initialize_socket New socket created 2019-11-26 15:59:33,190 [ERROR]: COMMANDS.cytecrf_commands driver_listener - _initialize_socket [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions
Regards
Geetha
Answer by Geetha Kuthalam · Nov 26, 2019 at 06:10 AM
If I change the port in the main file to 4003, I get the following error.
An error occurred trying to execute a command on a resource at this address: 43 The error was:There was an error talking to the server: System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:4012 at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port) at QualiSystems.ResourceManagement.Service.APIService.TclDriverTcpClient.SendMessage(String message, String responseTerminationString, Func`1 isDriverAvailable, Int32 timeout, Int32 receivingDataTimeout)
Answer by Geetha Kuthalam · Nov 28, 2019 at 05:52 AM
Driver logs
Answer by Yaniv Kalsky · Dec 02, 2019 at 08:53 PM
The Quali server decides which port to use when it starts the driver.
You should not change that in the driver itself.
If there are issues with a specific driver, maybe some other instance is still running when it shouldn't and is occupying this port.
Answer by Geetha Kuthalam · Dec 10, 2019 at 10:54 PM
Hi Yaniv,
I restarted the Quali service and that fixed the error.
Regards
Geetha
These forums are a place for learning, helping and sharing experiences with others about any of our products. Feel free to ask a question and get answers from our community and our most advanced users.
Note that these are public forums - anyone can view the discussions here.
Announcements | |
CloudShell | TestShell |
Developers | BI (Business Inteligence) |
This is where you can suggest your ideas to help and improve the product for everyone.
Please make sure to read the following article before posting a new idea, to get more information about the required information and ideas lifecycle.
Feel free to vote and comment on other ideas to promote them.
Thanks for everyone who suggested the ideas and voted for them.
Find, download and share integrations that can extend and enhance the CloudShell experience.
Integrations have several levels:
Certified - Officially tested and supported by Quali.
Preview - Provides a sneak peek to what the Quali team is developing. Officially supported by Quali. Feel free to experiment and comment, but please take into consideration that it is not yet tested and released.
Community - Integrations shared by community users. Feel free to look into what other users have contributed, please take into consideration that these integrations are not tested by Quali.
To learn more about creating Shells and integrating with CloudShell, use the following links:
CloudShell's Dev Guide | Configuration Management |
Getting started with Shells | Extending CloudShell with Cloud Providers |
Getting started with Orchestration | API Guide |
To share your integration, follow the instructions in this guide.