Hello We are indexing a file structure like /opt/logs////. with YYYY=year, MM=month and DD=day. So far, we have not been using crcSalt but we now have to apply crcSalt= for some of the smaller file types. We currently have only one monitor stanza for /opt/logs and I do not want to switch on crcSalt= for all files. My plan is to exclude the file names in question from the /opt/log stanza's whitelist and create a new stanza like /opt/logs////(|) and then add the relevant files to that stanza's whitelist and set crcSalt=. But how do I avoid that events get indexed twice, when I switch on crcSalt for these files ? All the files already indexed will not be recognised as indexed as the CRC calculation is changed. Thanks. ... View more

Hi We have just switched from native Splunk authentication to PAM scripted authentication. We are running Splunk 6.3.4 under Linux Suse, sles 11. After switching to PAM scripted authentication the administrator can no longer see the list of users in the GUI (under Settings/Access Controls/Users). Instead we get an error page and we can see internal error is related to "admin:1661 - 'str' object has no attribute 'os_startIndex'" Traceback (most recent call last): File "/opt/splunk/lib/python2.7/site-packages/splunk/appserver/mrsparkle/controllers/admin.py", line 1656, in listEntities pwnrList = en.getEntities("authentication/users", count=250, search="roles=*") File "/opt/splunk/lib/python2.7/site-packages/splunk/entity.py", line 131, in getEntities It seems to indicate a limit of 250 users but we do not have anything like 250 users in the system, which seems to be a (arbitrary) limit set in admin.py. We have tried to increase the count but it did no help. The PAM authentication is actually working but it is a major problem not to be able to see the list of users or to delete the old native user ids in the GUI. We tried to switch back to native authentication and there is no problem displaying the old users again. Thanks for any suggestions to resolve this issue. ... View more