Re: DCAE and DMaaP Bus Controller db pods (dcae-db-0 dbc-pg-0 ) are not running #dcaegen2 #dmaap


Dominic Lunanuova
 

This symptom is reminiscent of some errors we saw when OOM-1178 was first delivered.

i.e. we experienced some name conflicts between different components using common postgres chart

But that was in early Casablanca, not Beijing.

Do you also see dbpool pods?  (those were introduced in the mentioned Jira, and would clarify what versions are really being run)

 

Otherwise, I don’t recall this ever being reported in Beijing.

 

-Dom

 

From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of gulsumatici@...
Sent: Friday, December 7, 2018 3:44 AM
To: onap-discuss@...
Subject: [onap-discuss] DCAE and DMaaP Bus Controller db pods (dcae-db-0 dbc-pg-0 ) are not running #dmaap #dcaegen2

 

Hello,

I have  installed  Beijing  latest  version. 

dcae-db and  dbc-pg  containers are  not running   and  both of them  are using  the  following  images. Does  anybody  meet  such  kind of  problem ?

Thanks,

crunchydata/crunchy-postgres:centos7-10.3-1.8.2

crunchydata/crunchy-postgres:centos7-10.3-1.8.2

dbc-pg  postgresql logs:

2018-12-06 14:37:18.442 UTC [86] LOG:  shutting down

2018-12-06 14:37:20.404 UTC [82] LOG:  database system is shut down

2018-12-06 14:45:11.155 UTC [88] LOG:  database system was shut down at 2018-12-06 14:37:19 UTC

2018-12-06 14:45:11.230 UTC [85] LOG:  database system is ready to accept connections

2018-12-06 14:55:05.079 UTC [85] LOG:  received fast shutdown request

2018-12-06 14:55:09.110 UTC [85] LOG:  aborting any active transactions

2018-12-06 14:55:09.204 UTC [85] LOG:  worker process: logical replication launcher (PID 94) exited with exit code 1

2018-12-06 14:55:09.230 UTC [89] LOG:  shutting down

2018-12-06 14:55:20.266 UTC [85] LOG:  database system is shut down

2018-12-06 14:55:45.793 UTC [85] LOG:  database system was shut down at 2018-12-06 14:55:20 UTC

2018-12-06 14:55:45.923 UTC [82] LOG:  database system is ready to accept connections

2018-12-06 15:07:10.298 UTC [82] LOG:  received fast shutdown request

2018-12-06 15:07:10.360 UTC [82] LOG:  aborting any active transactions

2018-12-06 15:07:10.411 UTC [82] LOG:  worker process: logical replication launcher (PID 91) exited with exit code 1

2018-12-06 15:07:10.414 UTC [86] LOG:  shutting down

2018-12-06 15:07:10.926 UTC [82] LOG:  database system is shut down

2018-12-06 15:07:21.740 UTC [82] LOG:  database system was shut down at 2018-12-06 15:07:10 UTC

2018-12-06 15:07:21.786 UTC [79] LOG:  database system is ready to accept connections

2018-12-06 15:19:15.966 UTC [79] LOG:  received fast shutdown request

2018-12-06 15:19:16.023 UTC [79] LOG:  aborting any active transactions

2018-12-06 15:19:16.086 UTC [79] LOG:  worker process: logical replication launcher (PID 88) exited with exit code 1

2018-12-06 15:19:16.117 UTC [83] LOG:  shutting down

2018-12-06 15:19:16.483 UTC [79] LOG:  database system is shut down

2018-12-06 15:19:32.765 UTC [87] LOG:  database system was shut down at 2018-12-06 15:19:16 UTC

2018-12-06 15:19:32.833 UTC [84] LOG:  database system is ready to accept connections

2018-12-06 15:31:20.165 UTC [84] LOG:  received fast shutdown request

2018-12-06 15:31:20.187 UTC [84] LOG:  aborting any active transactions

2018-12-06 15:31:20.213 UTC [84] LOG:  worker process: logical replication launcher (PID 93) exited with exit code 1

2018-12-06 15:31:20.224 UTC [88] LOG:  shutting down

more_vert

more_vert


dbc-pg  container  is not  running  with the  follwing error:

  • Standard Error

07.12.2018 11:25:06chown: cannot access '/pgwal/dev2-dbc-pg-0-wal': No such file or directory

07.12.2018 11:25:06rm: cannot remove '/pgdata/dev2-dbc-pg-0/postmaster.pid': No such file or directory

07.12.2018 11:25:132018-12-07 08:25:13.229 UTC [83] LOG: listening on IPv6 address "::1", port 5432

07.12.2018 11:25:132018-12-07 08:25:13.229 UTC [83] LOG: listening on IPv4 address "127.0.0.1", port 5432

07.12.2018 11:25:132018-12-07 08:25:13.349 UTC [83] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

07.12.2018 11:25:132018-12-07 08:25:13.424 UTC [83] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"

07.12.2018 11:25:132018-12-07 08:25:13.588 UTC [83] LOG: redirecting log output to logging collector process

07.12.2018 11:25:132018-12-07 08:25:13.588 UTC [83] HINT: Future log output will appear in directory "log".


dcae-db container  is  not  running  with the  following  error:

07.12.2018 11:20:44chown: cannot access '/pgwal/dev2-dcae-db-0-wal': No such file or directory

07.12.2018 11:20:44rm: cannot remove '/pgdata/dev2-dcae-db-0/postmaster.pid': No such file or directory

07.12.2018 11:20:582018-12-07 08:20:58.711 UTC [82] LOG: listening on IPv6 address "::1", port 5432

07.12.2018 11:20:582018-12-07 08:20:58.719 UTC [82] LOG: listening on IPv4 address "127.0.0.1", port 5432

07.12.2018 11:20:582018-12-07 08:20:58.912 UTC [82] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

07.12.2018 11:20:592018-12-07 08:20:59.048 UTC [82] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"

07.12.2018 11:21:002018-12-07 08:21:00.256 UTC [82] LOG: redirecting log output to logging collector process

07.12.2018 11:21:002018-12-07 08:21:00.256 UTC [82] HINT: Future log output will appear in directory "log".

07.12.2018 11:30:46chown: cannot access '/pgwal/dev2-dcae-db-0-wal': No such file or directory

07.12.2018 11:30:502018-12-07 08:30:50.978 UTC [87] LOG: could not bind IPv6 address "::1": Address already in use

07.12.2018 11:30:502018-12-07 08:30:50.978 UTC [87] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.

07.12.2018 11:30:502018-12-07 08:30:50.978 UTC [87] LOG: could not bind IPv4 address "127.0.0.1": Address already in use

07.12.2018 11:30:502018-12-07 08:30:50.978 UTC [87] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.

07.12.2018 11:30:502018-12-07 08:30:50.978 UTC [87] WARNING: could not create listen socket for "localhost"

07.12.2018 11:30:502018-12-07 08:30:50.978 UTC [87] FATAL: could not create any TCP/IP sockets

07.12.2018 11:30:512018-12-07 08:30:51.002 UTC [87] LOG: database system is shut down

Join onap-discuss@lists.onap.org to automatically receive all group messages.