Open zspirate opened 4 years ago
@zspirate Thanks for the information. We will check and comeback on this. BTW what is the version of QAT Engine you are using ?
@zspirate In order to help us recreate your problem and to check whether your version of QAT engine is missing any fixes in this area in later releases of QAT engine, could you provide complete version info for QAT Engine, nginx and QAT driver? Thanks.
@zspirate Also Can you please use latest OpenSSL version (1.1.0l or 1.1.1f). Similar issue is fixed in this commit 6038.
@zspirate Thanks for the information. We will check and comeback on this. BTW what is the version of QAT Engine you are using ?
I use the latest version of qat engine,the openssl is 1.1.1b, the nginx is 1.16(with intel qat async patch), and the driver is 1.7.0
Hi @zspirate We are currently looking into this. Please could you forward the QAT driver config files you used when this core dump was created together with the nginx.conf file (as an attachment). Many thanks in advance. paulturx
Hi @zspirate We are currently looking into this. Please could you forward the QAT driver config files you used when this core dump was created together with the nginx.conf file (as an attachment). Many thanks in advance. paulturx here is the conf files
Hi @zsprirate We would be very interested to see whether you are able to reproduce the problem on your set-up with the nginx.conf parameter 'multi_accept' set to 'off' (or else not specifically set at all since the default is 'off') and get back to us with the results. Thanks in advance, paulturx
Hi @zsprirate We would be very interested to see whether you are able to reproduce the problem on your set-up with the nginx.conf parameter 'multi_accept' set to 'off' (or else not specifically set at all since the default is 'off') and get back to us with the results. Thanks in advance, paulturx
it works!!!,no coredump anymore, but i still don't understand why this parameter 'multi_accept' affect
I would also like to understand this better. Is there a limit to the number of connections accepted? Is this related to how qat_pause_job()/qat_wake_job()
behave?
I would also like to understand this better. Is there a limit to the number of connections accepted? Is this related to how
qat_pause_job()/qat_wake_job()
behave?
this problem occurs again,confused。
Hi: I'm running nginx in openssl 1.1.0e and qat driver of version 1.7, the nginx worker sometimes crashes in function ASYNC_WAIT_CTX_get_fd, not very often, it seems that the async job allocated by openssl has been released while qat engine is starting to wakeup the async job, here is the coredump stack:
this situation may happen when the SSL can not be established while the qat is still working on crypto steps, if the async timer was out of time, the nginx call ngx_ssl_shutdown() anyway to stop this session, but the async jobs can not be released,the qat can still wakeup the job when it finished work. how to solve this problem? it seems that the openssl lib does not provide the api to release the async job for user apps.