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

[harfanglabs] Error in the connector #1975

Open
SamuelHassine opened this issue Mar 25, 2024 · 1 comment · May be fixed by #2211
Open

[harfanglabs] Error in the connector #1975

SamuelHassine opened this issue Mar 25, 2024 · 1 comment · May be fixed by #2211
Assignees
Labels
filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. question use for asking information about a functionality or behavior
Milestone

Comments

@SamuelHassine
Copy link
Member

SamuelHassine commented Mar 25, 2024

Description

The connector is crashing in our internal demo env:

{"timestamp": "2024-03-25T04:55:23.644514Z", "level": "ERROR", "name": "HarfangLab", "message": "[CREATE] Failure stix observable created", "exc_info": "NoneType: None"}
{"timestamp": "2024-03-25T04:55:24.742582Z", "level": "ERROR", "name": "HarfangLab", "message": "Error in ListenStream loop, exit.", "exc_info": "Traceback (most recent call last):\n  File \"/usr/local/lib/python3.11/site-packages/pycti/connector/opencti_connector_helper.py\", line 633, in run\n    self.callback(msg)\n  File \"/opt/opencti-connector-harfanglab/harfanglab.py\", line 240, in _process_message\n    self.update_indicator(msg, \"stix\", \"IOCRule\", self.stix_list_id)\n  File \"/opt/opencti-connector-harfanglab/harfanglab.py\", line 420, in update_indicator\n    observables = entity[\"observables\"]\n                  ~~~~~~^^^^^^^^^^^^^^^\nTypeError: 'NoneType' object is not subscriptable", "attributes": {"reason": "'NoneType' object is not subscriptable"}}
Terminated```
@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 25, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.9 milestone Mar 25, 2024
@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 25, 2024
@helene-nguyen helene-nguyen removed their assignment Apr 2, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.9, Release 6.0.10, Release 6.1.0 Apr 3, 2024
@Jipegien Jipegien modified the milestones: Release 6.1.0, Release 6.1.1 May 3, 2024
@nino-filigran nino-filigran added the filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. label May 17, 2024
@Jipegien Jipegien modified the milestones: Bugs backlog, Release 6.2.0 May 23, 2024
@helene-nguyen
Copy link
Member

helene-nguyen commented Jun 5, 2024

@SamuelHassine this issue occured because the filter is not properly configured and checking it with @pierremahot, everything's working well.

Here's the details of the configuration:

image (7)

@Megafredo found out this issue and is also currently improve the logs and the README documentation, the changes are coming soon.

And as a reminder for anyone who found this ticket, here the blog post for more details:

@helene-nguyen helene-nguyen added question use for asking information about a functionality or behavior and removed bug use for describing something not working as expected labels Jun 7, 2024
@Megafredo Megafredo linked a pull request Jun 12, 2024 that will close this issue
4 tasks
@Megafredo Megafredo linked a pull request Jun 12, 2024 that will close this issue
4 tasks
@Jipegien Jipegien modified the milestones: Release 6.2.0, Release 6.3.0 Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. question use for asking information about a functionality or behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants