Re: CRITICAL:root:Error running database evolver function change_column_attr_unique:

2015-07-06 Thread John Schmitt
The Apache HTTP Server... Jul 04 11:07:44 dyn40-62-43.tintri.com rb-site[2066]: CRITICAL:root:Error running database evolver function change_column_attr_unique: Jul 04 11:07:44 dyn40-62-43.tintri.com rb-site[2066]: Traceback (most recent call last): Jul 04 11:07:44 dyn40-62-43.tintri.com rb-site

Re: CRITICAL:root:Error running database evolver function change_column_attr_unique:

2015-07-05 Thread Christian Hammond
Hi John, It looks like what's happening is that the database upgrade process is expecting your old database to have a unique index/constraint for a field (marking a particular column as being unique across entries in the table), which it doesn't have for some reason. What I'd suggest is: 1)

Re: CRITICAL:root:Error running database evolver function change_column_attr_unique:

2015-07-04 Thread Christian Hammond
to start httpd: Jul 04 11:07:32 dyn40-62-43.tintri.com systemd[1]: Starting The Apache HTTP Server... Jul 04 11:07:44 dyn40-62-43.tintri.com rb-site[2066]: CRITICAL:root:Error running database evolver function change_column_attr_unique: Jul 04 11:07:44 dyn40-62-43.tintri.com rb-site[2066

Re: CRITICAL:root:Error running database evolver function change_column_attr_unique:

2015-07-04 Thread John Schmitt
The Apache HTTP Server... Jul 04 11:07:44 dyn40-62-43.tintri.com rb-site[2066]: CRITICAL:root:Error running database evolver function change_column_attr_unique: Jul 04 11:07:44 dyn40-62-43.tintri.com rb-site[2066]: Traceback (most recent call last): Jul 04 11:07:44 dyn40-62-43.tintri.com rb