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
Yesterday i'm upgrading TheHive 2.10 - 2.11 all goes well | I have using "binary" deployment and all was ok.
Cortex engine is 1.0.1 and work with TheHive 2.11, I have my own analyzers, and work ok. But I tried to upgrade Cortex 1.0.1 to 1.1.0 Binary first and later, from deb package.
First| Problem, When I start Cortex doesnt show any analyzers , y check application.conf and all seems ok.
From package deb, the same problema, when I start Cortex-1.1.0 analyzers doesnt show, any analyzers.
I back to cortex 1.0.1 and work well | Maybe some bugs? any new config files to be configured?
Thanks in advance, I want to "release" my analyzers soon with us support!
The text was updated successfully, but these errors were encountered:
ST2Labs
changed the title
Cortex 1.10 doesnt work with theHive 2.11
Cortex 1.1.0 doesnt work with theHive 2.11.0
May 13, 2017
Thank you for your reporting.
Did you update Cortex-analyzers as well ? we have added licenses and authors in each individual JSON configuration file that cortex is looking for to run each analyzer properly.
Request Type
Bug Maybe
Work Environment
Problem Description
Yesterday i'm upgrading TheHive 2.10 - 2.11 all goes well | I have using "binary" deployment and all was ok.
Cortex engine is 1.0.1 and work with TheHive 2.11, I have my own analyzers, and work ok. But I tried to upgrade Cortex 1.0.1 to 1.1.0 Binary first and later, from deb package.
First| Problem, When I start Cortex doesnt show any analyzers , y check application.conf and all seems ok.
From package deb, the same problema, when I start Cortex-1.1.0 analyzers doesnt show, any analyzers.
I back to cortex 1.0.1 and work well | Maybe some bugs? any new config files to be configured?
Thanks in advance, I want to "release" my analyzers soon with us support!
The text was updated successfully, but these errors were encountered: