All Posts

Find Answers
Ask questions. Get answers. Find technical product solutions from passionate members of the Splunk community.

All Posts

I wouldn't expect any modern UF to be not only supported but also to work. That windows release is so out of support that I'd be more concerned with the OS itself than the UF version.
Hi @tech_g706 , there isn't any 8.x version certified compatible with Windows 2008/R2 and supported by Splunk. Probably the 9.4.x version runs on Windows 2008/R2 but it isn't certified and supporte... See more...
Hi @tech_g706 , there isn't any 8.x version certified compatible with Windows 2008/R2 and supported by Splunk. Probably the 9.4.x version runs on Windows 2008/R2 but it isn't certified and supported by Splunk. The only that  can formally answer to your question is Splunk Support. Ciao. Giuseppe
Although it looks like you should be able to use the "move" link in "Lookup definitions", you cannot. The best way to achieve this is to create a new KVstore in the desired location then copy the KV... See more...
Although it looks like you should be able to use the "move" link in "Lookup definitions", you cannot. The best way to achieve this is to create a new KVstore in the desired location then copy the KVstore data there. | inputlookup my_old_kvstore | outputlookup my_new_kvstore I did create a Splunk Idea to resolve this issue. Please vote for it here.
After moving a KVstore to a new Application, Splunk can not longer render the lookup. When moving a KVstore using the "move" link in "Lookup definitions" it only moves the transforms.conf stanza and... See more...
After moving a KVstore to a new Application, Splunk can not longer render the lookup. When moving a KVstore using the "move" link in "Lookup definitions" it only moves the transforms.conf stanza and not the collections.conf stanza. The on-prem solution is to manually move collections.conf but this cannot be done in Splunk Cloud.
Thanks, Upon checking the logs, it seems MongoDB is not running on the heavy forwarder, and that would be required. ta_netskopeappforsplunk_netskope_alerts_v2.log splunklib.binding.HTTPError: ... See more...
Thanks, Upon checking the logs, it seems MongoDB is not running on the heavy forwarder, and that would be required. ta_netskopeappforsplunk_netskope_alerts_v2.log splunklib.binding.HTTPError: HTTP 503 Service Unavailable -- KV Store initialization failed. 2: splunkd.log: ERROR KVStoreConfigurationProvider [15442 KVStoreConfigurationThread] - Failed to start mongod on first attempt reason=KVStore service will not start because kvstore process terminated  ERROR KVStoreConfigurationProvider [15442 KVStoreConfigurationThread] - Could not start mongo instance. Initialization failed.  ERROR KVStoreBulletinBoardManager [15442 KVStoreConfigurationThread] - Failed to start KV Store process. See mongod.log and splunkd.log for details. INFO  KVStoreConfigurationProvider [15442 KVStoreConfigurationThread] - Mongod service shutting down
Hi, We have some Windows 2008 R2 machines where UF 7.2 is running, and in Splunk Cloud CMC, we are getting the forwarder status as critical. My question is, can we install 9.4 or above 9 on the  Wi... See more...
Hi, We have some Windows 2008 R2 machines where UF 7.2 is running, and in Splunk Cloud CMC, we are getting the forwarder status as critical. My question is, can we install 9.4 or above 9 on the  Windows 2008 R2 machines? If not, what is the minimum supported UF version for Windows 2008 R2, and possible workaround to mitigate the critical status notification on Splunk Cloud CMC?   Thank you!
You should not need to enable the inputs separately on each indexer. That's what the CM-pushed apps are for.
@wm  Did you check the primary server is reachable from the Splunk server:  telnet <ServerName> <port>. Given the secondary database works, the issue is likely network-related (firewall, port, DNS)... See more...
@wm  Did you check the primary server is reachable from the Splunk server:  telnet <ServerName> <port>. Given the secondary database works, the issue is likely network-related (firewall, port, DNS) or authentication-related on the primary server. Ensure that no firewalls, network security groups, or proxies are blocking or interrupting the connection between the Splunk server and the HPC primary database.  
@kiran_panchavat @livehybrid Unfortunately , there seems to be no solution for this, i tried and followed the exact steps mentioned in the given below Splunk Doc, but i encounter the same error again... See more...
@kiran_panchavat @livehybrid Unfortunately , there seems to be no solution for this, i tried and followed the exact steps mentioned in the given below Splunk Doc, but i encounter the same error again and again. Do u know how to mitigate this scenarios or any further suggestions on why this is happening. I tried in few of the different settings of VMs where different platforms of linux were installed along with that i increased the capacity of the OS to ensure no issues on the other side. The issue seems to residing in unbundling of the downloaded packages. I understand installation is being corrupted but the package is being downloaded from splunk site right? it shows all files intact but unable to host forwarder in an instance I am stuck here with no specific solutions...   FYI -Tried different linux OS/versions, tried downgrading the SF versions as well... increased capacity of OS
@PickleRick @two separate apps - one with general HEC input settings, another with a token definition for your particular input needs) with CM in an app which is pushed to indexers... So here I crea... See more...
@PickleRick @two separate apps - one with general HEC input settings, another with a token definition for your particular input needs) with CM in an app which is pushed to indexers... So here I created two apps under etc/master-apps and in one enabled http and in other given token and other parameters. So once we push this to indexers.. HEC will be enabled right in indexers? Or do we need to edit each indexer etc/apps/http_input/local/inputs.conf and give [http] disabled = 0 in order to enable? Or already pushed app will do the similar work?
Hi @livehybrid , Thanks for the reply. We've already updated the build version and deployed it to the marketplace. Trying to understand why it's causing issues during an update, while working perfe... See more...
Hi @livehybrid , Thanks for the reply. We've already updated the build version and deployed it to the marketplace. Trying to understand why it's causing issues during an update, while working perfectly on a fresh install.
Hi, The problem seems to be the self signed certificate that was issued by Splunk from the cloud instance. It is not compatible with ver 9.4. I was wondering if it was just me who is experiencing t... See more...
Hi, The problem seems to be the self signed certificate that was issued by Splunk from the cloud instance. It is not compatible with ver 9.4. I was wondering if it was just me who is experiencing the issue or if some one else is experiencing it. But for now we are sticking with ver 9.3.1 in our HF until a fix is released by Splunk.  
I/O Error: DB server closed connection. Hi all, I am getting this error above when connecting to HPC primary database, secondary database connection works well on splunk db connect with exact same... See more...
I/O Error: DB server closed connection. Hi all, I am getting this error above when connecting to HPC primary database, secondary database connection works well on splunk db connect with exact same settings. From memory, hpc primary database connection used to be working too. I am using MS-SQL Server using jTDS Driver with Windows Authentication  jdbc:jtds:sqlserver://<ServerName>:<port number>/master;useCursors=true;domain=<domain_name>;useNTLMv2=true FYI this worked well for hpc secondary database with same configurations except <ServerName>
@livehybrid @kiran_panchavat PFA, this is so weird, i have seen few cases like this in the community with no solution. I tried multiple OS of Linux and older versions of forwarder, but its still the ... See more...
@livehybrid @kiran_panchavat PFA, this is so weird, i have seen few cases like this in the community with no solution. I tried multiple OS of Linux and older versions of forwarder, but its still the same.. Please find a solution as i tried a lot of versions here... splunkforwarder-9.4.1-e3bdab203ac8-linux-amd64-manifest older version 9.4.0 splunk forwarder - splunkforwarder-9.4.0-6b4ebe426ca6-linux-amd64-manifest  
As I said before in another thread - this is something that should be best discussed with your local Splunk Partner. I can tell you that you can just enable HEC input on the HF and send all the data... See more...
As I said before in another thread - this is something that should be best discussed with your local Splunk Partner. I can tell you that you can just enable HEC input on the HF and send all the data there so that the HF distributes it to the indexers but there are other possible issues with this setup. Since you probably have just one HF, you're gonna be creating a SPOF. It might also not be able to process all the load you're gonna push on it. That's why at the start I said that this problem only looks easy. There are several approaches to solving it which might look right from the technical point of view, meaning that each of them "should work" but some of them might be better from the business point of view given specific circumstances unique to your situation and environment.
@PickleRick we already have HF configured in our environment. So how to do it?
You don't define HEC input on CM. CM will not be ingesting your HEC events. You define HEC input (either just a token if you have the general HTTP input already enabled or enable whole HTTP input, d... See more...
You don't define HEC input on CM. CM will not be ingesting your HEC events. You define HEC input (either just a token if you have the general HTTP input already enabled or enable whole HTTP input, define TLS parameters and define a token - for maintainability I'd split it into two separate apps - one with general HEC input settings, another with a token definition for your particular input needs) with CM in an app which is pushed to indexers. So the only thing you should do (as with pretty much everything regarding configuring your indexers) is creating an app in the manager-apps directory and pushing it with a new configuration bundle to your indexers. I'm not sure if enabling HTTP input in general in case you hadn't had one already will not require you to rolling-restart your indexers (and that's why I prefer a dedicated HF-layer in front of indexers so that changes to ingestion process and parsing do not cause indexer restarts but that's a topic for another time.
In my case it is data manager or possibly lambda. There is no inputs.conf in both cases. 
Hi @PickleRick , thanks for the options. I think we are going with the 1st option. we are going to create AWS ELB for load balancing. But I am confused how to create HEC token on all indexers with t... See more...
Hi @PickleRick , thanks for the options. I think we are going with the 1st option. we are going to create AWS ELB for load balancing. But I am confused how to create HEC token on all indexers with the same token? My approach is this please correct me if I am wrong... Going to configure HEC on cluster manager first.. Then take those inputs.conf from etc/apps/http_input/local/ inputs.conf and paste it under etc/manager-apps/hec_input/local/inputs.conf and paste it here. But won't enable http in CM. (disabled = 1 for http) But http:inputname will be enabled (disabled = 0) will it still index HEC data in cluster manager (which should not do). Then push this configurations (app with inputs.conf) through configuration bundle to all my indexers so that each indexer will receive this inputs.conf. additionally should I need to go to each indexer and give [http] disabled = 0 to enable HEC in each indexer in order to receive data? Please confirm and correct me if I am wrong anywhere 
As usual, you have a relatively simply sounding problem which might not turn out to be so simple. As @marnall already pointed out - the HEC input is just an input on the component you define it on. ... See more...
As usual, you have a relatively simply sounding problem which might not turn out to be so simple. As @marnall already pointed out - the HEC input is just an input on the component you define it on. So you can have multiple options here. 1) Create a HEC input on each indexer using the same HEC token and let the sources load-balance their requests between the receivers. But that requires the sources which can actively do load-balancing. 2) Deploy an external HTTP LB which will distribute HTTP requests to HEC inputs defined on indexers (again - with the same HEC token). 3) Create a HF with a HEC input which will receive data and distribute it to indexers using normal s2s load-balancing mechanisms 4) Create multiple HFs with HEC input and either LB between them on source or set up a HTTP LB in front of them. Each of those scenarios have their own pros and cons (simplicity, cost, maintainability, resilience).