VMware Cloud Community
GoLLoMboje
Contributor
Contributor

connecting to an embedded vpostgres db in a windows 2012 r2 installation of vcenter fails

Guys,

I can not connect to vcenter via neither web nor vsphere client. Connection test in ODBC Data Sources --> System DSN fails with error the target machine actively refused it [127.0.0.1:5432]. Tried from cmd using the command c:\Program Files\VMware\vCenter Server\vPostgres\bin>psql -U username database_name  and I got an error psql: could not connect to server: Connection refused (0x0000274D/10061). vpxd log shows a connection error.

Furthermore vmware Inventory service can not  start on local computer. Also Vsphere web client and VMware VirtualCenter services can not start on local computer giving error 1068: The dependence service or group failed to start. Inventory service is one of dependence of the virtualcenter. However VMWare Postgres starts and running with no error.    

Please help.

12 Replies
msripada
Virtuoso
Virtuoso

What is the user account you have tried to login to postgres?

Can you upload the postgres logs in programdata\vmware\vcenterserver\logs\vpostgres

Thanks,

MS

GoLLoMboje
Contributor
Contributor

username is vc as per the vcdb properties shown below. The last log in vpostgres was Dec 13 as shown in the attachment, thereafter I couldn't access the vcenter.

driver = org.postgresql.Driver

dbtype = PostgreSQL

url = jdbc:postgresql://localhost:5432/VCDB

username = vc

password = zTBhjZ5eUA+)}tGx

password.encrypted = false

Reply
0 Kudos
msripada
Virtuoso
Virtuoso

Sent PM to try one command. I could not see the attachment on the thread. Can you PM me with the attachment or try to add it again.

Thanks,

MS

Reply
0 Kudos
GoLLoMboje
Contributor
Contributor

Wed 12/13/2017  7:35:36.15 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:36:09.94 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:36:43.37 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:37:16.32 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:37:49.97 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:38:22.53 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:38:56.55 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:39:29.74 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:40:02.65 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:41:06.70 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:41:40.44 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:42:13.85 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:42:46.62 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:43:20.48 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:43:53.14 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:44:26.71 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:44:59.75 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:45:32.90 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:46:06.43 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:46:39.29 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:47:12.52 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:47:46.50 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:48:19.51 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:48:52.66 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:49:25.98 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:49:59.17 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:50:31.67 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:51:05.44 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:52:09.10 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:52:42.66 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:53:15.35 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:53:48.86 sc query "vpostgres" RUNNING

Wed 12/13/2017  7:54:21.96 sc query "vpostgres" RUNNING

Reply
0 Kudos
GoLLoMboje
Contributor
Contributor

Here is another log. I think this is it.

Reply
0 Kudos
GoLLoMboje
Contributor
Contributor

2017-12-13 08:40:00.881 EAT 5a26ac60.20f0 0   LOG:  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No space left on device

2017-12-13 08:40:00.916 EAT 5a26ac60.20f0 0   LOG:  could not rename temporary statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": No space left on device

2017-12-13 08:40:01.577 EAT 5a26ac60.20f0 0   LOG:  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No space left on device

2017-12-13 08:40:01.593 EAT 5a26ac60.20f0 0   LOG:  could not rename temporary statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": No space left on device

2017-12-13 08:40:02.243 EAT 5a26ac60.20f0 0   LOG:  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No space left on device

2017-12-13 08:40:02.259 EAT 5a26ac60.20f0 0   LOG:  could not rename temporary statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": No space left on device

2017-12-13 08:40:02.907 EAT 5a26ac60.20f0 0   LOG:  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No space left on device

2017-12-13 08:40:02.923 EAT 5a26ac60.20f0 0   LOG:  could not rename temporary statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": No space left on device

2017-12-13 08:40:03.578 EAT 5a26ac60.20f0 0   LOG:  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No space left on device

2017-12-13 08:40:03.593 EAT 5a26ac60.20f0 0   LOG:  could not rename temporary statistics file "pg_stat_tmp/global.tmp" to "pg_stat_tmp/global.stat": No space left on device

2017-12-13 08:40:04.245 EAT 5a26ac60.20f0 0   LOG:  could not close temporary statistics file "pg_stat_tmp/db_0.tmp": No space left on device

2017-12-13 08:44:13.035 EAT 5a30be2d.3d6c 0   FATAL:  could not write init file

2017-12-13 09:02:55.921 EAT 5a30c28f.21b0 0   LOG:  database system was interrupted; last known up at 2017-12-13 01:46:31 EAT

2017-12-13 09:03:16.896 EAT 5a30c28f.21b0 0   LOG:  database system was not properly shut down; automatic recovery in progress

2017-12-13 09:03:16.975 EAT 5a30c28f.21b0 0   LOG:  redo starts at 1E/F7963308

2017-12-13 09:03:18.660 EAT 5a30c28f.21b0 0   LOG:  record with zero length at 1E/F847D528

2017-12-13 09:03:18.660 EAT 5a30c28f.21b0 0   LOG:  redo done at 1E/F847D4F8

2017-12-13 09:03:18.673 EAT 5a30c28f.21b0 0   LOG:  last completed transaction was at log time 2017-12-13 08:05:52.717+03

2017-12-13 09:03:18.691 EAT 5a30c28f.21b0 0   FATAL:  btree level 1 not found in index "1284524"

2017-12-13 09:03:18.877 EAT 5a30c289.2118 0   LOG:  startup process (PID 8624) exited with exit code 1

2017-12-13 09:03:18.877 EAT 5a30c289.2118 0   LOG:  aborting startup due to startup process failure

Reply
0 Kudos
msripada
Virtuoso
Virtuoso

Can you check for the file starting with name postgresql-XX.log and check for the latest timestamp and share the output of that file.

Thanks,

MS

Reply
0 Kudos
msripada
Virtuoso
Virtuoso

It looks like there is not space on the vcenter database

What is the vCenter?? Is it windows? Do we have space on the vCenter?

Thanks,

MS

Reply
0 Kudos
GoLLoMboje
Contributor
Contributor

vcenter run on Windows 2012 r2 with 62Gb free in Drive C. Earlier it was 1.6Gb free. 

Reply
0 Kudos
msripada
Virtuoso
Virtuoso

Did you restart the services again on the vCenter server

Thanks,

MS

Reply
0 Kudos
GoLLoMboje
Contributor
Contributor

Yes, I even restarted the whole server but still negative.

Reply
0 Kudos
EngGoLLo
Contributor
Contributor

Guys,

I tried to create a backup vcdb backup and turns out the backup file was zero KB. Which means the vpostgres db was corrupted. Therefore I decided to redeploy the vcenter. it's up and running again.