Good Habit: stop the service on the control panel

From last night, coreseek still had a strange problem. As a result, I didn't feel good at night.

You can search successfully in the command line, but once you call the API, it will be very strange, no matter whether it is a field or the original attribute, It is the previous situation. Index creation is successful, and the port is also listening, but the results are still problematic. After more than an hour of cooperation with our lab Eldest Brother and second brother, we finally found the problem.

When you stop a service in task manager, you can still call API Search ,!!! It indicates that the searchd service has not been stopped. Then, use netstat-a-o to check the port listening status and find that a searchd program is still running under the task manager. It is a success to restart the service after he finishes.

The reason is that when you stop the service in the task manager, the service itself is stopped, but the instance process created by the service itself is not stopped. There has been a listener, and this instantiation program still uses the original configuration file. Of course, the search will be weird.

So we need to stop the service under the control panel, so that the corresponding instance process will also stop, and there will be no problems I encountered.