Here are explanations and remedies.
A WebKB process that updates the KB locks it to prevent other processes to
read or write during the modification. However, it may happen that this
process goes into an infinite loop and that you cannot stop it just by
clicking on the "stop" orb "back" buttons of your browser (or exiting it).
In that case, this process and the pending ones need to be killed.
Please click here to do so.
A WebKB process that updates the KB also marks the KB as "dirty file" and killing the process might leave the KB marked that way. If you see the message "Can not open dirty file in read only mode", this is the case. Try to use the "statement update" tool (just enter a command such as "print 'Hello'"), that may be sufficient to remove the "dirty file" mark.
If WebKB is still not responding or behaving erratically, the database may be
corrupted and has to be re-initialized.
Please click here to do so.
If you have made modifications to the KB by sending documents containing
commands (which you should do rather than manually using the interfaces for
doing small incremental changes), you can now re-send these documents to
WebKB-2.