Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Upgrade from vRA 7.3 to 7.5 fails during script execution, /etc/bootstrap/postupdate.d/09-90-prepare-psql: Failed with exit code 256 (67055)

Last Updated: 3/4/2020Categories: TroubleshootingTotal Views: 4004Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Similar entries below found in /opt/vmware/var/log/vami/updatecli.log:

res=1
echo 'Script /etc/bootstrap/postupdate.d/09-90-prepare-psql failed, error status 1'
exit 1
rm -f /tmp/postupdate-err-log
exit 1
trapfunc
excode=1
test 1 -gt 0
vami_update_msg set post-install 'Post-install: failed'
test -x /usr/sbin/vami-update-msg
/usr/sbin/vami-update-msg set post-install 'Post-install: failed'
sleep 1
test 1 -gt 0 -o 0 -gt 0
vami_update_msg set update-status 'Update failed (code 0-1). Check logs in /opt/vmware/var/log/vami or retry update later.'
test -x /usr/sbin/vami-update-msg
/usr/sbin/vami-update-msg set update-status 'Update failed (code 0-1). Check logs in /opt/vmware/var/log/vami or retry update later.'
exit
03/02/2019 00:48:28 [ERROR] Failed with exit code 256

Similar entries below found in /var/log/bootstrap/postupdate.log

2019-02-03 00:48:26 PSQL perform base backup for this replica
Located file '/etc/vr/psql/db.env' to preset current environment settings for the database.
[2019-02-03 00:48:26] [root] [INFO] Default settings are overridden!
[2019-02-03 00:48:26] [root] [INFO] <psql-set-replica> Replication user is: <vcac_replication>
[2019-02-03 00:48:26] [root] [INFO] <psql-set-replica> Alter current Postgres user role for replication
[2019-02-03 00:48:26] [root] [INFO] <psql-set-replica>: locking psql-set-replica command
[psql]: Service vpostgres stopping...
Stopping VMware vPostgres: pg_ctl: directory "/var/vmware/vpostgres/current/pgdata" is not a database cluster directory
Last login: Sun Feb 3 00:48:08 UTC 2019
pg_ctl: directory "/var/vmware/vpostgres/current/pgdata" is not a database cluster directory
Last login: Sun Feb 3 00:48:26 UTC 2019
[psql]: Service vpostgres stopping DONE!
cp: cannot stat `/var/vmware/vpostgres/current/pgdata/postmaster.opts': No such file or directory
cp: cannot stat `/var/vmware/vpostgres/current/pgdata/pg_log': No such file or directory
[2019-02-03 00:48:26] [root] [INFO] [psql-util]: Reading confirmation, confirm mode is set to:
pg_basebackup: initiating base backup, waiting for checkpoint to complete
pg_basebackup: checkpoint completed
transaction log start point: 460/99000028 on timeline 1
pg_basebackup: starting background WAL receiver
pg_basebackup: could not get transaction log end position from server: ERROR: could not open file "./postgresql.conf_backup.Nov-28-2018": Permission denied
Last login: Sun Feb 3 00:48:26 UTC 2019
Script /etc/bootstrap/postupdate.d/09-90-prepare-psql failed, error status 1
pg_basebackup: replication stream was terminated before stop point

Cause

The failure is generated due to a lack of permissions on postgresql.conf_backup.<date> file.

This was a manual backup created file by the user while logged in as root. Found that it had root permissions:

-rw------- 1 root root 21700 Nov 28 09:20 postgresql.conf_backup.<date>

Whereas the postgresql.conf file has owner permissions as 'postgres users'

Impact / Risks

Manually created back up copies of postgres files can interrupt the pg_basebackup script process due to incorrect permissions.

Resolution

To resolve the problem, follow the steps below:

Roll back all nodes to a stage prior to the upgrade attempt

Reset the permission to 'postgres users'

chown postgres:users postgresql.conf_backup.<date>

Results:

-rw------- 1 postgres users 21700 Nov 28 09:20 postgresql.conf_backup.<date>

Attempt the upgrade again

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
在 VMware vRealize Operations Manager 6.1.x EndPoint 中更改 epops-agent 的服务帐户 (2142246)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.x

Take Our Survey

Support Assistant