01-13-2025 01:45 AM - edited 01-13-2025 01:56 AM
I am using Xsoar child tenant. However, I manually selected more than one incident and ran another playbook with the setplaybook command and suddenly Xsoar broke. When I want to reconnect through the browser, I get Starting your server error. I waited for about 3 hours, unfortunately it did not recover. When I checked the system via vmcenter, I saw that the RAM reached 90%. So I restarted the server with 64 gb ram and I still get the same error. What should I do for this problem? I can run commands on my Linux server and the memory usage is around 50%. Does something need to be done on the main tenant or do I need to make adjustments on the sub server?
01-13-2025 05:56 PM
Hi,
There could be different reasons when stuck in this same state, have you already raised the support case.
If not try to collect the logs from server side /var/log/demisto/ and create the case. Until support says dont restart the process again.
Any idea how many month of data was there ?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
