Skip to content
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

Closed
alepolidori opened this issue Jul 28, 2020 · 5 comments
Closed

Sometimes it happens that asterisk proxy can't get ready #5855

alepolidori opened this issue Jul 28, 2020 · 5 comments
Labels
bug A defect of the software nethcti Relative to NethCTI client or server verified All test cases were verified successfully

Comments

@alepolidori
Copy link

alepolidori commented Jul 28, 2020

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 the ready event and so the user component cannot starts, denying the user login.

Components

nethcti-server3

@alepolidori alepolidori added the bug A defect of the software label Jul 28, 2020
@alepolidori alepolidori self-assigned this Jul 28, 2020
@alepolidori alepolidori added the nethcti Relative to NethCTI client or server label Jul 28, 2020
alepolidori pushed a commit to alepolidori/astproxy that referenced this issue Jul 28, 2020
@alepolidori
Copy link
Author

alepolidori commented Jul 28, 2020

ToDo

  • Publish new version of astproxy npm module
  • Update nethcti-server package.json with the new version

@alepolidori
Copy link
Author

How to test

  • Being a sporadic bug it is not possible to describe in details an how to test: it seems to happen with "big" installation, where for example a lot of queues exists, a few dozens, but this depends also on the machine characteristics.
  • Is neither possible to have an how to reproduce
  • During the month of August the fix has been installed in to two different server in production and problem no longer appeared

alepolidori pushed a commit to nethesis/nethcti-server that referenced this issue Sep 4, 2020
@alepolidori alepolidori added the testing Packages are available from testing repositories label Sep 4, 2020
@nethbot
Copy link
Member

nethbot commented Sep 4, 2020

in 7.8.2003/nethesis-testing:

  • nethcti-server3-3.19.2-1.8.gdf79567.ns7.x86_64.rpm x86_64
  • nethcti-server3-debuginfo-3.19.2-1.8.gdf79567.ns7.x86_64.rpm x86_64

@andrea-marchionni andrea-marchionni removed their assignment Sep 7, 2020
@andrea-marchionni 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
@nethbot
Copy link
Member

nethbot commented Sep 9, 2020

in 7.8.2003/nethesis-testing:

  • nethcti-server3-3.19.2-1.7.g4e5ef68.ns7.x86_64.rpm x86_64
  • nethcti-server3-debuginfo-3.19.2-1.7.g4e5ef68.ns7.x86_64.rpm x86_64

@nethbot
Copy link
Member

nethbot commented Sep 9, 2020

in 7.8.2003/nethesis-updates:

  • nethcti-server3-3.20.0-1.ns7.x86_64.rpm x86_64
  • nethcti-server3-debuginfo-3.20.0-1.ns7.x86_64.rpm x86_64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect of the software nethcti Relative to NethCTI client or server verified All test cases were verified successfully
Projects
None yet
Development

No branches or pull requests

3 participants