<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Upgrading Ambari 2.2 to 2.4 issue in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130776#M39345</link>
    <description>&lt;P&gt;Hi,  I have upgraded Ambari 2.2 to 2.4 and everything went well as per steps but it failed to start the ambari service and the following is the error&lt;/P&gt;&lt;P&gt;2016-08-31 21:52:28,082  INFO - ******************************* Check database started *******************************
2016-08-31 21:52:31,647  INFO - Checking for configs not mapped to any cluster
2016-08-31 21:52:31,653  INFO - Checking for configs selected more than once
2016-08-31 21:52:31,655  INFO - Checking for hosts without state
2016-08-31 21:52:31,657  INFO - Checking host component states count equals host component desired states count
2016-08-31 21:52:31,660  INFO - Checking services and their configs
2016-08-31 21:52:33,669 ERROR - Unexpected error, database check failed
java.lang.NullPointerException
        at org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:543)
        at org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;ram&lt;/P&gt;</description>
    <pubDate>Thu, 01 Sep 2016 09:21:24 GMT</pubDate>
    <dc:creator>ram_pratapa</dc:creator>
    <dc:date>2016-09-01T09:21:24Z</dc:date>
    <item>
      <title>Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130776#M39345</link>
      <description>&lt;P&gt;Hi,  I have upgraded Ambari 2.2 to 2.4 and everything went well as per steps but it failed to start the ambari service and the following is the error&lt;/P&gt;&lt;P&gt;2016-08-31 21:52:28,082  INFO - ******************************* Check database started *******************************
2016-08-31 21:52:31,647  INFO - Checking for configs not mapped to any cluster
2016-08-31 21:52:31,653  INFO - Checking for configs selected more than once
2016-08-31 21:52:31,655  INFO - Checking for hosts without state
2016-08-31 21:52:31,657  INFO - Checking host component states count equals host component desired states count
2016-08-31 21:52:31,660  INFO - Checking services and their configs
2016-08-31 21:52:33,669 ERROR - Unexpected error, database check failed
java.lang.NullPointerException
        at org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:543)
        at org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;ram&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 09:21:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130776#M39345</guid>
      <dc:creator>ram_pratapa</dc:creator>
      <dc:date>2016-09-01T09:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130777#M39346</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/11567/rampratapa.html" nodeid="11567"&gt;@Ramakrishna   Pratapa&lt;/A&gt; - Can you attach ambari-server-check-database.log file present in /var/log/ambari-server/ directory?&lt;/P&gt;&lt;P&gt;Also please try running:&lt;/P&gt;&lt;P&gt;ambari-server start --skip-database-check&lt;/P&gt;&lt;P&gt;and let us know how it goes&lt;/P&gt;&lt;P&gt;From the first look, the issue appears due to an inconsistency in a service configuration. &lt;/P&gt;&lt;P&gt;Additionally, please paste the output of:&lt;/P&gt;&lt;P&gt;ambari-server --version&lt;/P&gt;&lt;P&gt;-Vivek&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 13:24:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130777#M39346</guid>
      <dc:creator>vsharma</dc:creator>
      <dc:date>2016-09-01T13:24:45Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130778#M39347</link>
      <description>&lt;P&gt;I was able to start the server using &lt;/P&gt;&lt;P&gt;ambari-server start --skip-database-check&lt;/P&gt;&lt;P&gt;and the following command returns &lt;/P&gt;&lt;P&gt;ambari-server --version&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.4.0.1-1&lt;/P&gt;&lt;P&gt;I will continue my upgrade and see how it goes&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;&lt;P&gt;Ram&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 19:41:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130778#M39347</guid>
      <dc:creator>ram_pratapa</dc:creator>
      <dc:date>2016-09-01T19:41:12Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130779#M39348</link>
      <description>&lt;P&gt;You've hit a bug. It most likely has to do with a service configuration you still have for a service that's no longer on your stack. I will go ahead and file a Jira to have this fixed in Ambari 2.4.0.1 ... In the meantime, can you run this SQL on your database so we can determine which config is the problem:&lt;/P&gt;&lt;PRE&gt;SELECT
  c.cluster_name,
  cs.service_name,
  cc.type_name,
  sc.version
FROM clusterservices cs
JOIN serviceconfig sc
  ON cs.service_name = sc.service_name
  AND cs.cluster_id = sc.cluster_id
JOIN serviceconfigmapping scm
  ON sc.service_config_id = scm.service_config_id
JOIN clusterconfig cc
  ON scm.config_id = cc.config_id
  AND sc.cluster_id = cc.cluster_id
JOIN clusters c
  ON cc.cluster_id = c.cluster_id
  AND sc.stack_id = c.desired_stack_id
WHERE sc.group_id IS NULL
AND sc.service_config_id = (SELECT
  MAX(service_config_id)
FROM serviceconfig sc2
WHERE sc2.service_name = sc.service_name
AND sc2.cluster_id = sc.cluster_id)
GROUP BY c.cluster_name,
         cs.service_name,
         cc.type_name,
         sc.version
