Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Apache Ambari error while starting components

Solved Go to solution
Highlighted

Apache Ambari error while starting components

Explorer

Hi,

Am getting below error from Ambari UI i.e., while starting or stopping or restarting the components present in Hadoop cluster. Could any one help please 

______________________________________________________________________________

Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120608-r11652): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.BatchUpdateException: Batch entry 0 INSERT INTO request (request_id, cluster_id, command_name, create_time, end_time, exclusive_execution, inputs, request_context, request_type, start_time, status, request_schedule_id) VALUES (820, 2, NULL, 1587733705827, -1, 0, NULL, 'Start History Server', 'INTERNAL_REQUEST', -1, NULL, NULL) was aborted. Call getNextException to see the cause.
Error Code: 0
Call: INSERT INTO request (request_id, cluster_id, command_name, create_time, end_time, exclusive_execution, inputs, request_context, request_type, start_time, status, request_schedule_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [12 parameters bound]

 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Apache Ambari error while starting components

Explorer

I solved above error by myself by clearing machine space.

View solution in original post

3 REPLIES 3
Highlighted

Re: Apache Ambari error while starting components

please give some screenshot from ambari

as you know each service have a log file , try to see what are the details from the log

 

Michael-Bronson
Highlighted

Re: Apache Ambari error while starting components

Explorer

there is no info in ambari so I have shared log details.

Re: Apache Ambari error while starting components

Explorer

I solved above error by myself by clearing machine space.

View solution in original post

Don't have an account?
Coming from Hortonworks? Activate your account here