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

Import External Reference connector getting stuck in ping work_id #1691

Closed
rach24smith opened this issue Jan 12, 2024 · 1 comment
Closed
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@rach24smith
Copy link

Description

Hello! We are having issues with the out of the box import-external-reference connector. It will process references, complete successfully, and then at random times after logging "Processing external reference", it will log "Ping work" and then just continuously log "Ping work" and will not process any more records until I restart it. Then it will process work again for a couple minutes, then repeat the same pattern of the ping work logs.

This problem was first seen in OpenCTI 5.11.7, so I thought the upgrade of the platform and connectors to 5.12.15 would solve it, but it did not.

Environment

  1. OS (where OpenCTI server runs): Windows
  2. OpenCTI version: OpenCTI 5.11.7 and 5.12.15
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Have data queued to be processed by import external reference connector (one instance I have 3k, the other 719k)
  2. Restart connector deployment image for Import External Reference
  3. Watch the logs

Expected Output

Continuously process all pieces of data until the connector message queue is 0.

Actual Output

Continuously logs "Ping work" and no data processed.

Additional information

Screenshots (optional)

Please see logs here:
image

image

@SamuelHassine SamuelHassine added bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR) labels Jan 16, 2024
@SamuelHassine
Copy link
Member

This should be solved in 5.12.17.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants