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. Try increasing the memory to -m 256m (assuming your machine has a lot of memory). If you still get the error try 255 or 254. | *'''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. Try increasing the memory to -m 256m (assuming your machine has a lot of memory). If you still get the error try 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 | + | *'''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. |
Revision as of 12:00, 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. Try increasing the memory to -m 256m (assuming your machine has a lot of memory). If you still get the error try 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.
