ERROR: “Python script has been killed due to timeout after waiting 300 secs” while performing Oozie service check

[#1]

PROBLEM DESCRIPTION

The Oozie service check fails and the following error message is displayed in Ambari:

stderr: /var/lib/ambari-agent/data/errors-12523.txt

Python script has been killed due to timeout after waiting 300 secs There is no error in the stdout. The service check is terminated because the timeout (300 secs by default) is reached.

CAUSE

This issue occurs when the time taken by Ambari to upload jar and workflow files to hdfs for Oozie service check takes longer than the timeout mentioned in the server settings.

Example:

Nodes in a cluster are configured on ipv4 proxy, which causes network slowness among nodes. Ambari uploads jar files and workflow files to the hdfs for Oozie service check, depending on network performance time required to upload these files exceeds 300 secs timeout.

WORKAROUND

To increase the timeout, find and update the timeout set in the metainfo.xml file located in Edit /var/lib/ambari-server/resources/common-services/OOZIE/your_version_number/metainfo.xml,

RESOLUTION

Improve the network performance, so that the Oozie service check can be finished in 300 secs timeout period.