Concourse Installed by helm chart

Concourse is installed with ldap auth by helm chart.
I’m looking why I able to create a pipeline by fly command, I see it on the web ui. I can trigger job but I cannot see the result of the job:

401 Unauthorized
You are not authorized to view
the details of this pipeline

So on I look inside the log file to find any trouble and the only thing I’ve found is inside the pg log.
Is it normal that on log of the postgresql pod for concourse I have this kind of error:

     /tmp:5432 - accepting connections
     17:08:01.97 INFO  ==> Creating user concourse
     17:08:02.07 INFO  ==> Grating access to "concourse" to the database "concourse"
     17:08:02.32 INFO  ==> Configuring replication parameters
     17:08:02.52 INFO  ==> Configuring fsync
     17:08:03.28 INFO  ==> Loading custom scripts...
     17:08:03.29 INFO  ==> Enabling remote connections
     17:08:03.38 INFO  ==> Stopping PostgreSQL...
     17:08:07.40 INFO  ==> ** PostgreSQL setup finished! **
     17:08:07.48 INFO  ==> ** Starting PostgreSQL **
    2019-10-25 17:08:08.078 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
    2019-10-25 17:08:08.081 GMT [1] LOG:  could not create IPv6 socket for address "::": Address family not supported by protocol
    2019-10-25 17:08:09.700 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
    2019-10-25 17:08:10.512 GMT [244] LOG:  database system was shut down at 2019-10-25 17:08:04 GMT
    2019-10-25 17:08:10.618 GMT [1] LOG:  database system is ready to accept connections
    2019-10-25 17:08:14.706 GMT [261] ERROR:  relation "schema_migrations" does not exist at character 15
    2019-10-25 17:08:14.706 GMT [261] STATEMENT:  SELECT * from schema_migrations
    2019-10-25 17:08:14.710 GMT [261] ERROR:  relation "migrations_history" does not exist at character 15
    2019-10-25 17:08:14.710 GMT [261] STATEMENT:  SELECT * from migrations_history
    2019-10-25 17:08:47.976 GMT [261] LOG:  unexpected EOF on client connection with an open transaction
    2019-10-25 17:08:48.282 GMT [312] ERROR:  relation "schema_migrations" does not exist at character 15
    2019-10-25 17:08:48.282 GMT [312] STATEMENT:  SELECT * from schema_migrations
    2019-10-25 17:09:47.352 GMT [416] ERROR:  relation "schema_migrations" does not exist at character 15
    2019-10-25 17:09:47.352 GMT [416] STATEMENT:  SELECT * from schema_migrations
    2019-10-25 20:29:26.788 GMT [18997] ERROR:  update or delete on table "volumes" violates foreign key constraint "volumes_parent_id_fkey" on table "volumes"
    2019-10-25 20:29:26.788 GMT [18997] DETAIL:  Key (id, state)=(47, created) is still referenced from table "volumes".
    2019-10-25 20:29:26.788 GMT [18997] STATEMENT:  UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
    2019-10-25 20:29:56.779 GMT [19051] ERROR:  update or delete on table "volumes" violates foreign key constraint "volumes_parent_id_fkey" on table "volumes"
    2019-10-25 20:29:56.779 GMT [19051] DETAIL:  Key (id, state)=(47, created) is still referenced from table "volumes".
    2019-10-25 20:29:56.779 GMT [19051] STATEMENT:  UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
    2019-10-25 20:30:26.779 GMT [19051] ERROR:  update or delete on table "volumes" violates foreign key constraint "volumes_parent_id_fkey" on table "volumes"
    2019-10-25 20:30:26.779 GMT [19051] DETAIL:  Key (id, state)=(47, created) is still referenced from table "volumes".
    2019-10-25 20:30:26.779 GMT [19051] STATEMENT:  UPDATE volumes SET state = $1 WHERE (id = $2 AND (state = $3 OR state = $4))
    2019-10-25 20:30:56.776 GMT [19051] ERROR:  update or delete on table "volumes" violates foreign key constraint "volumes_parent_id_fkey" on table "volumes" 

It seems that the worker’s volume and DB state are inconsistent. So, recreating workers may solve this error.

delete the worker pod one by one and k8s will take care of recreating the same.

Sorry for the delay on my answer (I was in holydays) @gowrisankar22 recreate worker doesn’t solve the pb
I also try to install concourse with a separate postgresql database
the 401 Unauthorized is still present
On worker log I’ve got {“timestamp”:“2019-11-03T21:11:32.984120828Z”,“level”:“error”,“source”:“worker”,“message”:“worker.beacon-runner.beacon.forward-conn.failed-to-dial”,“data”:{“addr”:“127.0.0.1:7777”,“error”:“dial tcp 127.0.0.1:7777: connect: connection refused”,“network”:“tcp”,“session”:“4.1.4”}}
{“timestamp”:“2019-11-03T21:11:33.984274010Z”,“level”:“info”,“source”:“worker”,“message”:“worker.beacon-runner.beacon.forward-conn.retrying”,“data”:{“addr”:“127.0.0.1:7777”,“network”:“tcp”,“session”:“4.1.4”}}
{“timestamp”:“2019-11-03T21:11:33.984485347Z”,“level”:“error”,“source”:“worker”,“message”:“worker.beacon-runner.beacon.forward-conn.failed-to-dial”,“data”:{“addr”:“127.0.0.1:7777”,“error”:“dial tcp 127.0.0.1:7777: connect: connection refused”,“network”:“tcp”,“session”:“4.1.4”}}

I see that there is one http request that takes a long time and failed:https://concourse.k8s-micro.nd-int-ops-paas/api/v1/builds/1/events
previous request succeed https://concourse.k8s-micro.nd-int-ops-paas/api/v1/builds/1/plan

I think that the trouble is due to my ingress controller Traefik as if I put the service in NodePort I can access to the /api/v1/builds/1/events
It’s a stream
may traefik doesn’t accept it

traefik doesn’t support text/event-stream with gzip compression enabled they are about to fix it in next version
a workaround is to disable the gzip compression
in next traefik version the gzip compression can be desactivated for specific content-type such as text/event-stream