New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NethCTI 3: server does not work properly if some ports are busy during the boot #5451
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Some logs related to the problem:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I've added a shutdown system:
|
The fix has been applied only to com_authentication_rest component to now. |
in |
How to test
stop the restart and verify that the authentication component is listening on port 50113 and that the clients successfully login (use |
in |
in |
in |
in |
in |
During
On a customer installation, during the boot of the machine, an uncaught exception happens and this cause the break of authentication service (that listen on 50113 port). So the users are not able to login to cti client.
This behavior can happens even if a port is already taken by other service during the boot.
Into the log an "Uncaught exception" is written.
Steps to reproduce
Expected behavior
After the machine boot, cti server have to work properly.
Actual behavior
In the customer installation clients cannot do the login.
Components
cti server
Fix
Wrap into a try/catch block all local services that listen on a specific port on localhost (in all server files of all com... components). Ports are set into the
/etc/nethcti/services.json.
In case of Uncaught exception, thing if a
process.exit(1);
is correct: upstart will restart the service.The text was updated successfully, but these errors were encountered: