VMware Cloud Community
RomanEliseev
Contributor
Contributor
Jump to solution

vCenter 6.0 windows to vCenter 6.5 windows upgrade fails with error (UPGRADE_EXPORT_TIMEOUT)

Hello!

I try to upgrade my vCenter 6.0 on Windows 2008R2 to 6.5 version.

Upgrade fails with error:

Can anybody help me?

System extension in Windows don't help.

UPGRADE_EXPORT_TIMEOUT=600

UPGRADE_IMPORT_TIMEOUT=600

1 Solution

Accepted Solutions
Vijay2027
Expert
Expert
Jump to solution

Ideally pgpass.conf file should have 4 lines. The file you uploaded has 2 lines.

This is from my lab environment:

localhost:5432:postgres:postgres:a9A5Qk>r%($JGZ#l

127.0.0.1:5432:postgres:postgres:a9A5Qk>r%($JGZ#l

localhost:5432:VCDB:postgres:a9A5Qk>r%($JGZ#l

127.0.0.1:5432:VCDB:postgres:a9A5Qk>r%($JGZ#l

Modify pgpass.conf file in your environment and retry upgrade.

View solution in original post

Reply
0 Kudos
23 Replies
Vijay2027
Expert
Expert
Jump to solution

Dd you verify the logs?? Possibly an issue with ODBC connection or corrupt pg conf file (if EMB postgres is used)

And any reason why you are sticking with vCenter windows??

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

My vCenter DB on postgres. vCenter is good. Working fine.

I tryed to migrate to VCSA 6.5 and  got same error.

I verify the log file UpgradeRunner.log and find "vcdb:collectRequirements: didn't have progress" and after 15 min upgrade or migration process stoped with error.

ODBC test:

pastedImage_0.png

PS: Sorry for my bad english.

Reply
0 Kudos
nirmalgnair
VMware Employee
VMware Employee
Jump to solution

Hi Roman,

I would suggest you to try setting the below environment variables in windows with value as 90 (for 90 minutes timeout)

Open CMD as Administrator and run the following command

set UPGRADE_EXPORT_TIMEOUT=90

set UPGRADE_IMPORT_TIMEOUT=90

If these values are not defined, it will use default timeout as 15 minutes. Also when you migrate just select the Configuration to be migrated and not the complete tasks & events.

Regards,

Nirmal Nair

vSphere Install-Upgrade Support

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

Thx.

I am already set it and it is not help for upgrade. Smiley Sad

pastedImage_0.png

I get error during "Running pre-upgrade checks"

pastedImage_2.png

Reply
0 Kudos
daphnissov
Immortal
Immortal
Jump to solution

My advice here would be to forget about the notion of upgrading a Windows-based vCenter, because this platform is dead. There is no more Windows vCenter after the 6.7 release. The better thing would be to upgrade your 6.0 vCenter to the vCSA on 6.5. You can eliminate this error entirely by doing so.

Reply
0 Kudos
nirmalgnair
VMware Employee
VMware Employee
Jump to solution

Hi Roman,

Have you rebooted the Windows machine after setting the environmental variable?

I would suggest you to try the migration again by selecting only Configuration.

Regards,

Nirmal Nair

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

Yes, i rebooted my server.

I use VMware-Migration-assistant.exe v6.5 for migration. How to run  migration to VCSA whith selecting only Configuration?

I use this manual (GUI Migration of vCenter Server with an Embedded vCenter Single Sign-On or Platform Services Controller to an Appliance)

Reply
0 Kudos
nirmalgnair
VMware Employee
VMware Employee
Jump to solution

Hi Roman,

After the Stage 1 is completed, you will get the option to select the migration data.

Regards,

Nirmal Nair

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

Ok. I agree whith You! Thx.

I try to migrate to the vCSA 6.5. I hope, that system environment variables in windows as 1000 min help me. 🙂

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

pastedImage_0.png

Reply
0 Kudos
nirmalgnair
VMware Employee
VMware Employee
Jump to solution

Hi Roman,

Is it possible for you to share the ZIP bundle generated.

Regards,

Nirmal Nair

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

I google info about this error and found that i must start migration assistant on the VM with VMware Update Manager.

I done it:

pastedImage_0.png

Than i try to start migration on the VM with vCenter and get this error again.

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

Nirmalgnair!

I am sorry but i dont understand what i must to do. 😞

Reply
0 Kudos
nirmalgnair
VMware Employee
VMware Employee
Jump to solution

Hi Roman,

Apologize for the delayed reply.

I would suggest you to try cleaning up the vCenter DB to reduce the size.

You can follow : VMware Knowledge Base

Also request you to go through below artciles.

VMware Knowledge Base

vCenter server 6.0 service crashes due to postgres database filling up OS Partition. - vSphere Arena

Regards,

Nirmal Nair

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

Hello!

Tables size after cleaning.

pastedImage_0.png

Unfortunately i have this error againe. Smiley Sad

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

Log file attached

Reply
0 Kudos
Vijay2027
Expert
Expert
Jump to solution

I looked at the logs:

2019-12-16T08:31:50.197Z INFO upgrade.states.component_states vcdb:CollectRequirements: didn't have progress. Next report will come after 60 seconds

2019-12-16T08:32:50.766Z INFO upgrade.states.component_states vcdb:CollectRequirements: didn't have progress. Next report will come after 60 seconds

2019-12-16T08:33:50.924Z INFO upgrade.states.component_states vcdb:CollectRequirements: didn't have progress. Next report will come after 60 seconds

2019-12-16T08:34:51.878Z INFO upgrade.states.component_states vcdb:CollectRequirements: didn't have progress. Next report will come after 60 seconds

2019-12-16T08:35:52.848Z INFO upgrade.states.component_states vcdb:CollectRequirements: didn't have progress. Next report will come after 60 seconds

2019-12-16T08:36:53.848Z INFO upgrade.states.component_states vcdb:CollectRequirements: didn't have progress. Next report will come after 60 seconds

2019-12-16T08:37:54.809Z INFO upgrade.states.component_states vcdb:CollectRequirements: didn't have progress. Next report will come after 60 seconds

2019-12-16T08:38:46.273Z WARNING wf.wf_processor Operation State CollectRequirements com.vmware.vcdb did not report progress for 901 seconds

2019-12-16T08:38:46.273Z INFO wf.wf_processor Shutting down all running states

2019-12-16T08:38:46.273Z INFO wf.wf Shutting down State CollectRequirements com.vmware.vcdb

2019-12-16T08:38:46.275Z INFO wf.wf Shutting down State CollectRequirements com.vmware.vcdb

2019-12-16T08:38:46.275Z INFO wf.wf State CollectRequirements com.vmware.vcdb is shut down

2019-12-16T08:38:46.276Z INFO wf.wf State CollectRequirements com.vmware.vcdb is shut down

As mentioned in my previous post could you take a look at pgpass.conf file or attach to the thread:

C:\Windows\System32\config\systemprofile\AppData\Roaming\postgresql\pgpass.conf

And were you able to login to VCDB using postgres user account:

C:\Program Files\VMware\vCenter Server\vPostgres\bin\psql -d VCDB -U postgres

Reply
0 Kudos
RomanEliseev
Contributor
Contributor
Jump to solution

Hello!

Login is succesed with password from C:\Windows\System32\config\systemprofile\AppData\Roaming\postgresql\pgpass.conf.

pastedImage_0.png

And i found this post How to upgrade VCSA 6.0 update 3 to VCSA 6.5 - tomaskalabis.com

But this decision does not help too. Smiley Sad

Reply
0 Kudos
Vijay2027
Expert
Expert
Jump to solution

Can you attach pgpass.conf file to the thread pls

Reply
0 Kudos