Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su d iscourse -c 'bundle install --deployment --verbose --without test --without deve lopment'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bu ndle exec rake assets:precompile'"]}
3f1727b6fec9e30bde95e2a47c13e710204c52f8a934e8181455be57985faa3a
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one
```
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [August 11, 2017, 6:04am UTC](https://meta.discourse.org/t/update-failed-due-to-primary-key-sequence-error/67852/2 "2017-08-11T06:04:16Z")
That seems like something has gone terribly, terribly wrong with your database, and the primary key sequence has gotten out of sync with the table, which… shouldn’t happen. What’s your setup (plugins, etc)?
I’d be interested to know what the record with `id`=`629` in your database _is_. Try running the following commands from the same directory as you run `./launcher rebuild app`:
```
./launcher enter app
su - discourse
psql
select * from schema_migration_details where id=629;
```
(To get back to the shell you started in, you’ll need to use `\q` to get out of `psql`, then `exit` twice)
The output of that `select` command should be interestingly informative.
---
### Author:  [@mdxdave](https://meta.discourse.org/u/mdxdave)
#### Post date: [August 11, 2017, 6:19am UTC](https://meta.discourse.org/t/update-failed-due-to-primary-key-sequence-error/67852/3 "2017-08-11T06:19:01Z")
Thanks for your quick reply 🙂
The setup is nothing special (no plugins, etc), its only a internal discussion board for team members.
The output from the `select` command:
```plaintext
discourse=> select * from schema_migration_details where id=629;
id | version | name | hostname | git_version | rails_version | duration | direction | created_at
-----+----------------+-----------------------+--------------+------------------------------------------+---------------+----------+-----------+----------------------------
629 | 20160317174357 | CreateGivenDailyLikes | 3d46f5a80e55+| d3a975e99a12a009cf6856de2512546264d6d952 | 4.2.8 | 229 | up | 2017-07-26 03:33:47.099986
| | | | | | | |
(1 row)
```
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [August 11, 2017, 6:56am UTC](https://meta.discourse.org/t/update-failed-due-to-primary-key-sequence-error/67852/4 "2017-08-11T06:56:05Z")
Well that’s mysterious. I was kinda expecting to find some rando rubbish in that record, but it looks like a regular migration.
More DB investigation: can you provide the output of the following commands, again in the `psql` command line (get in the same way as last time):
```
\d schema_migration_details_id_seq
select count(id),max(id) from schema_migration_details;
```
The first of these should produce a table that includes a line for `last_value`, while the second should just show how many rows and what the max value of the `id` column is. That’ll at least show the nature of the damage, although I doubt it’ll tell us exactly _why_ it happened.
---
### Author:  [@mdxdave](https://meta.discourse.org/u/mdxdave)
#### Post date: [August 11, 2017, 7:08am UTC](https://meta.discourse.org/t/update-failed-due-to-primary-key-sequence-error/67852/5 "2017-08-11T07:08:33Z")
```plaintext
discourse=> \d schema_migration_details_id_seq
Sequence "public.schema_migration_details_id_seq"
Column | Type | Value
---------------+---------+---------------------------------
sequence_name | name | schema_migration_details_id_seq
last_value | bigint | 629
start_value | bigint | 1
increment_by | bigint | 1
max_value | bigint | 9223372036854775807
min_value | bigint | 1
cache_value | bigint | 1
log_cnt | bigint | 32
is_cycled | boolean | f
is_called | boolean | t
Owned by: public.schema_migration_details.id
discourse=> select count(id),max(id) from schema_migration_details;
count | max
-------+-----
749 | 749
(1 row)
```
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [August 11, 2017, 7:27am UTC](https://meta.discourse.org/t/update-failed-due-to-primary-key-sequence-error/67852/6 "2017-08-11T07:27:49Z")
Oh… kay. That’s not entirely what I was expecting. In a perfect world, I’d love to know how you’ve managed to end up with a sequence so far out of whack, but I’m guessing we’re not going to live in a perfect world today.
The easy solution is run the following in `psql`:
```
alter sequence schema_migration_details_id_seq restart 750;
```
That’ll get the sequence back on track, and will stop the error from occuring. _However_, without knowing how this happened (I’ve _never_ seen it happen before, and I’ve been doing this a long time), I can’t guarantee there might not be other craziness lurking in your database. You may well be in for a rough time.
---
### Author:  [@mdxdave](https://meta.discourse.org/u/mdxdave)
#### Post date: [August 12, 2017, 1:11am UTC](https://meta.discourse.org/t/update-failed-due-to-primary-key-sequence-error/67852/7 "2017-08-12T01:11:17Z")
Thanks for your help.
It worked now. Installed version is now v1.9.0.beta5 +123 😄
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [August 12, 2017, 1:22am UTC](https://meta.discourse.org/t/update-failed-due-to-primary-key-sequence-error/67852/8 "2017-08-12T01:22:23Z")