>Well, the right answer is "it depends". Really, after such thing >happen, you need to run myisamchk on your MySQL database, and index -X1 to >check ASPseek binary database. If index -X1 will tell you something bad, >run index -X2 to fix it. In the worst case, you will have to delete and >reindex everything from scratch, so having an UPS is always a good >idea ;)
Oh ya, I've got a 12HR standby power supply, but I didn't run out of power, I was just asking about if something crashed. For some reason, when I tried to stop the indexing with ./index -E, it took over a day to end and since then, each time I try to run anything, I get the following and nothing works; [aspseek@minnseek sbin]$ ./index -D Loading configuration from /web/aspseek/etc/db.conf Loading configuration from /web/aspseek/etc/ucharset.conf Loading configuration from /web/aspseek/etc/stopwords.conf Loading configuration from /web/aspseek/etc/aspseek.conf Error opening file /web/aspseek/var/aspseek12/pid: No such file or directory Index already working index process finished. [aspseek@minnseek sbin]$ I'll try what you mentioned above but if you can tell me why I'm getting this error, that might help. Thanks. Mike
