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.

NIFI ERROR Crash Machine

Highlighted

NIFI ERROR Crash Machine

New Contributor

Hello,

We have a problem with our cluster NiFi. We have three virtual machines SLES12 in the same Hypervisor machine. A machine (only one) crash very much times with an error Java in nifi-users.log and nifi-app.log

2019-01-31 12:21:23,392 INFO [NiFi logging handler] org.apache.nifi.StdOut # A fatal error has been detected by the Java Runtime Environment:

2019-01-31 12:21:23,392 INFO [NiFi logging handler] org.apache.nifi.StdOut #

2019-01-31 12:21:23,392 INFO [NiFi logging handler] org.apache.nifi.StdOut # SIGBUS (0x7) at pc=0x00007f1932d8e21e, pid=2017629, tid=0x00007f18f482a700

2019-01-31 12:21:23,393 INFO [NiFi logging handler] org.apache.nifi.StdOut #

2019-01-31 12:21:23,393 INFO [NiFi logging handler] org.apache.nifi.StdOut # JRE version: OpenJDK Runtime Environment (8.0_161-b12) (build 1.8.0_161-b12)

2019-01-31 12:21:23,393 INFO [NiFi logging handler] org.apache.nifi.StdOut # Java VM: OpenJDK 64-Bit Server VM (25.161-b12 mixed mode linux-amd64 compressed oops)

2019-01-31 12:21:23,393 INFO [NiFi logging handler] org.apache.nifi.StdOut # Derivative: IcedTea 3.7.0

2019-01-31 12:21:23,393 INFO [NiFi logging handler] org.apache.nifi.StdOut # Distribution: Custom build (Mon Mar 5 16:04:55 UTC 2018)

2019-01-31 12:21:23,393 INFO [NiFi logging handler] org.apache.nifi.StdOut # Problematic frame:

Could you help us

Thanks in advance for your help

1 REPLY 1

Re: NIFI ERROR Crash Machine

Rising Star

It is unlikely that the error is directly related to NiFi itself, as this type of error typically indicates a JRE or hardware issue. Some initial searching indicates that a full device (particularly /tmp) may be to blame. Failing that, check the next few lines in the log, which should contain a dump of the frame that triggered the error and a reference to the library being called.

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