I’m a Richardson, RU?

See and download the full gallery on posterous
or here on flickr

Posted via email from imarichardson’s posterous

Just in time for Halloween, a scary movie of epic proportions - a tale of when a Mac gets a virus… (via TUAW)

If you are caught somewhere between subversion 1.4  and 1.5 then you’ll suddenly find yourself one day presented with the message: 

I originally found myself here while beta testing a new subversion client and inadvertently clicking “yes” I want to upgrade my working directory. But that’s another story. Here’s what I did (I’m running Mac OSX 10.5 Leopard):

1. Download and install the Subversion 1.5 binaries from OpenCollabNet (via http://subversion.tigris.org/getting.html#osx). Once you download the .dmg, simply run the installer like you’d normally do any installer. You’d imagine that this would be all but it’s not because the new subversion installs to /opt/subversion/bin rather than /usr/bin.
2. Update your path by either editing the “~/.profile” (for your individual user profile) or “/etc/profile” (for all system users). I chose to do this for my system as I used several accounts for different purposes. If the file doesn’t exist you need to create it. Then add the following line to the top of the file: 
   export PATH=/opt/subversion:$PATH
3. Finally, rename the previous svn executable. You may find that you still cannot access subversion 1.5 if the 1.4 file is still available. Navigate to your /usr/bin folder and rename the old svn located there:
   $sudo mv svn svn.old
   • Thanks much Coals [2] Newcastle for helping me with this one. 
4. Now when running svn –version you should see the 1.5 client referenced.

This is “wet-my-pants” kinda funny.

For a good deal of time I’ve been experiencing numerous problems relating to mongrel and mongrel_cluster. I’ve received proxy errors from my main site:

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.

Reason: Error reading from remote server

---

Apache/2.2.3 (Red Hat) Server at [myserver.com] Port 443

And when viewing the log files I was receiving errors like:

And this, too: (I tried these instructions too, but didn’t work.)

Additionally, I received “Operation Not Permitted” errors when trying to restart and/or stop the mongrel clusters:

Solution

I was able to resolve the issue by killing all the active Mongrel processes and then restarting manually. You can do this by:

1. Viewing all active mongrel processes:

(The second number is the process id; that is the id you’ll use to kill the process.)


2. Killing each process id

“sudo kill -9 [process id]“, For example, to kill the first process listed above:

3. Restarting your Mongrel instances