How to clean up licence violations and get the 'free' version working again?
The licensing /testing arrangement on spunk needs sorting out.
W hy must they act like microsoft and continually blame the user instead of clamping the data volume just prior to the licence being violated?
The setup....
Install load in a few logs and.... overshoot the licensing requirement, warning 1 (new user evaluation)
Cut back the data.... shutdown 'spunk' for a few days.... restart... and overshoot the licensing due to back-stored data, that on a daily basis would not trigger a licensing violation ( several more licence violations)... due to forgetting to set spunk to 'auto start' on the test server.
finally get "Error in 'litsearch' command: Your Splunk license expired or you have exceeded your license limit too many times. Renew your Splunk license by visiting www.splunk.com/store or calling 866.GET.SPLUNK." messages.....
drop back to 'free' version to try and clean up the mess...
Then on startup of 'free version":
"Error in 'litsearch' command: Your Splunk license expired or you have exceeded your license limit too many times. Renew your Splunk license by visiting www.splunk.com/store or calling 866.GET.SPLUNK."
Current data volume on test setup ~ .1gb
keeping in mind that this is a test server, just why must they make it so difficult to evaluate the product?
... View more