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

CSV Import Connector getting hung up on imports #6314

Closed
rach24smith opened this issue Mar 11, 2024 · 6 comments · Fixed by #6533
Closed

CSV Import Connector getting hung up on imports #6314

rach24smith opened this issue Mar 11, 2024 · 6 comments · Fixed by #6533
Assignees
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)
Milestone

Comments

@rach24smith
Copy link

Description

We have noticed that the ImportCSV connector gets hung up on several occasions while we are trying to upload a csv of IOCs. Since it is built into the platform, we are unable to restart it like a normal connector, and have to restart the entire platform. When we restart the platform, the problem resolves.

Environment

  1. OpenCTI version: 5.12.32 and past versions
  2. OpenCTI client: frontend

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Upload a csv to the platform
  2. run the importCSV connector on the document with a csv mapper that was already created

Expected Output

The expected result would be the import completes successfully

Actual Output

The import spins indefinitely, with no errors

Additional information

Screenshots (optional)

@rach24smith rach24smith added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 11, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.6 milestone Mar 12, 2024
@Jipegien Jipegien modified the milestones: Release 6.0.6, Release 6.0.7 Mar 12, 2024
@Jipegien
Copy link
Member

@rach24smith Does it concern a specific file, or files with a certain size? Are you able to share a problematic file with us for reproducing?

@Jipegien Jipegien added needs more info Intel needed about the use case and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 13, 2024
@rach24smith
Copy link
Author

@Jipegien, it appears to be random. We have seen no pattern. The most recent time was on a CSV file with 600 lines in it, and it got hung up, but when we restarted the platform and tried again, it worked no issues. But we have seen it with much smaller files too!

@Jipegien
Copy link
Member

Sorry I did not find a way to reproduce it. @Kedae @sbocahu any idea what could cause this or what could be retrieve to get more information?

@Jipegien
Copy link
Member

It probably comes from worker queue congestion. Try to add some workers to be able to process the queue more rapidly.

I close the issue for now. If you have the problem again, please share config of your platform in term of worker, database and ram, as well as specifics about the file.

@Jipegien Jipegien removed the needs more info Intel needed about the use case label Mar 25, 2024
@Jipegien Jipegien removed this from the Release 6.0.9 milestone Mar 25, 2024
@Jipegien Jipegien added question Further information is requested and removed bug use for describing something not working as expected labels Mar 25, 2024
@rach24smith
Copy link
Author

rach24smith commented Apr 1, 2024

Hello @Jipegien, this happened again today, on one of our instances of OpenCTI that is barely used. The file only had 8 items in it for upload. It has 15 workers, CPU usage sits below 25%. Can you please reopen this ticket?

@Jipegien Jipegien reopened this Apr 2, 2024
@Jipegien
Copy link
Member

Jipegien commented Apr 2, 2024

Thanks @rach24smith :) we are investigating.

@Archidoit Archidoit added bug use for describing something not working as expected and removed question Further information is requested labels Apr 2, 2024
@Archidoit Archidoit added this to the Release 6.0.9 milestone Apr 2, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 3, 2024
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

Successfully merging a pull request may close this issue.

5 participants