Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PG::UndefinedTable: ERROR: relation "sidekiq_jobs" does not exist #39

Open
supremebeing7 opened this issue Jul 15, 2015 · 4 comments
Open

Comments

@supremebeing7
Copy link

I installed this once without issue, but was getting this error when my CI was trying to run rake db:schema:load:

/gems/ruby-2.2.2/gems/activerecord-4.2.3/lib/active_record/connection_adapters/postgresql_adapter.rb:596:in `async_exec': PG::UndefinedTable: ERROR:  relation "sidekiq_jobs" does not exist
LINE 5:                WHERE a.attrelid = '"sidekiq_jobs"'::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 = '"sidekiq_jobs"'::regclass
                 AND a.attnum > 0 AND NOT a.attisdropped
               ORDER BY a.attnum
 (ActiveRecord::StatementInvalid)

I've since dropped my local database, removed all traces of the gem (or so I thought), recreated and re-migrated, and attempted to install the gem again. As soon as I add to my Gemfile, if I try to run rake db:migrate or rake db:rollback, it gives me the above error. I also get this error when trying rails g sidekiq:monitor:install.

Has anyone seen this before? I thought it might be just my database being messed up, but I'm working off a fresh db and getting this.

@jdraths
Copy link

jdraths commented Dec 15, 2015

+1 I'm having the same issue. Did you find a solution for this?

@supremebeing7
Copy link
Author

Unfortunately, the only solution I found was uninstalling the gem. As soon as I did, the problem went away. I didn't have time to dig into the gem internals to try to figure it out.

@janephilipps
Copy link

+1 I'm having this issue in production. Going to try testing by uninstalling the gem.

@yogev1
Copy link

yogev1 commented Dec 11, 2018

same issue here. bummer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants