If you you receive the following with a Ruby on Rails site: Ruby On Rails Error: Only specific requests are allowed. code ActionController::MethodNotAllowed Only get, head, post, put, and delete requests are allowed. The solution is to kill existing web/app server processes and restart the web/app server. Then, reload the page.
Earlier I switched one of the Litespeed web server virtual hosts from production mode to staging mode and after gracefully restarting rails was receiving a 503 Service Unavailable error. Initially I thought that maybe Litespeed had to be restarted completely instead of just a graceful restart but that produced the same results. Below I describe…
I ran into an issue earlier where adding a sub project to an already existing Redmine project produced an error and after a little bit of troubleshooting determined that upgrading Redmine would resolve the issue. During the upgrade process I ran into some other issues including a specific migration error using rake that is noted…
When I installed MacPorts 1.8.2 on MacOS X 10.5.8, it automatically changed my PATH in my .bash_profile file. To fix the “rubygems (LoadError)” error message, I moved the “/opt/local/bin” from the beginning of the PATH to the end as follows:
I was troubleshooting an issue at work the other day regarding some PostgreSQL connections that were not closing. They were left IDLE, never closed, and eventually used up all of the possible connections (which totaled 100) configured in the postgresql.conf configuration file. In the process of troubleshooting I noticed a bunch of Postgres log entries…
I assisted in looking into a Rails issue earlier with a friend. After making some modifications to some Ruby code he had an issue receiving exception emails which were generated by Rails. The rails plugin being used to accomplish this is called exception_notification and resolving the problem was simple. As you will see below instead…
The other day I did some optimization work on a PostgreSQL database and at the end needed to create migrations so the changes I was going to make could be deployed on multiple servers. It was my first shot at migrations so I wanted to note for myself and anyone else that may find it…
A friend of mine was over tonight and we were troubleshooting a issue with SVN authentication via the Redmine project management software. Redmine is built with Ruby and on this server is running via Apache and Mongrel. I needed to set the project to run in development mode but wasn’t very familiar with the Mongrel…
A friend of mine let me know about a vulnerability in Redmine today so I decided to upgrade to the latest stable release. Upgrading Redmine is easy but figured I would log the exact steps I took to upgrade from Redmine 0.8.3 to Redmine 0.8.7. The installation of Redmine I upgraded is running off of…