在基线更新期间,我收到错误,因为backup_log_dir_for_component_Dgraph2失败。
Setting flag 'baseline_data_ready' in the EAC.
1 file(s) moved.
[06.28.16 05:26:02] INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
[06.28.16 05:26:02] INFO: Definition has not changed.
[06.28.16 05:26:02] INFO: Starting baseline update script.
[06.28.16 05:26:02] INFO: Acquired lock 'update_lock'.
.
.
.
more logs in between
.
.
.
[06.28.16 05:26:17] INFO: [ITLHost] Starting component 'Forge'.
[06.28.16 05:45:14] INFO: [ITLHost] Starting backup utility 'backup_log_dir_for_component_Dgidx'.
[06.28.16 05:45:15] INFO: [ITLHost] Starting component 'Dgidx'.
[06.28.16 06:00:59] INFO: [MDEXHost] Starting shell utility 'cleanDir_local-dgraph-input'.
[06.28.16 06:01:01] INFO: [MDEXHost] Starting shell utility 'rmdir_dgraph-input-old'.
[06.28.16 06:01:03] INFO: [MDEXHost] Starting copy utility 'copy_index_to_host_MDEXHost'.
[06.28.16 06:01:26] INFO: Applying index to dgraphs in restart group 'A'.
[06.28.16 06:01:26] INFO: [MDEXHost] Starting shell utility 'mkpath_dgraph-input-new'.
[06.28.16 06:01:27] INFO: [MDEXHost] Starting copy utility 'copy_index_to_temp_new_dgraph_input_dir_for_Dgraph1'.
[06.28.16 06:01:59] INFO: [MDEXHost] Starting shell utility 'move_dgraph-input_to_dgraph-input-old'.
[06.28.16 06:02:01] INFO: [MDEXHost] Starting shell utility 'move_dgraph-input-new_to_dgraph-input'.
[06.28.16 06:02:02] INFO: [MDEXHost] Starting backup utility 'backup_log_dir_for_component_Dgraph1'.
[06.28.16 06:02:03] INFO: [MDEXHost] Starting component 'Dgraph1'.
[06.28.16 06:02:10] INFO: [MDEXHost] Starting shell utility 'rmdir_dgraph-input-old'.
[06.28.16 06:02:12] INFO: Applying index to dgraphs in restart group 'B'.
[06.28.16 06:02:12] INFO: [MDEXHost] Starting shell utility 'mkpath_dgraph-input-new'.
[06.28.16 06:02:13] INFO: [MDEXHost] Starting copy utility 'copy_index_to_temp_new_dgraph_input_dir_for_Dgraph2'.
[06.28.16 06:02:38] INFO: Stopping component 'Dgraph2'.
[06.28.16 06:02:39] INFO: [MDEXHost] Starting shell utility 'move_dgraph-input_to_dgraph-input-old'.
[06.28.16 06:02:40] INFO: [MDEXHost] Starting shell utility 'move_dgraph-input-new_to_dgraph-input'.
[06.28.16 06:02:42]
INFO: [MDEXHost] Starting backup utility 'backup_log_dir_for_component_Dgraph2'.
[06.28.16 06:02:43] SEVERE: Utility 'backup_log_dir_for_component_Dgraph2' failed. Refer to utility logs in [ENDECA_CONF]/logs/archive on host MDEXHost.
Occurred while executing line 5 of valid BeanShell script:
[[
2|
3| DgraphCluster.cleanDirs();
4| DgraphCluster.copyIndexToDgraphServers();
5| DgraphCluster.applyIndex();
6|
7|
]]
[06.28.16 06:02:43] SEVERE: Error executing valid BeanShell script.
Occurred while executing line 35 of valid BeanShell script:
[[
32| Dgidx.run();
33|
34| // distributed index, update Dgraphs
35| DistributeIndexAndApply.run();
36|
37| // if Web Studio is integrated, update Web Studio with latest
38| // dimension values
]]
[06.28.16 06:02:43] SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks.
Renaming G:\Endeca\MyEndecaApp\config\script\..\..\.\logs\dgraphs\Dgraph2 to G:\Endeca\MyEndecaApp\config\script\..\..\.\logs\dgraphs\Dgraph2.2016_06_28.06_02_42
Unable to rename G:\Endeca\MyEndecaApp\config\script\..\..\.\logs\dgraphs\Dgraph2 to G:\Endeca\MyEndecaApp\config\script\..\..\.\logs\dgraphs\Dgraph2.2016_06_28.06_02_42: Permission denied
我尝试一次又一次地运行基线更新,有时Dgraph1失败,有时Dgraph2失败。失败后,dgraph也停止了。
编辑1:我观察到当我从工作台停止dgraph然后运行基线更新时,它总是成功运行。我尝试了4-5次。 我们知道baseline_update会在备份日志文件夹之前停止dgraph。所以我假设在baseline_update备份日志文件夹之前没有正确停止dgraph,因此它会产生错误。
请帮我解决问题。我是Endeca Administration的新手
谢谢
答案 0 :(得分:1)
有几种情况会导致权限问题。
根据Endeca安装文档,您应该在Windows Server上将Endeca安装为特定用户。让我们假设用户被称为' endeca'。你有没有确定' endeca' user是G:\Endeca\MyEndecaApp
文件夹和子文件夹的当前所有者?指定'所有者'您还需要将此文件夹的权限设置为Full
到' endeca'用户。您是否正在运行您的Endeca服务作为' endeca'用户?
假设您已经完成了上述操作并且仍然存在问题,那么根据您开始索引的方式也可能会发生问题。如果您从CMD提示中启动基线索引,您是否正在以自己的身份执行此操作,那就是' endeca'用户或'管理员'?取决于您运行最后一个索引的人员,将确定您是否拥有所有后续运行的权限。我倾向于做CMD线路执行,因为'管理员'并且很少有许可问题。
您是否正在检查' Notepad.exe'中的日志文件?它会激活地锁定文件,因此如果您在文件夹中打开它,您将无法重命名该文件或文件夹。#Note;'。要么确保你没有在“记事本”中打开它。或者更确切地说,使用' Notepad ++'它没有锁定文件。
最后,我还遇到了需要重命名的日志文件夹中打开CMD提示的问题。因此,请确保您的CMD提示已关闭或未打开日志文件夹。
过去3年一直在Windows Server 2012 R2上运行Endeca,这是我唯一遇到的问题。如果所有其他方法都失败了,您可以随时尝试使用sysinternals
工具,特别是' procmon.exe',但它会在您构建索引期间输出大量信息,以便为信息做好准备过载。
答案 1 :(得分:0)
从IAP工作台将Dgraph属性'numIdleSecondsAfterStop'更改为90秒解决了这个问题。
它显示失败的原因是Dgraph在重命名之前没有正确停止,而日志文件夹被Dgraph锁定。
设置'numIdleSecondsAfterStop'会导致基线在Dgraph停止后等待90秒以处理后续步骤。
答案 2 :(得分:0)
日志中的问题非常明显,这样的文件夹不存在,因此基线进程无法重命名文件夹Dgraph2。这通常发生在基线更新运行时进程失败的过程中。比如说,您运行了该过程,并且该脚本在收回该内容后清除了一个文件夹,但它失败了。您可以再次从第一个开始运行该过程,因此当它再次尝试清除时,您通常会得到丢失文件夹的错误。简单的解决方案是创建丢失的文件夹Dgraph2,或者由于工作台停止或任何事情导致更新失败。然后注释应用程序配置脚本,直到它成功运行并再次从该特定实例运行。希望这有帮助!