All Apps and Add-ons

Change in Database causes FlowReceiver to stop?

colinregan
New Member

I have run into the common problem of running out of disk space (less than 5000 mb error). To fix this, I've attached a 10+Tb drive by changing $SPLUNK_DB within my splunk-start.conf file. I've also exported SPLUNK_DB to the path of the new db location. All this works but when i go into Splunk Stream App to check if I am still getting flows, nothing pops up except an error and FlowReceiver being marked as 'inactive' I'm not sure why this is happening any help would be much appreciated.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...