Getting Data In

ERROR BucketMover - coldToFrozenScript exited with non-zero status: exited with code 1

Splunk Employee
Splunk Employee

I checked splunkd.log today and all i see is this:
06-02-2010 14:04:00.013 INFO BucketMover - will attempt to freeze: /opt/splunk/var/lib/splunk/defaultdb/db/db_1270897276_1268202702_19 because frozenTimePeriodInSecs=1209600 exceeds difference between now=1275505440 and latest=1270897276
06-02-2010 14:04:00.225 ERROR BucketMover - coldToFrozenScript exited with non-zero status: exited with code 1

What does this mean?

0 Karma
1 Solution

Super Champion

What's the value of your coldToFrozenScript setting in your indexes.conf file? Whatever script that is pointed to will be run when for a bucket when it is about to expire (be "frozen"). This mechanism is generally useful as a way to make a backup copy (or often export) your bucket's data to another location before it is deleted from the disk by splunk.

I'm surprised that the name of the script isn't seen in one of these messages.

The term exited with non-zero status generally means that that an OS process (a script or executable) is indicating that it was not successful. Unfortunately, that's pretty much all you can know without some other kind of log message indicating the real issue. If you know what script is setup to run, then you can figure out what's going on from there.

Related docs:

View solution in original post

SplunkTrust
SplunkTrust

Will Splunk retry a coldToFrozenScript call if the script exits with a non-zero status?

0 Karma

Super Champion

What's the value of your coldToFrozenScript setting in your indexes.conf file? Whatever script that is pointed to will be run when for a bucket when it is about to expire (be "frozen"). This mechanism is generally useful as a way to make a backup copy (or often export) your bucket's data to another location before it is deleted from the disk by splunk.

I'm surprised that the name of the script isn't seen in one of these messages.

The term exited with non-zero status generally means that that an OS process (a script or executable) is indicating that it was not successful. Unfortunately, that's pretty much all you can know without some other kind of log message indicating the real issue. If you know what script is setup to run, then you can figure out what's going on from there.

Related docs:

View solution in original post