Archive for the ‘Break-Fix’ Category

Varnish not responding to CLI, killing it died signal=3 Explained

The error below is typical in a new Nginx installation for a busy web site. Nginx apparently hits a user resource as well as configuration limitation:

Nginx accept() failed (24: Too many open files) while accepting new connection
here’s how to fix this Nginx error.

Here is a workaround to the Drupal imagecache issue with Nginx running as a reverse proxy to Apache.

Depending on which version of Varnish you have running, there is a chance the code is still experimental and the whole Varnish daemon is prone to a fatal crash. Here is a quick and dirty monitoring script for Varnish. It essentially runs as a crontab job and requests a PING response. Should it not receive [...]

Howdy! The above error can come up quite often on a busy database-driven website or it could happen at one time or the other for different reasons. Today, we are going to cover the main two reasons for it happening. I shall break this down by architecture. Linux x86_64 (64-bit) The Out of memory error [...]

phpBB is a open source forum software. The board’s index page lists the topics along with a listing of online members. While trouble shooting a customer report of a slower loading of the board “index” page, we found out that the fix in itself is simple and easy to implement. We would like to share [...]

« Older Entries -