Support Questions
Find answers, ask questions, and share your expertise

unable to start Hive and hive metastore .

unable to start Hive and hive metastore .

Contributor

I am Unable to start HIve and Metastore in my hdp cluster due to following error

Caught an exception while executing custom service command: <type 'exceptions.OSError'>: [Errno 1] Operation not permitted: '/var/lib/ambari-agent/cred/conf/hive/hive-site.jceks'; [Errno 1] Operation not permitted: '/var/lib/ambari-agent/cred/conf/hive/hive-site.jceks'

Command failed after 1 tries

in logs I am getting this message 

17 Nov 2017 02:53:28,873  WARN [ambari-client-thread-30] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:53:33,263  INFO [ambari-client-thread-281] QuickLinkVisibilityControllerFactory:44 - No quick link profile is set, will display all quicklinks.
17 Nov 2017 02:53:33,565  INFO [ambari-client-thread-282] QuickLinkVisibilityControllerFactory:44 - No quick link profile is set, will display all quicklinks.
17 Nov 2017 02:53:33,566  INFO [ambari-client-thread-29] QuickLinkVisibilityControllerFactory:44 - No quick link profile is set, will display all quicklinks.
17 Nov 2017 02:53:34,806  INFO [ambari-client-thread-282] QuickLinkVisibilityControllerFactory:44 - No quick link profile is set, will display all quicklinks.
17 Nov 2017 02:53:41,694  INFO [ambari-client-thread-30] AbstractResourceProvider:939 - Received a updateHostComponent request, clusterName=myhdp, serviceName=HIVE, componentName=HIVE_SERVER, hostname=ip-172-31-91-248.ec2.internal, request={ clusterName=myhdp, serviceName=HIVE, componentName=HIVE_SERVER, hostname=ip-172-31-91-248.ec2.internal, publicHostname=null, desiredState=STARTED, state=null, desiredStackId=null, staleConfig=null, adminState=null, maintenanceState=null}
17 Nov 2017 02:53:41,695  INFO [ambari-client-thread-30] AbstractResourceProvider:650 - Handling update to host component, clusterName=myhdp, serviceName=HIVE, componentName=HIVE_SERVER, hostname=ip-172-31-91-248.ec2.internal, currentState=INSTALLED, newDesiredState=STARTED
17 Nov 2017 02:53:41,712  INFO [ambari-action-scheduler] ServiceComponentHostImpl:1028 - Host role transitioned to a new state, serviceComponentName=HIVE_SERVER, hostName=ip-172-31-91-248.ec2.internal, oldState=INSTALLED, currentState=STARTING
17 Nov 2017 02:53:42,376  INFO [qtp-ambari-agent-233] HeartBeatHandler:332 - HeartBeatHandler.sendCommands: sending ExecutionCommand for host ip-172-31-91-248.ec2.internal, role HIVE_SERVER, roleCommand START, and command ID 40-0, task ID 264
17 Nov 2017 02:53:42,395  INFO [ambari-client-thread-282] MetricsCollectorHAManager:54 - Adding collector host : ip-172-31-18-87.ec2.internal to cluster : myhdp
17 Nov 2017 02:53:44,994  WARN [ambari-heartbeat-processor-0] HeartbeatProcessor:547 - Structured output was found, but not parseable: "{}"
17 Nov 2017 02:53:44,994 ERROR [ambari-heartbeat-processor-0] HeartbeatProcessor:551 - Operation failed - may be retried. Service component host: HIVE_SERVER, host: ip-172-31-91-248.ec2.internal Action id 40-0 and taskId 264
17 Nov 2017 02:53:44,996  INFO [ambari-heartbeat-processor-0] ServiceComponentHostImpl:1028 - Host role transitioned to a new state, serviceComponentName=HIVE_SERVER, hostName=ip-172-31-91-248.ec2.internal, oldState=STARTING, currentState=INSTALLED
17 Nov 2017 02:54:03,078  WARN [ambari-client-thread-70] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:54:04,929  WARN [ambari-client-thread-70] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:54:08,110  WARN [ambari-client-thread-30] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:54:14,458  WARN [ambari-client-thread-30] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:55:22,703  WARN [ambari-client-thread-70] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:56:14,980  WARN [ambari-client-thread-30] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:56:21,303  WARN [ambari-client-thread-29] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:56:27,607  WARN [ambari-client-thread-70] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"
17 Nov 2017 02:56:33,908  WARN [ambari-client-thread-70] AbstractResourceProvider:259 - Unable to parse task structured output: "{}"