<?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 Re: Cannot start secondary namenode:  &amp;quot;currentState=STOPPING, newDesiredState=STARTED&amp;quot; in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cannot-start-secondary-namenode-quot-currentState-STOPPING/m-p/232694#M82832</link>
    <description>&lt;P&gt;Thanks for the tip.   I have the same problem but alas I don't have the same skills &amp;amp; understanding of the ambari internals.  &lt;/P&gt;&lt;P&gt;Please tell me how you solved it -- where are the entries in the Ambari internal DB to fix, please?&lt;/P&gt;&lt;P&gt;Thx very much&lt;/P&gt;</description>
    <pubDate>Tue, 06 Aug 2019 04:25:22 GMT</pubDate>
    <dc:creator>L_JanseVanRensb</dc:creator>
    <dc:date>2019-08-06T04:25:22Z</dc:date>
    <item>
      <title>Cannot start secondary namenode:  "currentState=STOPPING, newDesiredState=STARTED"</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cannot-start-secondary-namenode-quot-currentState-STOPPING/m-p/232692#M82830</link>
      <description>&lt;P&gt;Good morning!&lt;/P&gt;&lt;P&gt;So, I just upgraded a small cluster to Version 3.0.0.   The upgrade seemed to go well.   But after a reboot I am stuck-  I have two services that ambari still thinks are "stopping...".  (seconday namenode and also zookeeper)&lt;BR /&gt;&lt;BR /&gt;Because of this, I can't get the services running.     The error I get is:&lt;/P&gt;&lt;PRE&gt;Error message: java.lang.IllegalArgumentException: Invalid transition for servicecomponenthost, clusterName=ontomatedev, clusterId=2, serviceName=HDFS, componentName=SECONDARY_NAMENODE, hostname=myhost.domain.com, currentState=STOPPING, newDesiredState=STARTED&lt;/PRE&gt;&lt;P&gt;As far as I can tell, I *should* hopefully be able to "reset" this somehow via a curl command but I'm at a loss as to what.&lt;/P&gt;&lt;P&gt;Something like this has no effect:&lt;/P&gt;&lt;P&gt;curl -s -u admin:admin -H 'X-Requested-By: Ambari' -X PUT -d '{"RequestInfo":{"context":"Stop Component"},"Body":{"HostRoles":{"state":"INSTALLED"}}}' &lt;A href="http://localhost:8080/api/v1/clusters/ontomatedev/hosts/myhost.domain.com/host_components/SECONDARY_NAMENODE" target="_blank"&gt;http://localhost:8080/api/v1/clusters/ontomatedev/hosts/myhost.domain.com/host_components/SECONDARY_NAMENODE&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If anyone can tell me how to reset this incorrect 'state' I'd be *most* grateful!!!&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 21:23:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cannot-start-secondary-namenode-quot-currentState-STOPPING/m-p/232692#M82830</guid>
      <dc:creator>kbrodie</dc:creator>
      <dc:date>2018-08-28T21:23:55Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot start secondary namenode:  "currentState=STOPPING, newDesiredState=STARTED"</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cannot-start-secondary-namenode-quot-currentState-STOPPING/m-p/232693#M82831</link>
      <description>&lt;P&gt;After several hours of searching, I have come to the conclusion that there is no easy fix for this, specifically through ambari API calls, which is a shame.   The API calls in terms of services are limited to stopping, starting, adding, deleting.   But there's no way to "fix" a broken state as per above.&lt;BR /&gt;&lt;BR /&gt;Apparently the only way to solve this was to hack the ambari database and change the component state from "STOPPING" to "INSTALLED" and then I was fine.&lt;BR /&gt;&lt;BR /&gt;There really oight to be a better way.....&lt;/P&gt;</description>
      <pubDate>Wed, 29 Aug 2018 02:37:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cannot-start-secondary-namenode-quot-currentState-STOPPING/m-p/232693#M82831</guid>
      <dc:creator>kbrodie</dc:creator>
      <dc:date>2018-08-29T02:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot start secondary namenode:  "currentState=STOPPING, newDesiredState=STARTED"</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cannot-start-secondary-namenode-quot-currentState-STOPPING/m-p/232694#M82832</link>
      <description>&lt;P&gt;Thanks for the tip.   I have the same problem but alas I don't have the same skills &amp;amp; understanding of the ambari internals.  &lt;/P&gt;&lt;P&gt;Please tell me how you solved it -- where are the entries in the Ambari internal DB to fix, please?&lt;/P&gt;&lt;P&gt;Thx very much&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2019 04:25:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cannot-start-secondary-namenode-quot-currentState-STOPPING/m-p/232694#M82832</guid>
      <dc:creator>L_JanseVanRensb</dc:creator>
      <dc:date>2019-08-06T04:25:22Z</dc:date>
    </item>
  </channel>
</rss>

