Some Common Error Messages
From DLXS Documentation
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | *'''Returning without an answer''' -- Sometimes seen when running xpatbldu, especially when the server is loaded. There may be a bug in xpatbldu that's triggered under certain conditions related to the size of memory allocated for the indexing process. | + | *'''Returning without an answer''' -- Sometimes seen when running xpatbldu, especially when the server is loaded. There may be a bug in xpatbldu that's triggered under certain conditions related to the size of memory allocated for the indexing process. If, for example, your index build command is <code>xpatbldu -m 256m -D $DLXSROOT/idx/c/coll/coll.dd</code>, try changing the memory to 255 or 254. |
| - | *'''pitstge''' -- Sometimes seen when searching for a word in an index that is somehow corrupted and/or truncated. For example, pitstge: n = 154526 out of range. Size = 136844. | + | *'''pitstge''' -- Sometimes seen when searching for a word in an index that is somehow corrupted and/or truncated. For example, <code>pitstge: n = 154526 out of range. Size = 136844.</code> Searches in the index prior to the area of corruption/truncation work, which can mislead you into believing that it is a problem with the query. |
Revision as of 11:04, 15 October 2007
- Returning without an answer -- Sometimes seen when running xpatbldu, especially when the server is loaded. There may be a bug in xpatbldu that's triggered under certain conditions related to the size of memory allocated for the indexing process. If, for example, your index build command is
xpatbldu -m 256m -D $DLXSROOT/idx/c/coll/coll.dd, try changing the memory to 255 or 254. - pitstge -- Sometimes seen when searching for a word in an index that is somehow corrupted and/or truncated. For example,
pitstge: n = 154526 out of range. Size = 136844.Searches in the index prior to the area of corruption/truncation work, which can mislead you into believing that it is a problem with the query.
