Dyna|on|Rails

Skipping one version, since I got kinda lazy, NginX 0.5.23 is out with some fixes worth an upgrade.

The full changelog:
- Feature: the ngx_http_ssl_module supports Server Name Indication TLS extension.
- Feature: the “fastcgi_catch_stderr” directive.
- Bugfix: a segmentation fault occurred in master process if two virtual servers should bind() to the overlapping ports.
- Bugfix: if nginx was built with ngx_http_perl_module and perl supported threads, then during second reconfiguration the error messages “panic: MUTEX_LOCK” and “perl_parse() failed” were issued.
- Bugfix: in the HTTPS protocol in the “proxy_pass” directive.

Some more updates to NginX got released just today:

- Bugfix: if server has more than about ten locations, then regex locations may be choosen not in that order as they were specified.
- Bugfix: a worker process may got caught in an endless loop on 64-bit platform, if the 33-rd or next in succession backend has failed.
- Bugfix: a bus error might occur on Solaris/sparc64 if the PCRE library was used.
- Bugfix: in the HTTPS protocol in the “proxy_pass” directive.

It’s curious how several of the errors in the recent fixes have specifically come out on a 64-bit platform. I guess we’re still having issues with that just like Vista drivers of the same nature >.<

NginX has come out with a new version, 0.5.20. There were enough changes over the last few versions to definitely warrant an upgrade, which took an overly complicated minute /sarcasm. It probably would have taken less time if I could not make typo’s XD

I can’t really argue with this, nginx, mysql, php-cgi:

@redvps:/usr/local/nginx/sbin$ free -m
total used free shared buffers cached
Mem: 254 233 21 0 36 68
-/+ buffers/cache: 127 126
Swap: 511 4 507


Even though I’m still running release 0.5.16, there haven’t really been any changes that would significantly influence me to rush the upgrade, it is nice to see that release 0.5.18 is out. For completeness sake here’s the changelog:

Feature: the ngx_http_sub_filter_module.
Feature: the “$upstream_http_…” variables.
Feature: now the $upstream_status and $upstream_response_time variables keep data about all upstreams before X-Accel-Redirect (These are actually pretty cool, and will give you more data on what exactly the times are after NginX passes off the work )

Bugfix: a segmentation fault occurred in master process after first reconfiguration and receiving any signal if nginx was built with ngx_http_perl_module and perl did not support multiplicity; bug appeared in 0.5.9.
Bugfix: if perl did not support multiplicity, then after reconfiguration perl code did not work; bug appeared in 0.3.38.