Saved my day😁 ... View more

Check if the KV store is running (splunk show kvstore status), if not start it.  ... View more

I had a similar problem when I upgrade from 3.11.1 to 3.12.2 I had the following error  12-3-2020 15:44:16.843 +0200 ERROR ExecProcessor [9972 ExecProcessor] - message from "/global/apps/splunk/etc/apps/splunk_app_db_connect/bin/dbxquery.sh" action=dbxquery_server_start_failed error=java.lang.RuntimeException: The certificate chain length (11) exceeds the maximum allowed length (10) stack=com.splunk.DBXService.sendImpl(DBXService.java:114)\\com.splunk.DBXService.send(DBXService.java:52)\\com.splunk.HttpService.get(HttpService.java:172)\\com.splunk.Entity.refresh(Entity.java:381)\\com.splunk.Entity.refresh(Entity.java:24)\\com.splunk.Resource.validate(Resource.java:186)\\com.splunk.Entity.validate(Entity.java:462)\\com.splunk.Entity.getContent(Entity.java:157)\\com.splunk.Entity.getString(Entity.java:279)\\com.splunk.ServiceInfo.getVersion(ServiceInfo.java:155)\\com.splunk.DBXService.fetchInfo(DBXService.java:42)\\com.splunk.DBXService.connect(DBXService.java:35)\\com.splunk.dbx.splunkclient.SplunkServiceBuilder.build(SplunkServiceBuilder.java:70)\\com.splunk.dbx.command.DbxQueryServerStart.startDbxQueryServer(DbxQueryServerStart.java:80)\\com.splunk.dbx.command.DbxQueryServerStart.streamEvents(DbxQueryServerStart.java:50)\\com.splunk.modularinput.Script.run(Script.java:66)\\com.splunk.modularinput.Script.run(Script.java:44)\\com.splunk.dbx.command.DbxQueryServerStart.main(DbxQueryServerStart.java:95)\\     I fixed this problem increasing the certificate chain limit in  /opt/splunk/etc/apps/splunk_app_db_connect/jars/ server.vmopts   parameter: -Djdk.tls.maxCertificateChainLength=13 ... View more

Solution is in this thread  https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Machine-Learning-Tool-kit-Error-in-fit-command-External/m-p/408103 ... View more

Solution is in this thread https://atc.bmwgroup.net/bitbucket/projects/SPLUNK/repos/splunk-aws-emea-onboarding/pull-requests/733/overview ... View more

I had a similar problem, I resolved it by trying of the different versions of Splunk_SA_Scientific_Python which were supposed to be compatible with the version of Splunk MLTK I was using.  Splunk MLTK v540 is fully compatible to Splunk SA Scientific Python linux x86 64 v310 ... View more

I had the same problem and I resolved it by installing Install Splunk_SA_Scientific_Python which is compatible with MLTK. ... View more

I had the same error I did all that @khourihan_splun  mentioned and tests were negative. to solve the problem I restarted splunkd on the indexer in question.  ... View more

Hello I'm having the same error, did you manage to fixing it?   2023-03-15 05:26:05,915 level=WARNING pid=2768 tid=Thread-7 logger=splunk_ta_aws.modinputs.sqs_based_s3.handler pos=handler.py:_process:390 | datainput="XXXXXX" start_time=1678855832, message_id=XXXXXXXXXXXXXXX ttl=300 job_id=XXXXXXXXXXXXX | message="Warning: This message does not have a valid SNS Signature Message is too old: 2 days, 16:30:10.556919" ... View more

I'm facing the same problem. Did anyone figure out a way around it?  ... View more

No, there were special characters in my lookup which caused the email alert_action python script to break. Once I removed the special characters email were sent out.  ... View more

I'm also having the same error. How did you fix it? 03-01-2023 15:00:20.084 +0000 WARN sendmodalert [36371 AlertNotifierWorker-0] - action=aws_sns_modular_alert - Alert action script returned error code=1 ... View more

I had the same error, I fixed it by giving splunk user read access to the  logs and the directory they reside in. ... View more

Reloading servers can take a bit more time if your environment is big. that is you have thousands of forwarders connecting to your DS. ... View more

Facing the same problem in version 8.2.4, disk usage on the frontend is 92% and on the backend its 86%. ... View more