Nginx

Nginx 1.2.8

Nginx 1.2.8 has been released with 4 bugfixes. See the full Changelog for more details.

As a consequence, Dotdeb’s packages of Nginx 1.2.8 are now available for Debian 6.0 “Squeeze” (amd64/i386) with the following changes :

The config of the default vhost is now ok by default (see [Edit]).
The X-rid header module has been added to all the Nginx flavors.
The chunkin-nginx-module, headers-more-nginx-module, nginx-cache-purge, nginx-echo, nginx-lua, nginx-push-stream-module and ngx_http_substitution_filter_module modules have been updated.

As usual, if you want to know which module has been included in each Nginx flavor, you just have to look at this document.

[Edit] A minor update (1.2.8-1~dotdeb.2) has been published :

it now displays errors at startup, if any
the ipv6only typo has been fixed, the default vhost now works perfectly.

Tags Nginx, release

20 replies on “Nginx 1.2.8”

And again thank you Guillaume!
Just a small hint, a nginx -v command print out the old version 1.2.7.

nginx -v
nginx version: nginx/1.2.8

Wups, Thanks. Checked again, my upgrade was not complete…..

Again, init.d script init.d script does not show an error.
https://github.com/gplessis/dotdeb-nginx/issues/32

In my test vps, I have get the same error,
it said “invoke-rc.d: initscript nginx, action “start” failed.”

invoke-rc.d: initscript nginx, action “start” failed.
dpkg: error processing nginx-extras (–configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
nginx-extras
E: Sub-process /usr/bin/dpkg returned an error code (1)

On upgrade (nginx-full) I got the same error as Cronner.

Three other problems.
1. Despite selecting “no” to replace the old default config file, it was replaced anyway. /etc/nginx/sites-available/default was moved to /etc/nginx/default.dpkg.old
2. The new default config has a typo in it. ipv6_only instead of the correct ipv6only.
3. Fixed the above issues and did a nginx configtest.
/etc/init.d/nginx configtest
[ ok ] Testing nginx configuration:[….] nginx:.

Everything looks fine now so tried a restart and now I am getting:

/etc/init.d/nginx restart
[….] Restarting nginx: nginxnginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()

Did fuser -n tcp 80 and found 4 running processes so I tried a nginx stop. Output said it stopped but it didn’t so I did a kill -9 for each pid and then a nginx restart and everything was fine.

Not really sure why this happened but at least I found a fix for it. Credit to http://ibnuyahya.com/nginx-emerg-bind-to-0-0-0-080-failed-98-address-already-in-use/

Terry

Oh, sorry for the ipv6_only => ipv6only typo, I’m building new packages that will fix it.

Great! It works. Now I can start nginx. Thanks.

What comman it is correct to update Nginx?

from repositories

I’ve also got nginx -v 1.2.7

apt-get dist-upgrade fixed it.

Still stuck on 1.2.4. This is after update/upgrade and dist-upgrade as Plazik suggested above. Any ideas?

I wonder is there any advantage of taking nginx from dotdev.org over the Nginx from official repos at nginx.org ?

@Pawel : it’s up to you. With Nginx packages from Dotdeb, you can choose between 5 flavors, each with its own combination of core/official/3rd-party modules, depending on your needs.