Search Server error - disk usage exceeded flood-stage watermark
search cancel

Search Server error - disk usage exceeded flood-stage watermark

book

Article ID: 277600

calendar_today

Updated On:

Products

CA Service Desk Manager CA Service Management - Service Desk Manager ServiceDesk

Issue/Introduction

While installing SDM 17.4 I am getting an error in the post-installation steps

<date> <time> INFO  [m_pollthread] [Network] RunMethod - params[Host=********,Sponsor=iPoz,Method=DeltaAppObjects] Took=15ms, CallsPending=0
<date> <time> WARN  [DeployThread: Running Post Installation steps for CA Service Desk Manager Update(s) : 17.4] [Messages] Unable to find resource task.sdm.postinstall.steps.17.4 in bundle com / ca / smsi / installui / resources / ui / configui
<date> <time> DEBUG [DeployThread: Running Post Installation steps for CA Service Desk Manager Update(s) : 17.4] [Task] inside initErrMap() generic. This method should be overloaded if possible
<date> <time> INFO  [DeployThread] [DeployThread] task.sdm.postinstall.steps.17.4 : failed
<date> <time> INFO  [DeployThread] [DeployThread] Abort requested while running task: Running Post Installation steps for CA Service Desk Manager Update(s) : 17.4 

Manually performing post-installation steps seemed to resolve the problem but an error was found in the initial_load.log file.

[19:23:32,611][ERROR][*************** ][main] index [sdm_index_pcat_##########] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];
[19:23:32,644][FATAL][loader                   ][main] Failed to bulk index sdm_index_pcat
java.lang.Exception: Failed to bulk index sdm_index_pcat
    at com.ca.casm.esearch.AbstractLoader.execute(AbstractLoader.java:825) [search-17.4.0.77.jar:?]
    at com.ca.casm.esearch.InitialLoader.run(InitialLoader.java:88) [search-17.4.0.77.jar:?]
    at com.ca.casm.esearch.Runner.main(Runner.java:75) [search-17.4.0.77.jar:?]

Environment

CA Service Desk Manager 17.3 and up

Cause

It appears the search server was running low on disk space.

Resolution

Freeing up storage space resolved the problem.