-
Notifications
You must be signed in to change notification settings - Fork 624
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
[Bug] Analyzer reports dissapear in 4.1.4 (observable already exists error) #1982
Comments
Hello, I think this issue is the same as this one : #1905 |
+1 |
we have observed the same bug in thehive4.1.4 gives us the errors: and later in other reports: Is happening to us with hashes when we consult a case report. |
We see the same issue for version 4.1.3 on Ubuntu 20.04. When accessing observables page we get:
After trying to run analyzer again we briefly see the analyzer showing the last time the analyzer ran, but cannot open the report - when the analyzer is done, it shows again as not being run at all. For this we see:
|
more (i think) relevant logs. POST request that give the error:
|
i observe that taxonomy continue to be attached to the observable on THv4 |
We are seeing the same issues as explained above. Observable analysis reports are not shown. |
also have the same issue here after upgrading Thehive 4.0.5 to 4.1.0 |
still having the issue after upgrading to 4.1.4, is anything planned to fix this ? do you (TheHive devs) need help figuring out what is happening ? |
This commit fixes the error |
With this commit, the import of the job report won't fail if an observable can't be created (because is already exist, for example). |
Request Type
Bug
Work Environment
Problem Description
After running analyzers on an observable (and all finishing successfully), when loading the Observable page, the analyzer reports suddently dissapear and show "none", as if never run. The Hive log shows this error multiple times:
This error happens mainly with file analyzers, such as EMLparser.
As no error occurs in Cortex, we believe it is an issue in TheHive.
Steps to Reproduce
Complementary information
We started observing this issue after upgrading The Hive 4.0.5 to 4.1.4.
The text was updated successfully, but these errors were encountered: