how can i find out whehter files/db in /var are corrupted?
Markus Rietzler
* kommunikation & online service
* RZF NRW
* Tel: 0211.4572-130
-----Urspr�ngliche Nachricht-----
Von: Kir Kolyshkin [mailto:[EMAIL PROTECTED]]
Gesendet am: Freitag, 3. August 2001 12:31
An: [EMAIL PROTECTED]
Betreff: Re: [aseek-users] searchd is dying
One possible reason may be your MySQL DB is corrupted - run myisamchk
on it. Another reason may be your ASPSeek DB (the one in /var) is
corrupted - it that case the universal solution is (oops) reindex
everything to new DB. And at last, searchd may contain a bug, it that
case you need to run gdb to debug and locate it.
So, first do myisamchk, then if the problem persist, make sure that you
have debugging info in searchd (compiled with at least with -g), start
searchd and connect gdb to it (gdb searchd <pid>, there <pid> is process
id of just started searchd). Then try the query that fails and see in gdb
what happened to searchd (backtrace, info threads, etc. - read gdb manual).
> [EMAIL PROTECTED] �����(�):
>
> hi,
>
> everything runs fine so far except that searchd is dying sometimes.
> i have restartet searchd yesterday (22.00) and until now (10.00) searchd was restartet 16 times. i have written a small shellscript that
>
> permanently looks whether there are any searchd processess and restart searchd if it is missing.
>
> the interessting part is, that certain search phrases allways lead to an error, eg. when i look for "anonyme alkoholiker" then i get
>
> an "error in query". looking for other two-word-searches is now problem. any idea?
>
> i run aspseek 1.2.4a on suse 6.3 with unicode-support
>
> Markus Rietzler
> * kommunikation & online service
> * RZF NRW
> * Tel: 0211.4572-130
--
[EMAIL PROTECTED] ICQ 7551596 Phone +7 903 6722750
Reality always seems harsher in the early morning.
--
