-
Notifications
You must be signed in to change notification settings - Fork 625
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] Unable to start TheHive after migration #1450
Comments
Were hitting the same timeout after updating from rc3 to 1.0. Unsure if related but we are also seeing the following before hitting the timeout.
|
This errors occurs at each startup ? |
@To-om yes. I tried several times and I got the same result |
Can you enable debug by adding |
I changed it but I see almost the same logs. This is the few debug log at the beginning of starting thehive:
|
@mamoedo I can't reproduce this behavior. Try to start TheHive with a fresh database: change the cassandra keyspace in your configuration file ( |
@To-om changing the cassandra keyspace doesn't solve the problem. TheHive is stuck showing this errors on the logfile, and the web interface isn't up. Cassandra is up.
|
Can you confirm that the server on which TheHive is installed can connect to Cassandra ? (check Firewall rules, SElinux/AppArmor policy). |
@To-om sorry, there wasn't connectivity, TheHive started before Cassandra was fully up, it happens sometimes in my setup. So I did the testing that you asked me and TheHive is up and running correctly with a new keyspace. I can't see what could be wrong with my data then :( I just migrated from TheHive3 to TheHive4 using the tool. I think my data is too large to check in time for the configured timeouts. |
The first start of TheHive (after a migration) can be a little bit long. It indexes data. I was supposing that 5 minutes is enough but if your data is large, you can get a timeout. I can make this timeout configurable. |
@To-om in my setup it's a bit difficult to edit the logback.xml, because it isn't located in
Thanks! It would help a lot to be able to configure it. |
Request Type
Bug
Work Environment
Problem Description
TheHive4 crashes when starting with a not empty database. It makes some checks that seem to be slower than the configured timeout when the database is not empty (or it has few data)
Data size:
Steps to Reproduce
Possible Solutions
Increase the timeout. Although it would be nice to increase the checks speed.
Complementary information
The text was updated successfully, but these errors were encountered: