Today, Nginx 1.2.7 has been released with a few new features but also bugfixes merged from 1.3.x. See the full Changelog for more details.
As a consequence, Dotdeb’s packages of Nginx 1.2.7 are now available for Debian 6.0 “Squeeze” (amd64/i386) with the following changes :
- Logs are now rotated on a weekly basis.
- Passenger has been upgraded to the 3.0.19 version.
- The
chunkin-nginx-module,nginx-luaandnginx-upload-modulemodules got minor updates.
As usual, if you want to know which module has been included in each Nginx flavor, you just have to look at this document.
websites went down tried “service nginx restart” Restarting nginx: nginxnginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
First time it’s happened using nginx-extras
I run a update on my Debian Box to the new version and find this strange behavior. I try to explain this bug.
First the Installation error: http://pastebin.com/8f4qHAE0
After a second run of apt-installation there was still nginx 1.2.6 running. I killed all PIDs of them manually. As next step I tried to start nginx /etc/init.d/nginx start
Result: no output and nginx was not running.
As next step I checked my configuration manually:
root@nginx:~# /usr/sbin/nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: [emerg] open() “/var/log/nginx/domain/subdomains/kernel/access.log” failed (2: No such file or directory) nginx: configuration file /etc/nginx/nginx.conf test failed
The rc-script was modified and don’t show any error messages if they occur.
I compare init scrips of both version (1.2.7 and 1.2.6) Version 1.2.6 shows my mistake and version 1.2.7 is silent.
Hi,
I see Debian released a security update for Nginx yesterday, disabling SSL compression due to CVE-2012-4929
http://www.debian.org/security/2013/dsa-2627
I read that nginx upstream had disabled SSL compression in 1.2.2: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700426
Just wanted to confirm if the dotdeb.org also has this fix already or will a fix be released?
Thanks!
Hello Guillaume,
I was wondering if you could tell me all of the configure options if i want to compile nginx from source to be like your nginx-full package?
I LOVE your work…. your packages are so helpful. But i recently switched to wheezy… and none of your packages work, even if i have a newer version of their dependencies.
I cannot move back to squeeze though… so i would like to try re-creating your nginx-full package.
Any help is greatly appreciated.
Thank you in advance.
This is excellent…. thank you so much Guillaume.
Do you have the same thing for php?
I would like to use the latest php5-fpm, php5-apc, php5-cli, and php5-geoip.
But wheezy does not have any packages available that use the latest versions.
Thank you in advance!
I could not get them to work under any circumstances.
The packages said that they need very specific dependencies that are not available in wheezy…. allow me to paste what i am getting when trying to install dotdeb packages… if you do not mind. And btw… i sincerely appreciate your help in any form.
root@black~ $ aptitude install php5-fpm The following NEW packages will be installed: php5-fpm{b} 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 2,724 kB of archives. After unpacking 8,548 kB will be used. The following packages have unmet dependencies: php5-fpm : Depends: libdb4.8 which is a virtual package. Depends: libssl0.9.8 (>= 0.9.8m-1) which is a virtual package. Depends: php5-common (= 5.4.11-1~dotdeb.0) but it is not going to be installed. The following actions will resolve these dependencies:
Accept this solution? [Y/n/q/?]
Has anybody encountered this Nginx error upon trying to start or restart Nginx?
Starting nginx: nginxnginx: invalid option: “5”
I’ve tried rebooting 3x and did ’nginx remove’ and then ‘sudo apt-get install nginx-full’ and still get this same error. I did install beanstalkd and memcached recently, but they are up and running, so I don’t think it’s related to that. I think it’s just an nginx issue after this last upgrade.
I got it working, though by guess and check so I hope I didn’t screw the pooch on it.
I opened /etc/init.d/nginx found start() and stop() which both had “5” in it. After trying to change to the value to 4, I still had the error, but this time with “invalid option: 4”. So I deleted the number. And it works! Here’s the code from /etc/init.d/nginx in case it helps future googlers. http://pastebin.com/BLHzKtfR
Nginx not write to the log error. Just do not print it out on the console. Then install nginx from the official repository. Got the console error.
nginx: [emerg] could not build the server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64
Other errors not display too. FIX please.