-
Notifications
You must be signed in to change notification settings - Fork 640
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
No analyzers available after full upgrade? #1187
Comments
Connection with Cortex looks ok from TheHive: |
Hi @xme, |
Yes, confirmed. Tested just now. |
I've a tcpdump between the 2 dockers and I see TheHive talking to Cortex. No auth issue, user is correct. It seems to be the classic polling at regular interval:
But nothing when I try to launch analyzers... So it seems to be located on TheHive side. |
I restarted my containers... TheHive did the expected request:
|
Hello @xme, After your latest comment, is the problem still there? Nabil |
Interesting finding: when I try to run analyzers from the detail page, it prompts to select the Cortex instance... empty! I also restarted the TheHive container and changed the Cortex instance name... just in case but same problem. |
Ok, can you share the response of |
Email is ok? To? |
Yes, go ahead |
Something probably interesting:
|
I don't like the |
The |
Ok, thank a lot Nabil for your time! The issue was related to 2 old Analyzers that have been removed but still present in the DB (I did a migration from the previous Cortex instance). The 2 Analyzers have been removed from the DB using this command:
|
Work Environment
Problem Description
I can't run any analyzers after a full upgrade. Message is:
"Sorry, there are currently no analyzers for the selected observable type(s)"
Steps to Reproduce
Complementary information
I upgraded my dockers: ES 6.8.5, Cortex 3.0.0 and TheHive 3.4.0.
Cortex integration is ok (green logo), I can start jobs from the Cortex web interface but nothing from TheHive. No specific error message in logs!?
The text was updated successfully, but these errors were encountered: