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
Sometimes it happens that asterisk proxy can't get ready #5855
Comments
ToDo
|
How to test
|
andrea-marchionni
added
verified
All test cases were verified successfully
and removed
testing
Packages are available from testing repositories
labels
Sep 7, 2020
alepolidori
pushed a commit
to nethesis/nethcti-server
that referenced
this issue
Sep 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Sometimes it happens that
astproxy
component can't get ready. Usually happens in installation with many extensions and queues. Analyzing a production environment adding some additional debug information, I've seen that the initialization of the queues starts but never ends. It may depends on parallel operations made with a lot of queues.In the past the same thing happened with extensions.
Expected behavior
The asterisk proxy component has to always emit the
ready
event.Actual behavior
When the problem occurs, the
astproxy
component does not emit theready
event and so the user component cannot starts, denying the user login.Components
nethcti-server3
The text was updated successfully, but these errors were encountered: