Canvas Page Error - Oops! It Looks Like Something Broke

[Mario DeFazone]

I see "Oops! It Looks Like Something Broke" page instead of the login screen. 

/var/www/canvas/log/production.log is available at http://pastebin.com/xTiutRwy

[Cody Cutrer]

You need to upgrade your redis server.

Cody Cutrer

Software Engineer

Instructure

On Wed, Feb 19, 2014 at 2:44 PM, Mario DeFazone <funact...@gmail.com> wrote:

I see "Oops! It Looks Like Something Broke" page instead of the login screen. 

/var/www/canvas/log/production.log is available at http://pastebin.com/xTiutRwy

--
 
---
You received this message because you are subscribed to the Google Groups "Canvas LMS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to canvas-lms-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Mario DeFazone]

Updated redis and still see this error message. 

redis-server -v
Redis server v=2.8.6 sha=00000000:0 malloc=jemalloc-3.2.0 bits=64 build=788a0cdf1d3a47f2

New (?) log: http://pastebin.com/8dfwM16g

[Ryan Marsh]

If you look at the instructions in the Deployment guide, upgrading isn't enough. You need to completely uninstall 2.3 and then install 2.8. Looking at your production log, you're still getting 'evalsha' command errors which is a Redis command that is only supported on newer versions of Redis (2.6+).

[Midiman]

Hey, this thread totally helped me! When doing a fresh install with Ubmutn 12.04.3 LTS, the section on Redis has a subtle aside on notifying users that an old version of Redis is in the Precise Pangolin Repositories. Since the instructions advocate that Ubuntu 12.04 LTS server can be used for a production environment, I wish the GIT wiki maintainer would just add the following instructions under the Redis section header:

Ubutntu 12.04 LTS users, add this PPA to your list of Repositories:

sudo apt-add-repository ppa:chris-lea/redis-server

Instructure GIT repo managers: This is the format used for the External Dependencies section to make sure Ruby 1.9.3 is selected properly, so why not update your instructions on this page to have this be a little more clear?