Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

ViPR SRM/Watch4Net: Couldn't synchronize the load factor for end point BackendX (508108)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 10046Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

ViPR SRM/Watch4Net: Couldn't synchronize the load factor for end point BackendX

In the load balancer arbiter log located on the backend host:
WARNING     -- [2017-09-29 08:39:37 GMT] -- Arbiter$BalancingThread::run(): The decision manager is still not ready. Waiting for the next balancing run
WARNING     -- [2017-09-29 08:39:39 GMT] -- LoadFactorDecision$EndPointLoadFactor::syncLoadFactor(): Couldn't synchronize the load factor for end point BackendX. Reverting to current load of 0.0 and a limit of 1.0: The server sent HTTP status code 403: Forbidden

On the ViPR SRM Backend host could see a lot of pending tasks which can be seen from Administration>>Centralized Management>>Physical Overview>>Problem Backend Host>>Tasks Tab

Running df -k on the Backend Host through putty could see 100% disk space used

The Backend cache logs located in /opt/APG/Backends/APG-Backend/Default/logs were not being updated with information

Cause

The ViPR SRM Backend Host had run out of disk space

Resolution

Extend the filesystem space on the problem backend server
Run mysql-database-check from opt/APG/bin on the problem backend server
Restart all services on the Backend Host cd /opt/APG/bin ./manage-modules.sh service restart all
Make sure all tasks run successfully for those backends from Administration>>Centralized Management>>Physical Overview>>Problem Backend Host>>Tasks Tab
Then reconfigure the load balancer arbiter  on problem backend server from administration>>centralized management>>solutions packs>>other components>>load balancer arbiter for problem server>>select pencil icon>.reconfigure

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant