We had troubles with our install (web instance got gradually slower). Due to lots of errors in the db-log we wiped the installation and setup a new fresh one. However, even before login into our new Concourse instance, we observed lots of errors in the log.
concourse-up version 0.8.4.
Is this related to concourse, or the product itself?
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “users” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE TABLE USERS ( id char(36) not null primary key, created TIMESTAMP default current_timestamp, lastModified TIMESTAMP default current_timestamp, version BIGINT default 0, username VARCHAR(255) not null, password VARCHAR(255) not null, email VARCHAR(255) not null, authority BIGINT default 0, givenName VARCHAR(255) not null, familyName VARCHAR(255) not null )
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “unique_uk_1_1" already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE UNIQUE INDEX unique_uk_1_1 on users (LOWER(username))
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: column “active” of relation “users” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: ALTER TABLE USERS ADD COLUMN active BOOLEAN default true
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: column “phonenumber” of relation “users” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: ALTER TABLE USERS ADD COLUMN phoneNumber VARCHAR(255)
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: column “authorities” of relation “users” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: ALTER TABLE USERS ADD COLUMN authorities VARCHAR(1024) default ‘uaa.user’
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: column “verified” of relation “users” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: ALTER TABLE USERS ADD COLUMN VERIFIED BOOLEAN
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “sec_audit” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE TABLE SEC_AUDIT ( principal_id char(36) not null, event_type INTEGER not null, origin VARCHAR(255) not null, event_data VARCHAR(255), created TIMESTAMP default current_timestamp )
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “audit_principal” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE INDEX audit_principal ON SEC_AUDIT (principal_id)
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “audit_created” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE INDEX audit_created ON SEC_AUDIT (created)
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “oauth_client_details” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE TABLE OAUTH_CLIENT_DETAILS ( client_id VARCHAR(256) PRIMARY KEY, resource_ids VARCHAR(1024), client_secret VARCHAR(256), scope VARCHAR(256), authorized_grant_types VARCHAR(256), web_server_redirect_uri VARCHAR(1024), authorities VARCHAR(256), access_token_validity INTEGER )
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: column “refresh_token_validity” of relation “oauth_client_details” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: ALTER TABLE OAUTH_CLIENT_DETAILS ADD COLUMN refresh_token_validity INTEGER default 0
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: column “additional_information” of relation “oauth_client_details” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: ALTER TABLE OAUTH_CLIENT_DETAILS ADD COLUMN additional_information VARCHAR(4096)
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “groups” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE TABLE GROUPS ( id VARCHAR(36) not null primary key, displayName VARCHAR(255) not null, created TIMESTAMP default current_timestamp not null, lastModified TIMESTAMP default current_timestamp not null, version BIGINT default 0 not null, constraint unique_uk_2 unique(displayName) )
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “group_membership” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE TABLE GROUP_MEMBERSHIP ( group_id VARCHAR(36) not null, member_id VARCHAR(36) not null, member_type VARCHAR(8) not null default ‘USER’, authorities VARCHAR(255) not null default ‘READ’, added TIMESTAMP default current_timestamp not null, primary key (group_id, member_id) )
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “oauth_code” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: create table oauth_code ( code VARCHAR(256), authentication BYTEA )
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “authz_approvals” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE TABLE AUTHZ_APPROVALS ( userName VARCHAR(36) not null, clientId VARCHAR(36) not null, scope VARCHAR(255) not null, expiresAt TIMESTAMP default current_timestamp not null, status VARCHAR(50) default ‘APPROVED’ not null, lastModifiedAt TIMESTAMP default current_timestamp not null, primary key (userName, clientId, scope) )
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:ERROR: relation “external_group_mapping” already exists
2018-03-27 11:00:05 UTC:10.0.0.7(40282):adminhr7wdjl3mhlw43o7jwlw@uaa:[7085]:STATEMENT: CREATE TABLE external_group_mapping ( group_id VARCHAR(36) not null, external_group VARCHAR(255) not null, added TIMESTAMP default current_timestamp not null, primary key (group_id, external_group) )
2018-03-27 11:01:01 UTC:10.0.0.7(40546):adminhr7wdjl3mhlw43o7jwlw@credhub:[7344]:WARNING: there is already a transaction in progress
2018-03-27 11:01:10 UTC::@:[3739]:LOG: checkpoint starting: time
2018-03-27 11:01:35 UTC:10.0.0.7(41666):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[7411]:ERROR: relation “migration_version” does not exist at character 21
2018-03-27 11:01:35 UTC:10.0.0.7(41666):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[7411]:STATEMENT: SELECT version FROM migration_version
2018-03-27 11:01:36 UTC:10.0.0.7(41684):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[7415]:ERROR: relation “migration_version” does not exist at character 21
2018-03-27 11:01:36 UTC:10.0.0.7(41684):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[7415]:STATEMENT: SELECT version FROM migration_version
2018-03-27 11:02:03 UTC::@:[3739]:LOG: checkpoint complete: wrote 531 buffers (0.2%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=53.441 s, sync=0.004 s, total=53.452 s; sync files=305, longest=0.003 s, average=0.000 s; distance=18165 kB, estimate=18165 kB
2018-03-27 11:06:10 UTC::@:[3739]:LOG: checkpoint starting: time
2018-03-27 11:07:09 UTC::@:[3739]:LOG: checkpoint complete: wrote 586 buffers (0.2%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=58.977 s, sync=0.002 s, total=58.986 s; sync files=249, longest=0.002 s, average=0.000 s; distance=13641 kB, estimate=17713 kB
2018-03-27 11:11:10 UTC::@:[3739]:LOG: checkpoint starting: time
2018-03-27 11:11:19 UTC::@:[3739]:LOG: checkpoint complete: wrote 92 buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=9.261 s, sync=0.004 s, total=9.271 s; sync files=71, longest=0.004 s, average=0.000 s; distance=16420 kB, estimate=17584 kB
2018-03-27 11:16:10 UTC::@:[3739]:LOG: checkpoint starting: time
2018-03-27 11:16:20 UTC::@:[3739]:LOG: checkpoint complete: wrote 100 buffers (0.0%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=10.067 s, sync=0.003 s, total=10.076 s; sync files=70, longest=0.003 s, average=0.000 s; distance=16340 kB, estimate=17459 kB
2018-03-27 11:21:10 UTC::@:[3739]:LOG: checkpoint starting: time
2018-03-27 11:21:23 UTC::@:[3739]:LOG: checkpoint complete: wrote 130 buffers (0.1%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=13.086 s, sync=0.003 s, total=13.094 s; sync files=87, longest=0.003 s, average=0.000 s; distance=16667 kB, estimate=17380 kB
2018-03-27 11:23:26 UTC:10.0.0.6(45890):adminhr7wdjl3mhlw43o7jwlw@bosh:[11328]:ERROR: database “concourse_atc” already exists
2018-03-27 11:23:26 UTC:10.0.0.6(45890):adminhr7wdjl3mhlw43o7jwlw@bosh:[11328]:STATEMENT: CREATE DATABASE concourse_atc
2018-03-27 11:23:26 UTC:10.0.0.6(45890):adminhr7wdjl3mhlw43o7jwlw@bosh:[11328]:ERROR: database “uaa” already exists
2018-03-27 11:23:26 UTC:10.0.0.6(45890):adminhr7wdjl3mhlw43o7jwlw@bosh:[11328]:STATEMENT: CREATE DATABASE uaa
2018-03-27 11:23:26 UTC:10.0.0.6(45890):adminhr7wdjl3mhlw43o7jwlw@bosh:[11328]:ERROR: database “credhub” already exists
2018-03-27 11:23:26 UTC:10.0.0.6(45890):adminhr7wdjl3mhlw43o7jwlw@bosh:[11328]:STATEMENT: CREATE DATABASE credhub
2018-03-27 11:23:53 UTC:10.0.0.7(40544):adminhr7wdjl3mhlw43o7jwlw@credhub:[7343]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40546):adminhr7wdjl3mhlw43o7jwlw@credhub:[7344]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40540):adminhr7wdjl3mhlw43o7jwlw@credhub:[7341]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40542):adminhr7wdjl3mhlw43o7jwlw@credhub:[7342]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40538):adminhr7wdjl3mhlw43o7jwlw@credhub:[7340]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40536):adminhr7wdjl3mhlw43o7jwlw@credhub:[7339]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40532):adminhr7wdjl3mhlw43o7jwlw@credhub:[7337]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40534):adminhr7wdjl3mhlw43o7jwlw@credhub:[7338]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40530):adminhr7wdjl3mhlw43o7jwlw@credhub:[7336]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:23:53 UTC:10.0.0.7(40528):adminhr7wdjl3mhlw43o7jwlw@credhub:[7335]:LOG: could not receive data from client: Connection reset by peer
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:ERROR: duplicate key value violates unique constraint “oauth_client_details_pkey”
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:DETAIL: Key (client_id, identity_zone_id)=(admin, uaa) already exists.
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:STATEMENT: insert into oauth_client_details (client_secret, resource_ids, scope, authorized_grant_types, web_server_redirect_uri, authorities, access_token_validity, refresh_token_validity, additional_information, autoapprove, lastmodified, required_user_groups, client_id, identity_zone_id, created_by) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15)
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:ERROR: duplicate key value violates unique constraint “oauth_client_details_pkey”
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:DETAIL: Key (client_id, identity_zone_id)=(credhub_cli, uaa) already exists.
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:STATEMENT: insert into oauth_client_details (client_secret, resource_ids, scope, authorized_grant_types, web_server_redirect_uri, authorities, access_token_validity, refresh_token_validity, additional_information, autoapprove, lastmodified, required_user_groups, client_id, identity_zone_id, created_by) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15)
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:ERROR: duplicate key value violates unique constraint “oauth_client_details_pkey”
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:DETAIL: Key (client_id, identity_zone_id)=(atc_to_credhub, uaa) already exists.
2018-03-27 11:24:36 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:STATEMENT: insert into oauth_client_details (client_secret, resource_ids, scope, authorized_grant_types, web_server_redirect_uri, authorities, access_token_validity, refresh_token_validity, additional_information, autoapprove, lastmodified, required_user_groups, client_id, identity_zone_id, created_by) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15)
2018-03-27 11:24:37 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:ERROR: duplicate key value violates unique constraint “external_group_unique_key”
2018-03-27 11:24:37 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:DETAIL: Key (origin, external_group, group_id)=(ldap, cn=test_org,ou=people,o=springsource,o=org, f90855f9-bce6-4827-bc8a-b07dc65895d4) already exists.
2018-03-27 11:24:37 UTC:10.0.0.7(52032):adminhr7wdjl3mhlw43o7jwlw@uaa:[11517]:STATEMENT: insert into external_group_mapping ( group_id,external_group,added,origin,identity_zone_id ) values ($1,lower($2),$3,$4,$5)
2018-03-27 11:26:00 UTC:10.0.0.7(54468):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11821]:ERROR: relation “migration_version” does not exist at character 21
2018-03-27 11:26:00 UTC:10.0.0.7(54468):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11821]:STATEMENT: SELECT version FROM migration_version
2018-03-27 11:26:00 UTC:10.0.0.7(54478):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11825]:ERROR: relation “migration_version” does not exist at character 21
2018-03-27 11:26:00 UTC:10.0.0.7(54478):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11825]:STATEMENT: SELECT version FROM migration_version
2018-03-27 11:26:10 UTC::@:[3739]:LOG: checkpoint starting: time
2018-03-27 11:26:30 UTC:10.0.0.7(54482):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11827]:ERROR: update or delete on table “volumes” violates foreign key constraint “volumes_parent_id_fkey” on table “volumes”
2018-03-27 11:26:30 UTC:10.0.0.7(54482):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11827]:DETAIL: Key (id, state)=(10, created) is still referenced from table “volumes”.
2018-03-27 11:26:30 UTC:10.0.0.7(54482):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11827]:STATEMENT: UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
2018-03-27 11:26:30 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:ERROR: update or delete on table “volumes” violates foreign key constraint “volumes_parent_id_fkey” on table “volumes”
2018-03-27 11:26:30 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:DETAIL: Key (id, state)=(21, created) is still referenced from table “volumes”.
2018-03-27 11:26:30 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:STATEMENT: UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
2018-03-27 11:26:30 UTC:10.0.0.7(54482):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11827]:ERROR: update or delete on table “volumes” violates foreign key constraint “volumes_parent_id_fkey” on table “volumes”
2018-03-27 11:26:30 UTC:10.0.0.7(54482):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11827]:DETAIL: Key (id, state)=(1, created) is still referenced from table “volumes”.
2018-03-27 11:26:30 UTC:10.0.0.7(54482):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11827]:STATEMENT: UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
2018-03-27 11:26:43 UTC::@:[3739]:LOG: checkpoint complete: wrote 328 buffers (0.1%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=33.010 s, sync=0.003 s, total=33.022 s; sync files=220, longest=0.002 s, average=0.000 s; distance=16404 kB, estimate=17282 kB
2018-03-27 11:27:00 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:ERROR: update or delete on table “volumes” violates foreign key constraint “volumes_parent_id_fkey” on table “volumes”
2018-03-27 11:27:00 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:DETAIL: Key (id, state)=(10, created) is still referenced from table “volumes”.
2018-03-27 11:27:00 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:STATEMENT: UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
2018-03-27 11:27:00 UTC:10.0.0.7(57454):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[12003]:ERROR: update or delete on table “volumes” violates foreign key constraint “volumes_parent_id_fkey” on table “volumes”
2018-03-27 11:27:00 UTC:10.0.0.7(57454):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[12003]:DETAIL: Key (id, state)=(21, created) is still referenced from table “volumes”.
2018-03-27 11:27:00 UTC:10.0.0.7(57454):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[12003]:STATEMENT: UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
2018-03-27 11:27:00 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:ERROR: update or delete on table “volumes” violates foreign key constraint “volumes_parent_id_fkey” on table “volumes”
2018-03-27 11:27:00 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:DETAIL: Key (id, state)=(1, created) is still referenced from table “volumes”.
2018-03-27 11:27:00 UTC:10.0.0.7(54484):adminhr7wdjl3mhlw43o7jwlw@concourse_atc:[11828]:STATEMENT: UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
Closing this issue assuming it was a problem in either an old version of concourse-up or an old version of Concourse itself. If you are still experiencing this then feel free to reopen the issue.
We had troubles with our install (web instance got gradually slower). Due to lots of errors in the db-log we wiped the installation and setup a new fresh one. However, even before login into our new Concourse instance, we observed lots of errors in the log.
concourse-up version 0.8.4.
Is this related to concourse, or the product itself?