[Users] https://bugzilla.openvz.org/show_bug.cgi?id=2470

[Gena Makhomed]

On 23.07.2015 5:44, Kir Kolyshkin wrote:

>>>> 1) currently even suspend/resume not work reliable:
>>>> https://bugzilla.openvz.org/show_bug.cgi?id=2470
>>>> - I can't suspend and resume containers without bugs.
>>>> and as result - I also can't use it for live migration.
>>>
>>> Valid point, we need to figure it out. What I don't understand
>>> is how lots of users are enjoying live migration despite this bug.
>>> Me, personally, I never came across this.
>>
>> Nevertheless, steps to 100% reproduce bug provided in bugreport.
>
> I was not saying anything about the bug report being bad/incomplete.
> My point was, the feature works fine for many people despite this bug.

You want to see entire picture? Ok.

All works fine from POV of administrator of hardware node.
 From POV of administrator of VPS/VDS - all works fine,
but unexpectedly nginx config test fails - and this is
for administrator of VDS/VPS looks like nginx bug,
I even see bugreports about unexpected failed config
tests in nginx mail list. People say: on FreeBSD
nginx config test works fine, but on Linux
it sometimes fails, sometimes works fine.

But root cause of this nginx "bug" - is OpenVZ bug:
https://bugzilla.openvz.org/show_bug.cgi?id=2470

See also how this OpenVZ bug described in Odin KB:
http://kb.odin.com/en/116197

The problem is caused by a race condition in nginx init script 
(/etc/init.d/nginx), which causes the service start attempt to begin 
before all nginx worker processes are properly shut down.

This behavior was confirmed to be a software issue with ID #PPPM-353.

=====================================================================

but this is not nginx init script bug!!!

you can see nginx init script sources here:
http://nginx.org/packages/mainline/centos/6/

"service nginx restart" just test configuration before
restarting server and config test failed due to OpenVZ bug.

also config test performed before nginx upgrading executable on the fly.

information about "race condition in nginx init script" is not true.

And this false information about such non-existent bugs in nginx
looks like FUD and something like "Damage to business reputation".

Because nginx is web server with high quality code and algorithms,
see for example, http://nginx.org/en/docs/control.html#upgrade

Can you please update information at the http://kb.odin.com/en/116197
page, and describe there what this is not nginx bug, but OpenVZ bug ?

compare:

https://bugzilla.openvz.org/show_bug.cgi?id=2470

[root at mamonov /]# nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] listen() to 0.0.0.0:80, backlog 511 failed (98: Address 
already in use)
nginx: configuration file /etc/nginx/nginx.conf test failed

=============================================

http://kb.odin.com/en/116197

Unable to generate the web server configuration file on the host 
<plesk11.test> because of the following errors:
  nginx: [emerg] listen() to 10.0.0.1:80, backlog 511 failed (98: 
Address already in use)
  nginx: configuration file /etc/nginx/nginx.conf test failed

=====================================================================

-- 
Best regards,
  Gena