* On 11/09/05 12:00 -0700, Mark Sapiro wrote:
> Odhiambo Washington wrote:
> >
> >I recently upgraded a 2.1.3 install to 2.1.5 (along with
> >htdig-2.1.5-0.1.patch and indexing-2.1.5-0.1.patch) and now
> >htdig/archive searches are failing for the following error:
> >
>
> >
> >After the fixes, and
Odhiambo Washington wrote:
>
>I recently upgraded a 2.1.3 install to 2.1.5 (along with
>htdig-2.1.5-0.1.patch and indexing-2.1.5-0.1.patch) and now
>htdig/archive searches are failing for the following error:
>
>
>After the fixes, and after running the nightly_htdig script again as
>the mailman us
Hello users,
I have searched the archives for this one and I did not get any answers
that would help my situation, though I did get some clues..
I recently upgraded a 2.1.3 install to 2.1.5 (along with
htdig-2.1.5-0.1.patch and indexing-2.1.5-0.1.patch) and now
htdig/archive searches are failing f
Michael
The error is saying that when the MM/htdig integration's mmsearch
script attempted to run Htdig's htsearch program as a subprocess, an
exit status value of 127 was returned.
Exit status 127 is conventionally/often/sometimes returned to indicate
"command not found".
A possible cause of
I recently upgraded a 2.1.2 install to 2.1.4 (along with
htdig-2.1.4-0.1.patch and indexing-2.1.4-0.1.patch) and now
htdig/archive searches are failing for the following error:
htdig Archives Access Failure
search failed -12-
in addtion, logs/error shows:
htsearch for list: , existat
