You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
OS (where OpenCTI server runs): Windows
OpenCTI version: OpenCTI 5.11.7 and 5.12.15
OpenCTI client: frontend
Other environment details:
Reproducible Steps
Steps to create the smallest reproducible scenario:
Have data queued to be processed by import external reference connector (one instance I have 3k, the other 719k)
Restart connector deployment image for Import External Reference
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:
The text was updated successfully, but these errors were encountered:
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
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
Reproducible Steps
Steps to create the smallest reproducible scenario:
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:
The text was updated successfully, but these errors were encountered: