Is there known way to reproduce already closed issue

[Aleš Bregar]

Hi,

I have one setup (nginx 1.2.8 and push module 0.3.5) and seems that is affected by

https://github.com/wandenberg/nginx-push-stream-module/issues/154
https://github.com/wandenberg/nginx-push-stream-module/issues/100

due I see following in the logs
nginx-push[21756]: segfault at 0 ip 0000000000497c06 sp 00007fff91619360 error 6 in nginx-push[400000+c8000]
nginx-push[6306]: segfault at 0 ip 0000000000497c06 sp 00007fff91619300 error 6 in nginx-push[400000+c8000]
nginx-push[19285]: segfault at 2ccdfc98 ip 000000000049d509 sp 00007fff916193d0 error 4 in nginx-push[400000+c8000]
nginx-push[13728] general protection ip:49d537 sp:7fff916193d0 error:0 in nginx-push[400000+c8000]
nginx-push[6305]: segfault at 0 ip 000000000049d537 sp 00007fff91619370 error 6 in nginx-push[400000+c8000]
nginx-push[25129]: segfault at 44c1c4 ip 000000000049d54d sp 00007fff916193d0 error 7 in nginx-push[400000+c8000]
nginx-push[2664]: segfault at 0 ip 0000000000497c06 sp 00007fff91619360 error 6 in nginx-push[400000+c8000]

My question is if there are some known cause of the issues (and possibly know-how to reproduce those) mentioned above so I can try out of production site before going into full debug?

Thank you in advance and best regards

[Wandenberg Peixoto]

Hi,

Those problems are hard to reproduce locally, they depended of the load, concurrency and if the client closes the connection at some specific moments.

I suggest you to move to the latest release of the module, update one of your servers and compare to the old ones.

Regards,

Wandenberg

--
You received this message because you are subscribed to the Google Groups "nginxpushstream" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nginxpushstre...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.