Postgresql Error: ‘relation "settings" does not exist’ / Installation not working.

[Rike-Benjamin Schuppner]

Hi,

I tried to follow the Production Start and install Canvas on a Ubuntu Server (most recent version / also tested the LTS) using a postgresql database for production.

Unfortunately, on the final site, all I see is ‘Page Error –Well, looks like something broke. Sorry you had to see that.’

Are there any log files where I could look for an explanation?

I looked around a bit and found two strange things – I don’t know if these are related:

When I run

  RAILS_ENV=production $GEM_HOME/bin/bundle exec rake db:initial_setup

it seems to install most of the data to the postgresql database – however, I’m getting the following error messages:

2011-11-28 17:09:48 CET ERROR:  relation "settings" does not exist at character 245

2011-11-28 17:09:48 CET STATEMENT:              SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull

                      FROM pg_attribute a LEFT JOIN pg_attrdef d

                        ON a.attrelid = d.adrelid AND a.attnum = d.adnum

                     WHERE a.attrelid = '"settings"'::regclass

                       AND a.attnum > 0 AND NOT a.attisdropped

                     ORDER BY a.attnum

2011-11-28 17:09:57 CET ERROR:  relation "settings" does not exist at character 245

2011-11-28 17:09:57 CET STATEMENT:              SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull

                      FROM pg_attribute a LEFT JOIN pg_attrdef d

                        ON a.attrelid = d.adrelid AND a.attnum = d.adnum

                     WHERE a.attrelid = '"settings"'::regclass

                       AND a.attnum > 0 AND NOT a.attisdropped

                     ORDER BY a.attnum

Second, when I also use a development database and do the initial_setup on this one as well, the error disappears. Do I really need to use a separate dev database for my production server? This seems a bit strange to me…

Hope anybody can help. Thanks in advance.

Cheers

/rike

[Rike-Benjamin Schuppner]

The database problem could be solved by adding

SetEnv RAILS_ENV production

to the VirtualHost configuration. That one is obviously missing in the docs.

Cheers

/rike