Unfortunately, even the most experienced users of the perfect program run into trouble at times. Here is an extremely short section (to be expanded over time) to assist during those times.
Occasionally, it will be necessary to restart your local OpenCyc image. To restart your image, follow the instructions in the next section for halting an OpenCyc image (How to Safely Halt Your OpenCyc image), then go to the top of this document and follow the instructions for starting up a new image in the How to Start a New OpenCyc image section.
If your OpenCyc image doesn’t seem to be responding, do not despair. There are several possible reasons for this:
The Cyc Agenda is processing a long operation: Certain operations, most notably unasserts or edits which involve deeply embedded knowledge, may take some time to process. This is normal. Remember that when an assertion is removed from the KB (and edit operations involve an unassert), the TMS (Truth Maintenance System) must look at all of that assertion’s dependents and reevaluate if they should remain in the KB. For each of those that is subsequently removed, the procedure must be repeated. Eventually, the Agenda will finish with the operation, and the OpenCyc image will free up. See the Cyc Agenda Documentation for details on how the Cyc Agenda works.
The Cyc Agenda is stuck in an error break: If the error handling mode is set to “Enter the Debugger”, an error in the Cyc Agenda will freeze up the OpenCyc image until the error is dealt with. To avoid having your OpenCyc image freeze up when the agenda runs across an error, set the error handling mode to “Halt and Display Reason”. The Agenda will still halt, but the OpenCyc image itself will still be usable, even if the error is not dealt with right away. For help with the error handling modes, see the Agenda Process Control Help.
If your OpenCyc image is not starting up, and you see a message like:
style="line-height: normal;"> Loading init file: init/opencyc-init.lisp Error: Can't bind port XXXX.
This almost always means you already have a version of Cyc running. You must quit this version to start up a new one.
If you are unable to connect to the image and unable to find the emacs buffer it is running in, you can kill the image manually, using something like the following in a Unix/xterm window:
style="line-height: normal;"> ps auxww | grep cyc (to find the process id of cyc) kill -9 process_id (use that process id to kill cyc)