Awhile back I upgraded the “rack” gem on one of our CentOS Linux servers that runs LiteSpeed and Ruby. The upgrade took the rack gem from rack version 1.0.0 to rack version 1.0.1. After upgrading the Rack gem I attempted to visit the site located on the server where the gem was updated only to receive a 503 error from LiteSpeed. During the troubleshooting process I looked at the LiteSpeed error logs and noticed errors that lead me back to the Rack gem I had just updated. Below I describe the error in more detail and what can be done to resolve the issue of rack-1.0.1.
On accident today I discovered a really cool plugin for WordPress called the Error Reporting plugin. This plugin is a great tool to log any errors related to WordPress, WordPress plugins, etc. One of the options that the plugin provides is the ability to have each error emailed to you which could be overwhelming depending on what errors you are logging with the plugin. I like to log as much as possible so the problem for me was the fact that the error emails automatically go to the WordPress site administrator email address. My preference would be for this field to be an option that can be configured so I could create a new Gmail address and send all of the errors there. This way you can archive every single error message that has been generated for a long time because of Gmail’s 7GB+ storage capacity. So below I describe how to modify the email address the error logs are sent to along with a couple other items I modified while I was poking around.
After modify some Perl modules with CPAN I started getting the below errors in the Apache error_log.
[Sun Jul 12 14:15:03 2009] [notice] child pid 4329 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:27 2009] [notice] child pid 4331 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:30 2009] [notice] child pid 5065 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:31 2009] [notice] child pid 4339 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:48 2009] [notice] child pid 10111 exit signal Segmentation fault (11)
[Sun Jul 12 14:15:48 2009] [notice] child pid 4325 exit signal Segmentation fault (11)
You can disable Windows XP Operating System and application errors from being sent to Microsoft. Even though these errors are confidential and will not have your personal information attached to them disabling the errors will stop you from being prompted to send the errors to Microsoft every time something crashes or you kill a process. Also whenever these errors are disabled from being sent to Microsoft you have the option to either still notify you or to not do so. My recommendation would be that even though you disable the errors from being sent to Microsoft annonymously that you should definitely still be notified of these critical errors.
Follow the below steps which detail how to not send the errors to Microsoft but to still watn you of such errors.