Recently, a machine learning platform was deployed on the company's Shenwei server, and many problems were encountered during the deployment process. This chapter mainly talks about the problems that occur in oozie.
Go straight! ! ! ! !
After oozie is started, it automatically hangs up after a period of time, and the interface can be accessed. I don’t know the reason, but I can only look at the log. The log has no error message. I am very entangled and I don’t know how to solve it. So I restarted oozie and there was a problem with the log. , Encountered oozie_pid already exists, it turns out that the pid file has been generated when oozie is started, but this is not a problem.
It still hangs after a while after booting. Tangled ~~~~ I don't know how to solve it.
Go to Du Niang. Someone has encountered this problem and modified it like this.
Add a configuration file to oozie-site.xml to call the configuration of hadoop
<property>
<name>oozie.service.HadoopAccessorService.hadoop.configurations</name>
<value>*=/usr/local/hadoop/etc/hadoop</value>
</property>
But I have configured this, and it has not been resolved.
It's okay to automatically hang up, I'm very worried, and I went to the doctor for a sudden illness.
Is there not enough memory? Is the cpu too high? It really is not. It is the kingly way to find the problem! ! ! ! !
Later, there is a hs_err_pid22831.log file under oozie/bin, happy~~~ Error. When I opened it, it turned out to be an error. I don't know how the error went under the bin. Let's solve it.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0xa) at pc=0x0000020008346ba8, pid=22831, tid=2201573061120
#
# JRE version: OpenJDK Runtime Environment (8.0) (build 1.8.0-h272-zhj_2017_08_10_10_45-b00)
# Java VM: OpenJDK 64-Bit Server VM (25.25-b02 mixed mode linux-sw64 compressed oops)
# Problematic frame:
# J 1849 C2 java.text.DecimalFormat.format(JLjava/lang/StringBuffer;Ljava/text/Format$FieldDelegate;)Ljava/lang/StringBuffer; (255 bytes) @ 0x0000020008346ba8 [0x0000020008346550+0x658]
#
# Core dump written. Default location: /usr/local/oozie/bin/core or core.22831
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
was originally a java problem, java_1.8_sw had a problem, so it was changed to version 1.7 and the problem was solved.