&lt;/PRE&gt;&lt;P&gt;Created &lt;A href="https://issues.apache.org/jira/browse/AMBARI-18296"&gt;AMBARI-18296&lt;/A&gt; to track this...&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 21:51:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130779#M39348</guid>
      <dc:creator>jonathanhurley</dc:creator>
      <dc:date>2016-09-01T21:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130780#M39349</link>
      <description>&lt;P&gt;Thank you for the quick response.   I thought it may be better to start  fresh and manually removed all artifacts related to Ambari 2.2 and Hdp 2.4 and started installing Ambari 2.4.0.1 as fresh install.&lt;/P&gt;&lt;P&gt;I should have waited little longer....&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Ram&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 22:28:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130780#M39349</guid>
      <dc:creator>ram_pratapa</dc:creator>
      <dc:date>2016-09-01T22:28:10Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130781#M39350</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am getting this same error and I've installed via yum repo: name=ambari-2.4.0.1 - Updates.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rupert&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2016 02:43:09 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130781#M39350</guid>
      <dc:creator>rupert_stechman</dc:creator>
      <dc:date>2016-09-07T02:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130782#M39351</link>
      <description>&lt;P&gt;how should one use the query results? is this the fix  --&amp;gt; delete sc rows where sc.group_id is null. Alternatively if there is a patch(#5621 commit? ) release can you please share the binary download link.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2016 01:13:46 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130782#M39351</guid>
      <dc:creator>skunkunuru</dc:creator>
      <dc:date>2016-09-08T01:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130783#M39352</link>
      <description>&lt;P&gt;You should see if the services reported for each config are still valid. If not, then it could just be an orphaned configuration which needs to be removed from the database.&lt;/P&gt;&lt;P&gt;Ambari 2.4.1 will address this issue by providing a warning but letting the server startup. &lt;/P&gt;</description>
      <pubDate>Fri, 09 Sep 2016 02:47:07 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130783#M39352</guid>
      <dc:creator>jonathanhurley</dc:creator>
      <dc:date>2016-09-09T02:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130784#M39353</link>
      <description>&lt;P&gt;Note the above query didn't work for us on PostgreSQL 9.2 where Ambari is using the &lt;EM&gt;ambari&lt;/EM&gt; schema instead of &lt;EM&gt;public&lt;/EM&gt;; the following query works in our case:&lt;/P&gt;&lt;PRE&gt;SELECT
  c.cluster_name,
  cs.service_name,
  cc.type_name,
  sc.version
FROM ambari.clusterservices cs
JOIN ambari.serviceconfig sc
  ON cs.service_name = sc.service_name
  AND cs.cluster_id = sc.cluster_id
JOIN ambari.serviceconfigmapping scm 
  ON sc.service_config_id = scm.service_config_id
JOIN ambari.clusterconfig cc
  ON scm.config_id = cc.config_id
  AND sc.cluster_id = cc.cluster_id
JOIN ambari.clusters c
  ON cc.cluster_id = c.cluster_id
  AND sc.stack_id = c.desired_stack_id
WHERE sc.group_id IS NULL
AND sc.service_config_id = (SELECT MAX(service_config_id)
  FROM ambari.serviceconfig sc2
  WHERE sc2.service_name = sc.service_name
  AND sc2.cluster_id = sc.cluster_id)
GROUP BY c.cluster_name,
 cs.service_name,
 cc.type_name,
 sc.version;
&lt;/PRE&gt;</description>
      <pubDate>Fri, 23 Sep 2016 03:16:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130784#M39353</guid>
      <dc:creator>demarkle</dc:creator>
      <dc:date>2016-09-23T03:16:43Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130785#M39354</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/11567/rampratapa.html" nodeid="11567"&gt;@Ramakrishna   Pratapa&lt;/A&gt;&lt;P&gt; Did the upgrade go smoothly? Were you able to upgrade by skipping the consistency check. I am hitting the same problem. Can you please suggest the path forward?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 09:51:26 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130785#M39354</guid>
      <dc:creator>bipin_alugubell</dc:creator>
      <dc:date>2017-01-25T09:51:26Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130786#M39355</link>
      <description>&lt;P&gt;Hi,  Good morning,   I ran into different issues and I felt it may be easy to do fresh install 2.4 after removing the 2.2.  So I went with fresh install.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ram&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 21:59:33 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130786#M39355</guid>
      <dc:creator>ram_pratapa</dc:creator>
      <dc:date>2017-01-25T21:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130787#M39356</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/11567/rampratapa.html" nodeid="11567"&gt;@Ramakrishna   Pratapa&lt;/A&gt; Thank you for your response. I already have a cluster running with 2.2 and now I upgraded to 2.4. Is it possible to remove ambari completely and install newly for an existing cluster? Can you please point me to the steps.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2017 01:21:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130787#M39356</guid>
      <dc:creator>bipin_alugubell</dc:creator>
      <dc:date>2017-01-26T01:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading Ambari 2.2 to 2.4 issue</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130788#M39357</link>
      <description>&lt;P&gt;I don't have any data in the cluster and hence it was easy for me to remove all bits from the nodes and did fresh install with 2.4.  But if you have data in the cluster it may be better to proceed with cluster upgrade steps and verify them as you have already upgraded the Ambari to 2.4.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ram&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2017 01:28:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Upgrading-Ambari-2-2-to-2-4-issue/m-p/130788#M39357</guid>
      <dc:creator>ram_pratapa</dc:creator>
      <dc:date>2017-01-26T01:28:00Z</dc:date>
    </item>
  </channel>
</rss>

