Endeca Utility 'backup_log_dir_for_component_AuthoringDgraph' failed

Question

I am getting error when i am executing baseline update script on windows. The forge is happening fine after which the script is throwing error.
[06.25.14 21:04:38] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[06.25.14 21:04:39] INFO: Definition has not changed.
[06.25.14 21:04:39] INFO: Starting baseline update script.
[06.25.14 21:04:39] INFO: Acquired lock 'update_lock'.
[06.25.14 21:04:39] INFO: [ITLHost] Starting shell utility 'cleanDir_processing'.
[06.25.14 21:04:40] INFO: [ITLHost] Starting shell utility 'cleanDir_forge-output'.
[06.25.14 21:04:41] INFO: [ITLHost] Starting shell utility 'cleanDir_dgidx-output'.
[06.25.14 21:04:42] INFO: [ITLHost] Starting shell utility 'move_-_to_processing'.
[06.25.14 21:04:44] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input_for_forge_Forge'.
[06.25.14 21:04:45] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Forge'.
[06.25.14 21:04:46] INFO: [ITLHost] Starting component 'Forge'.
[06.25.14 21:04:55] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Dgidx'.
[06.25.14 21:04:56] INFO: [ITLHost] Starting component 'Dgidx'.
[06.25.14 21:05:11] INFO: [AuthoringMDEXHost] Starting shell utility 'cleanDir_local-dgraph-input'.
[06.25.14 21:05:12] INFO: [AuthoringMDEXHost] Starting shell utility 'rmdir_dgraph-input-old'.
[06.25.14 21:05:13] INFO: [AuthoringMDEXHost] Starting copy utility 'copy_index_to_host_AuthoringMDEXHost_AuthoringDgraph'.
[06.25.14 21:05:14] INFO: Applying index to dgraphs in restart group 'A'.
[06.25.14 21:05:14] INFO: [AuthoringMDEXHost] Starting shell utility 'mkpath_dgraph-input-new'.
[06.25.14 21:05:16] INFO: [AuthoringMDEXHost] Starting copy utility 'copy_index_to_temp_new_dgraph_input_dir_for_AuthoringDgraph'.
[06.25.14 21:05:17] INFO: [AuthoringMDEXHost] Starting shell utility 'move_dgraph-input_to_dgraph-input-old'.
[06.25.14 21:05:18] INFO: [AuthoringMDEXHost] Starting shell utility 'move_dgraph-input-new_to_dgraph-input'.
[06.25.14 21:05:19] INFO: [AuthoringMDEXHost] Starting backup utility 'backup_log_dir_for_component_AuthoringDgraph'.
[06.25.14 21:05:20] SEVERE: Utility 'backup_log_dir_for_component_AuthoringDgraph' failed.
Occurred while executing line 5 of valid BeanShell script:
2|
3|    AuthoringDgraphCluster.cleanDirs();
4|    AuthoringDgraphCluster.copyIndexToDgraphServers();
5|    AuthoringDgraphCluster.applyIndex();
6|
7|    LiveDgraphCluster.cleanDirs();
8|    LiveDgraphCluster.copyIndexToDgraphServers();
[06.25.14 21:05:20] SEVERE: Error executing valid BeanShell script.Occurred while executing line 28 of valid BeanShell script:
25|        Dgidx.run();
26|
27|        // distributed index, update Dgraphs
28|        DistributeIndexAndApply.run();
29|
30|        WorkbenchManager.cleanDirs();
31|        Forge.getPostForgeDimensions();
[06.25.14 21:05:20] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 - null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing
valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing
valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.utility.Utility runInParallel - Utility 'backup_lo
g_dir_for_component_AuthoringDgraph' failed.
[06.25.14 21:05:20] INFO: Released lock 'update_lock'.
In the AuthoringDgraph log it is showing below message.
FATAL
06/25/14 14:39:40.954 UTC (1403707180954)
DGRAPH
{dgraph,baseline}
Rapid updates are not supported for datasets that do not have a record specification model specified in the record spec file.
Stemming should be enabled for 1 languages

Answer 1

Hello,
I believe there are two different issues that may be occurring here, so we can start with the easiest one first, the error message in AuthoringDgraph.  The error message is being triggered as it can't find a property within your records that has been flagged as a Record Specifier (aka Record Spec or RecSpec).  In the Endeca world, this is similar to what a Primary Key on a table would accomplish in a relational database.  These Record Specs are used in many ways for record retrieval, but it's not neccessary to have one put in place.
If you don't specify a property to be a Record Spec, than Endeca will create one for you.  However - and this is where the error message comes in - you cannot perform updates to the data, known as a Partial Update.  Since Endeca hasn't been told what property will uniquely represent a specific record, it can't receive updates to update/delete them.  That's where the "Rapid Updates" comes into play.
There are two choices for this, firstly specify a property as a Record Spec, either through Developer Studio, or through the IOC/CSV overrides if you're using the product catalog integration method (what ATG uses to send data to Endeca).  The second option is to disable Rapid Update (partial updates) functionality in your index - you'll need to comment out references to "partial" directories in the various Dgraph XML configurations in your config/scripts directory.  However, that does go against Endeca Best Practices which are to always have a Record Spec.
And now onto the second issue, the error with the "backup_log_dir_for_component_AuthoringDgraph" script.  This isn't an uncommon type of error, and may be unrelated to the issue above.  The usual culprits for this are permission errors, inability to obtain a lock, etc.  These scripts are run by the EAC and not the application, so are stored in a different location.
Firstly, find the installation directory for Platform Services on your system.  Inside it should be a logging directory, and you're looking for workspace/logs/utility/<appName>.backup_log_dir_for_component_AuthoringDgraph.txt inside there.  Open up that file, and it should help to clarify what the issue is - if not, then please post it's contents here and we can delve deeper.
Best,
- Jeff