topic coldtofrozen script on linux doesnt work in Deployment Architecture

coldtofrozen script on linux doesnt work

Starlette — Sat, 27 Nov 2010 14:18:08 GMT

My coldtofrozenscript on linux is totaly ignored, I tweaked the indexes.conf (a few warmbuckets and small total index) and the data is nicely deleted from cold....

How can I see why the coldtofrozen script isnt working?

Configed exactly like the manual,,,

[<index>]
coldToFrozenScript = /opt/splunk/bin/compressedExport.sh

compressedExport.sh I only set the path to the archivelocation

Re: coldtofrozen script on linux doesnt work

tedder — Sun, 28 Nov 2010 09:23:18 GMT

What are the contents of compressedExport.sh? Can you verify that it is executable? Also, try running that script by hand under the same user as splunk:

touch /tmp/foo
/opt/splunk/bin/compressedExport.sh /tmp/foo

Re: coldtofrozen script on linux doesnt work

Starlette — Mon, 29 Nov 2010 14:51:17 GMT

#!/bin/sh
# Copyright (C) 2005-2010 Splunk Inc.  All Rights Reserved. Version 4.0
# Edit this script to reflect your archive directory and save as
# compressedExport.sh

( cd "$1" && gzip *.tsidx )

cp -r "$1" /opt/fl_virtual_san

you mean a test dir instead of a file right? I'have made dir /opt/foo for testing and ran:

/opt$ /opt/splunk/bin/compressedExport.sh /opt/foo

#!/bin/sh
# Copyright (C) 2005-2010 Splunk Inc.  All Rights Reserved. Version 4.0
# Edit this script to reflect your archive directory and save as
# compressedExport.sh

( cd "$1" && gzip *.tsidx )

cp -r "$1" /opt/fl_virtual_san 

*** /opt/foo: directory ***

No files anywhere?

Re: coldtofrozen script on linux doesnt work

tedder — Mon, 28 Sep 2020 09:21:25 GMT

I think your problem is that you cd into the directory, then you try to copy the directory from the wrong location. Change it to this:
gzip $1/*tsidx
cp -r $1 /opt/fl_virtual_san/

Re: coldtofrozen script on linux doesnt work

gkanapathy — Tue, 30 Nov 2010 04:30:57 GMT

Shouldn't be, since the ( ... ) indicates the cd happens in a subshell, so the next command doesn't go to the directory. Furthermore, the path should be absolute for the cp command, so it shouldn't matter. The error indicates that it cp won't copy because /opt/foo is a directory. -r should deal with that. That error message does look strange, and I'm not sure which command is generating it.