nil.unpack error+discussion

First off, thanks for all the contextual info.  Very helpful.

It seems pretty clear that the problem is with the uuid gem, though I'm not immediately certain I know how to fix it.  You don't have the gem installed locally; it's in /vendor/plugins.  I'd have to ask around to figure out how that got there; I don't think it's usually there for folks who do the git install, so it may be a legacy thing.

If I were working on this, the first thing I would try would be moving the gem out of /var/www/wagn/vendor/gems/ into some holding space and installing the gem locally.

In any case, Wagn only makes a very basic call to the uuid gem (UUID.new.generate), and it's failing, so it's pretty clear the problem is pretty localized.

Let us know if the above doesn't work.

-e

My vendor/gems/ (the uuid gem was not in vendor/plugins/) looks like this:

# ls -la vendor/gems/

total 28

drwxr-xr-x 7 www-data www-data 4096 2010-05-11 09:40 .

drwxr-xr-x 5 www-data www-data 4096 2010-05-11 09:40 ..

drwxr-xr-x 3 www-data www-data 4096 2010-05-11 09:40 assert2-0.5.5

drwxr-xr-x 10 www-data www-data 4096 2010-05-11 09:40 json-1.1.7

drwxr-xr-x 3 www-data www-data 4096 2010-05-11 09:40 macaddr-1.0.0

drwxr-xr-x 6 www-data www-data 4096 2010-05-11 09:40 ruby-openid-2.1.7

drwxr-xr-x 4 www-data www-data 4096 2009-09-10 08:32 uuid-2.0.2

I have moved both the macaddr (this is a dependancy of the uuid gem) and uuid gem elsewhere and installed them system-wide.

This has fixed my issue.

  --Charl Matthee (Not signed in).....Wed Dec 15 13:08:23 -0800 2010

Oh, great. Thanks for letting us know what you did. (yeah, I meant vendor/gems, not vendor/plugins)

  --Ethan McCutchen.....Wed Dec 15 16:09:52 -0800 2010