Support Questions

Find answers, ask questions, and share your expertise

to add services in hdp-2.5. ambari-2.4.0.1

avatar
Contributor

i tried on to add services on multiple clusters using above version i was facing same issue.

screen was sitting like that.

7760-ambari.png

1 ACCEPTED SOLUTION

avatar
New Contributor

Hi,

We had this issue working with MySQL as Ambari's backend database.

What helped us solve this issue was updating a table called "cluster_version", it seemed that from some reason Ambari didn't update the "state" field of this table on cluster initial installation.

We found it by running over Amvari's web javascript code, located the REST API call for stack version, then finally finding the table name in the java code.

This is the update clause we used:

UPDATE ambari.cluster_version SET state = 'CURRENT';

Hope it helps.

View solution in original post

16 REPLIES 16

avatar
Master Guru

are there any logs? browser messages in javascript console?

what browser and platform are you running client from?

who added the other service or are those the OOTB ones?

avatar
Contributor

I have the same issue, cant get past it any way.. nothing in the logs, tried multiple browsers, added RAM.... still nothing.

avatar
Contributor

also tried with 2.4 stack .... same result. Seems like an ambari-server issue.

avatar
Contributor

I was getting this issue with 2.4.0.1 ambari, does this issue they have to fix in version?

avatar

@bob bza Do you see any error/Warning in the ambari-server.log?

avatar
Contributor

no, nothing is there. i spin up multiple clusters with this repo.

all the time i was facing same issue

http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.4.0.1/ambari.repo

avatar
Explorer

I am having the same problem: Add Service is stuck at Loading screen. Ambari 2.4.1.0 on CentOS 7 with HDP 2.5.

Tried at least six times. Once let the screen stay up for an hour.

---- Here are two excerpts from the Chrome browser dev tools console log:

Status code 200: Success.vendor.js:17347

STATEMANAGER: Sending event 'navigateAway' to state root.main.dashboard.widgets.vendor.js:17347 STATEMANAGER: Sending event 'unroutePath' to state root.main.dashboard.widgets.vendor.js:17347

STATEMANAGER: Sending event 'unroutePath' to state root.main.dashboard.vendor.js:17347

STATEMANAGER: Sending event 'unroutePath' to state root.main.vendor.js:17347

STATEMANAGER: Sending event 'routePath' to state root.main.vendor.js:17584

STATEMANAGER: Entering root.main.adminvendor.js:17584

STATEMANAGER: Entering root.main.admin.stackAndUpgradevendor.js:17584

STATEMANAGER: Entering root.main.admin.stackAndUpgrade.indexvendor.js:17584

STATEMANAGER: Entering root.main.admin.stackAndUpgrade.servicesapp.js:53802

Status code 200: Success.app.js:14629

Uncaught TypeError: Cannot read property 'repository_versions' of undefined app.js:53805

Status code 202: Success for creation.app.js:54093

App.alertDefinitionSummaryMapper execution time: 65.480ms

---- and later, this:

Status code 200: Success.vendor.js:17584

STATEMANAGER: Entering root.main.serviceAddapp.js:

Status code 20053802: Success.vendor.js:17584

STATEMANAGER: Entering root.main.serviceAdd.step1app.js:53805

Status code 202: Success for creation.app.js:34025

Uncaught TypeError: Cannot read property 'repository_versions' of undefinedapp.js:53802

Status code 200: Success.app.js:178322 Ajax loading time: host.status.counters [/clusters/foxdata?fields=Clusters/health_report,Clusters/total_hosts,alerts_summary_hosts&minimal_re]: 1307.275ms

----

where both TypeError lines are red.

Any help will be much appreciated.

avatar
Explorer

@Timothy Spann: do those Chrome console messages inspire any theories?

@bob bza: did you ever find a cure for this?

avatar
Contributor

i just created 1 node and then attaching rest nodes 1 by one. i dint find any other solution.