length for item [id] does not match old magic file, expected 0 got [something else]
forward_processor: [number], idx = [id]: Could not locate magic file /san/[esp_folder]/data/data/data_fixml/[Set_folder]/Elem_xx.xml
[code="5" description="Failed to persist batch: Could not create compressed fixml file '[path]\latest.fixml.gz'" suggested action="DROP" component="indexing"].
1) ESP not having full write access to everything inside %FASTSEARCH%,
2) A previous SAN connectivity issue that may have resulted in some things being mounted read only,
3) Some corruption in the storage of data_fixml, or in the ability to access it.
1. Run the command:
indexeradmin -a suspendindexing
2. Using the rc command, verify that the fixmlindex process for each partition is aborted after waiting up to five minutes.
After suspendindexing, the fixmlindex processes should stop the current tasks and become idle, but they will still be running. This can be verified by:
Running the following on a Unix platform: rc -r indexing | grep "state of partition”
Running the following on a Windows platform: rc -r indexing | findstr /C:"state of partition"
The above commands will provide an output of all idle partitions, which is the intent of the suspendindexing step prior to running "nctrl stop indexer" as in STEP #3. If, and only if, they are not idle after five minutes, then it may be necessary to kill the one that is not idle (that is, the one that had some problem stopping its work, and whose ID is already known). Since the rc command returns the partition number, this can be used to identify the process number to kill. %FASTSEARCH%\var\run\producer_X.pid (Linux:$FASTSEARCH/var/run/producer_X) will also contain that process number.
3. Run the command:
nctrl stop indexer
4. Delete %FASTSEARCH%\data\data_fixml\hashFlushed
5. Add the parameter verifyMagicFileEnabled="true" to the %FASTSEARCH%\etc\config_data\RTSearch\webcluster\rtsearchrc.xml file on the ESP node.
6. Run the command:
nctrl start indexer
The indexer will then validate all fixml and regenerate its internal db.
WARNING: The steps above will create a temporary feeding outage.
Artikelnummer: 2568580 – Letzte Überarbeitung: 01.09.2011 – Revision: 1