Closed Darkera524 closed 6 years ago
The capture session may not be shutting down properly. Killing the process without shutting the capture session down can cause the issue you are describing.
But I did not kill the python script process directly.As the code above,when it is shutting down depends on the info returned from the port 8093 or the alive of the port 8093.I just kill the process that listening 8093,then the python scripts process exit after execing the job.stop().I would appreciate it if you help me with the following question.
If the capture session is not stopped,how can I find the session and stop it? To see if session is still running use the command - logman -ets To stop capture session - logman -ets "session name" stop
How can I avoid happenning of this? When stop() is called the capture session will stop.
Thanks a lot! Besides this,I find another performance problem that when the trace info is very large,for example the dns access log info,the job.start() prints the info slowly,then do you have some suggestion of how can I improve the performance of it
There is an option that will disable output to the console. That may help.
Closing.
I am using this module to capture the info of the dns server.At the beginning,everything is ok and I can capture the log,but when I stop the process once,I can't capture the info of this provider unless I reboot the windows,but the other provider can capture as usual.When I use it in product,I can't reboot system at any time,so how could I solve the problem?The following is my code.Thanks!