Gitlab CI给出500,错误:relation“;“会议”;不存在

Gitlab CI给出500,错误:relation“;“会议”;不存在,gitlab,gitlab-ci,Gitlab,Gitlab Ci,因此,我使用omnibus包将Gitlab从7.1.1升级到7.7.2 升级后,我决定尝试一下Gitlab CI,并将CI_external_url行添加到/etc/Gitlab/Gitlab.rb,但当我浏览到定义的url时,我得到一个500错误,日志输出如下: Started GET "/" for 1.3.3.7 at 2015-02-04 09:14:35 +0200 Processing by ProjectsController#index as HTML PG::Undefined

因此,我使用omnibus包将Gitlab从7.1.1升级到7.7.2

升级后,我决定尝试一下Gitlab CI,并将
CI_external_url
行添加到/etc/Gitlab/Gitlab.rb,但当我浏览到定义的url时,我得到一个500错误,日志输出如下:

Started GET "/" for 1.3.3.7 at 2015-02-04 09:14:35 +0200
Processing by ProjectsController#index as HTML
PG::UndefinedTable: ERROR:  relation "sessions" does not exist
LINE 5:                WHERE a.attrelid = '"sessions"'::regclass
                                          ^
:               SELECT a.attname, format_type(a.atttypid, a.atttypmod),
                     pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod
                FROM pg_attribute a LEFT JOIN pg_attrdef d
                  ON a.attrelid = d.adrelid AND a.attnum = d.adnum
               WHERE a.attrelid = '"sessions"'::regclass
                 AND a.attnum > 0 AND NOT a.attisdropped
               ORDER BY a.attnum

Redirected to 
Completed 500 Internal Server Error in 5ms

ActiveRecord::StatementInvalid (PG::UndefinedTable: ERROR:  relation "sessions" does not exist
LINE 5:                WHERE a.attrelid = '"sessions"'::regclass
                                          ^
:               SELECT a.attname, format_type(a.atttypid, a.atttypmod),
                     pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod
                FROM pg_attribute a LEFT JOIN pg_attrdef d
                  ON a.attrelid = d.adrelid AND a.attnum = d.adnum
               WHERE a.attrelid = '"sessions"'::regclass
                 AND a.attnum > 0 AND NOT a.attisdropped
               ORDER BY a.attnum
):
  app/controllers/application_controller.rb:76:in `check_config'

我正在Debian 7上运行此操作。

要么您尚未迁移数据库(
rake db:migrate
),要么您已经迁移,并且您的代码正在使用不存在的数据库表

尝试迁移,看看这是否解决了您的问题


更新:对于其他有相同问题的人来说,Gitlab的命令似乎是Gitlab ci rake db:migrate我发现集成信息check
sudo-u git-H bundle exec rake Gitlab:check RAILS\u ENV=production
是Gitlab中最有用的命令。它可以突出显示更新过程中可能遇到的许多问题。除了常规的权限问题外,它还标识缺少的数据库更新


除此之外,我们还将严格遵循指南,因为它们包含了我们目前所需的所有步骤(我们不使用omnibus)。

对于gitlab来说,文档有点混乱,但您是对的:gitlab ci rake db:migrate完成了trickNice!那么@Tebro,你能把我的答案标记为正确的答案吗?谢谢当然,只需等待计时器耗尽;)