Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Upgrade HDF 3.1.1.0 to HDF 3.1.2

avatar
Contributor

Hi All,

I tried upgrading from HDF 3.1.1.0 to HDF 3.1.2.

I upgraded to the new version of Ambari 2.6.2 from Ambari 2.6.0

And now Ambari not work as needed.

In upper menu do not exist, all menu items as " Dashboard Services Hosts Alerts Admin" not there.

If I click on specific service and press on button "Service Actions" only start and stop there and circle which show the loading process.

And I can to continue upgrade process because Ambari asks to run a service check.

If I install the new version of HDF 3.1.2 (not upgrade) all work as needed.

Please help.

In logs of Ambari I cannot find anything strange.

Update:

I found some strange rows in ambari-server.log Maybe something in scheduler?

ClusterImpl:1953 - No service found for config types '[cluster-env]', service config version not created
 <pre>08 Aug 2018 16:38:02,103  INFO [main] QuartzScheduler:305 - Scheduler meta-data: Quartz Scheduler (v2.2.1) 'ExecutionScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 5 threads.
  Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreTX' - which supports persistence. and is not clustered.

 
08 Aug 2018 16:38:01,400  WARN [main] Errors:173 - The following warnings have been detected with resource and/or provider classes:
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.ActionService.getActionDefinitions(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.ActionService.getActionDefinition(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getServices(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getService(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getServiceComponents(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getServiceComponent(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getRootHosts(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getRootHost(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getRootHostComponents(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getRootHostComponent(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String,java.lang.String,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RootServiceService.getRootHostComponent(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RequestService.getRequests(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.RequestService.getRequest(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.BlueprintService.getBlueprints(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.BlueprintService.getBlueprint(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.StacksService.getStacks(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.StacksService.getStack(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity.
  WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.StacksService.getStackLevelConfigurations(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String,java.lang.String), should not consume any entity.
1 ACCEPTED SOLUTION

avatar

Hi @Ilya Li ,

If you are using default postgreSQL of ambari ,

Please follow this steps which might help you get ride to this issue

1) Stop ambari -server

2) login to psql

psql -U ambari ambari

(default password will be bigdata)

select * from ambari.stack where stack_id in (select clusters.desired_stack_id from ambari.clusters);

probably it will be pointing towards HDF-3.1.0 if my assumption is correct or pointing towards a wrong REPO

then you might need to update the desired_stack_id to HDF-3.1.2 which is your current version , cluster id yu can get from clusters table.

update clusters set desired_stack_id = X where cluster_id = Y; 

You will get the stack_ID X from this command :

select stack_id,stack_version from stack;

Please refer to this help which explains it very good manner : https://community.hortonworks.com/content/supportkb/150258/the-ambari-versions-page-keeps-loading-wh...

Suggested DB backup before this operaton

If PostgreSQL:

  pg_dump -U ambari ambari > ./ambari_$(date +"%Y%m%d%H%M%S").sql

If MySQL:

mysqldump -u ambari -p ambari > ./ambari_$(date +"%Y%m%d%H%M%S").sql 

After the opration you can start ambari-server.

Please mark the asnwer as accepted if this helps you.

View solution in original post

5 REPLIES 5

avatar

Hi @Ilya Li ,

Can you please open developer console of your browser and see if there any Error exists in your UI.

you can press Press Ctrl + Shift + J (Windows / Linux) or Cmd + Opt + J (Mac) for the same.

Usually after the upgrade there is a chance some JS files are cached. can you see the Ambari-ui in incognito window and see if there is any exception.

Please post the screenshot of exception if you see any in Chrome console.

avatar
Contributor

In the incognito mode, I see the same result.

This is errors in console:

86393-2018-08-08-12-09-09.png

avatar

Hi @Ilya Li ,

If you are using default postgreSQL of ambari ,

Please follow this steps which might help you get ride to this issue

1) Stop ambari -server

2) login to psql

psql -U ambari ambari

(default password will be bigdata)

select * from ambari.stack where stack_id in (select clusters.desired_stack_id from ambari.clusters);

probably it will be pointing towards HDF-3.1.0 if my assumption is correct or pointing towards a wrong REPO

then you might need to update the desired_stack_id to HDF-3.1.2 which is your current version , cluster id yu can get from clusters table.

update clusters set desired_stack_id = X where cluster_id = Y; 

You will get the stack_ID X from this command :

select stack_id,stack_version from stack;

Please refer to this help which explains it very good manner : https://community.hortonworks.com/content/supportkb/150258/the-ambari-versions-page-keeps-loading-wh...

Suggested DB backup before this operaton

If PostgreSQL:

  pg_dump -U ambari ambari > ./ambari_$(date +"%Y%m%d%H%M%S").sql

If MySQL:

mysqldump -u ambari -p ambari > ./ambari_$(date +"%Y%m%d%H%M%S").sql 

After the opration you can start ambari-server.

Please mark the asnwer as accepted if this helps you.

avatar
Contributor

This fix was helped to me. Thank you

avatar

Hi @Ilya Li,

Glad to hear your issue is resolved.

If this comment helped you can you please accept this answer as Best answer so that other Users who face the issue will get Help from this.