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

Harbor service fails to start with sudo: unable to change expired password: Authentication token manipulation error (79497)

Last Updated: 6/11/2020Categories: TroubleshootingTotal Views: 6868Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

·         Harbor service is failing to start.

·         When you check the harbor-app logs, you see the entries similar to:
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: unable to change expired password: Authentication token manipulation error
sudo: Account or password is expired, reset your password and try again Changing password for root.

Cause

This issue occurs as the harbor-log container set a 90 days to expire its password, see below github page for more information.
https://github.com/goharbor/harbor/issues/11633

Resolution

This is a known issue with Harbor 1.10.x, it will be fixed in 1.10.3.

Workaround

Note: These steps will not work for an upgraded Harbor installation. Please contact VMware Technical Support for guidance.

To work around this issue:

1.       Connect Harbor vm from bosh by running the below command:
bosh ssh -d <Harbor-service_instance-name>

2.       Switch to sudo mode by running: sudo -i

3.       Export the docker alias:
alias docker='/var/vcap/packages/docker/bin/docker -H unix:///var/vcap/sys/run/docker/dockerd.sock'

4.       Stop all running containers and delete them by running:
docker stop $(docker ps -aq) && docker rm $(docker ps -a)

5.       Pull the new harbor-log image:
docker pull goharbor/harbor-log:v1.10.3-dev
Note: If you do not have internet access from Harbor, then download it on any client vm and then copy to Harbor and load the image.

6.       Update this latest image in docker-compose file and then start all the services.

a.                   Navigate to /var/vcap/packages/harbor-app

b.                   Edit the docker-compose.yaml file, search for the harbor-log image and update it with latest image, goharbor/harbor-log:v1.10.3-dev.

c.                   Export the docker compose alias:
alias docker-compose='/var/vcap/packages/docker-compose/bin/docker-compose -H unix:///var/vcap/sys/run/docker/dockerd.sock -f /var/vcap/packages/harbor-app/docker-compose.yml '
export PATH=$PATH:/var/vcap/jobs/andes/bin/

d.                   Start all the services by running docker compose:
docker-compose up -d

e.                   Confirm that all the services are running and Harbor UI is accessible.

Note:  Please note that these changes are ephemeral and gets reverted upon vm recreation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
尝试运行单元管理工具命令时出现 "FileNotFoundException" 错误 (79525)

KB
•
[VMC on AWS] 非対称のトラフィックパスにより VMC SDDC でパケットドロップが発生する可能性がある (79533)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant