Caldera UI Does Not Display New Results After Restart

[HackerFerret]

Describe the bug
I encountered an issue where operations and agents disappear from the Caldera UI after a restart, even though the execution results are stored in caldera/data/results/

To Reproduce
Steps to reproduce the behavior:

1. Successfully deploy an agent and execute an operation (confirmed that results are displayed in the UI).
2. Restart Caldera.
3. Upon restart, the agent and operation from that day are no longer visible in the UI.
4. Check caldera/data/results/ and confirm that the execution results exist.

Expected behavior
After restarting Caldera, the UI should still display the operations and agents, as long as the execution results exist in data/results/.

Desktop (please complete the following information):

• OS: Ubuntu
• Browser: Chrome/Firefox
• Version 4.2.0

Additional context
Troubleshooting Attempts which failed:
• Changed file ownership and permissions of data/results/. (via chown & chmod commands)
• Modified system and file timestamps. (since we thought it might be a new bug recently)
• Attempted to overwrite data/results from a previously successful operation with our new result. (since we thought it might be a bug which the Operation ID couldn't link to the new results)

p.s. We deleted all data in data/results/, but Caldera still displayed old results, suggesting it might not be reading from data/results/.

Request for Help:
Is there another directory or database where Caldera stores operation data? How can we ensure that previously executed operations are properly loaded after a restart?

[github-actions]

Looks like your first issue -- we aim to respond to issues as quickly as possible. In the meantime, check out our documentation here: http://caldera.readthedocs.io/

[uruwhy]

what command are you using to restart the server, and how are you terminating the server to begin with?

[HackerFerret]

Thanks for your reply. I terminate the server by "ctrl C" to suspend the caldera server starting command, and I use "sudo python3 server.py –insecure" command to restart the server.

Also when I tried to reproduce this issue, I found out that even if I don't restart Caldera, simply changing the IP and refreshing the Caldera UI interface would cause the same error. The operations and agents that displayed on UI before were all gone.

[uruwhy]

Alright, I'll see if I can replicate your issue with v4.2.0. In the meantime, are you able to use a more recent version of CALDERA to get things working?

[uruwhy]

Data is also stored in data/object_store, though I wouldn't recommend touching that file manually. If you want to clear existing server data, you can rerun it with the --fresh flag, which will have the server create data backups and start from a blank slate.

I wasn't able to replicate your issue, with or without sudo. Tried accessing my local caldera instance from 2 separate browsers (1 as localhost, the other as 127.0.0.1) and was able to see the data after server restart.

I'm thinking maybe you somehow have a separate caldera instance running. There should really be no reason why you're seeing different results without even restarting the server, but accessing it via a different IP, unless you're actually looking at two separate databases (i.e. 2 separate instances of caldera). Can you verify that your caldera logs don't show any errors on startup, like failure to bind to an address?

[HackerFerret]

Thanks for your reply. I'll try the more recent version of Caldera and see if the issue would be solved, I'll let you know if there's any breakthrough, thanks again for your assistance.

[uruwhy]

@HackerFerret do you still need additional assistance with this issue?