[Bug] Cuckoo Analyzer Fails when it hasn't been executed for many hours

[nicpenning]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Run Cuckoo Cortex Analyzer against a URL
2. Receive error
3. Run Cuckoo Cortex Analyzer again - it works

Expected behavior
The analyzer should not fail on first run.

Complementary information
This error is received when running the analyzer after it hasn't been used in many hours (about 8-12 hours):
Unexpected Error: Expecting value: line 1 column 1 (char 0)

However, the next run everything just works.

Running 3.3.0-RC5 TheHive (This also occurred on the latest stable release) and
Cortex2.1.3-1
Elastic4Play1.7.2
Play2.6.20
Elastic4s5.6.6
ElasticSearch client 5.6.9
ElasticSearch cluster 5.6.15

But it only seems to happen the once and for the first time when it is a new day. I have not been able to have this issue occur repeatedly outside of the first time trying to run it every morning.

After the failure it works great for the remainder of the day.

Work environment

• Client OS: Win10
• Server OS: Ubuntu 18.04
• Browse type and version: Chrome
• Cortex version:
• Cortex Analyzer/Responder name:
• Cortex Analyzer/Responder version:

[nicpenning]

Update - This appears to be a configuration issue with MySQL on the Cuckoo side, not the analyzer.

The analyzer works great when increasing the default MySQL time out period from 8 hours to something much higher, such as a month.

If you don't use the MySQL back-end for Cuckoo you may not see this problem.

You can check it out how to change it here: https://support.rackspace.com/how-to/how-to-change-the-mysql-timeout-on-a-server/

We have tested this by decreasing the timeout and noticing that the same error existed in a shorter period of time. Based on this testing, we are confident this will resolve the issue at hand.