[
https://issues.apache.org/jira/browse/NIFI-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roberta updated NIFI-8384:
--------------------------
Description:
Hi All,
Hope everything is fine. I’m writing you as we are experiencing a problem in
Nifi 1.12.1 on a RHEL 7.8 with java version "1.8.0_281" .
It is a single node, secured, without any load balancer upstream. However, it
does have a s2s (it process provenance from another machine), ListSFTP +
FetchSFTP processors as well as the ExecuteStreamCommand processor.
After few days running NiFi suddenly shuts down reporting the following message:
_INFO [main]_ _org.apache.nifi.bootstrap.Command Apache NiFi is running at PID
XXXX but is not responding to ping requests_
Looking at the log file we are facing the following WARN:
_WARN [NiFi Web Server-XX-acceptor-X@XXXX -ServerConnector@XXXX
{SSL,[ssl, http/1.1]}\{hostname:9443}]
o.eclipse.jetty.server.AbstractConnector java.io.IOException: Too many open
files_
We tried to fix the problem my means of the best practice configurations
([https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices])
but the problem persists.
After some research we found out that a possible cause might be the use of the
processor FetchSFTP that we use in our flow. It creates always new files during
SFTP connections (https://issues.apache.org/jira/browse/NIFI-7222). We would
like to substitute the .nar file you attached to jira but, unfortunately, it is
no more available.
Based on your experience, is it possible that the bug found in NiFi 11.1.4 and
1.12.0 could be still present in the 1.12.1?
Thank you in advance for your support and let me know if you need further
details
was:
Hi All,
Hope everything is fine. I’m writing you as we are experiencing a problem in
Nifi 1.12.1 on a RHEL 7.8 with java version "1.8.0_281" .
It is a single node, secured, without any load balancer upstream. However, it
does have a s2s (it process provenance from another machine), ListSFTP +
FetchSFTP processors as well as the ExecuteStreamCommand processor.
After few days running NiFi suddenly shuts down reporting the following message:
_INFO [main]_ _org.apache.nifi.bootstrap.Command Apache NiFi is running at PID
XXXX but is not responding to ping requests_
Looking at the log file we are facing the following WARN:
_WARN [NiFi Web Server-XX-acceptor-X@XXXX -ServerConnector@XXXX
\{SSL,[ssl, http/1.1]}_
_\{hostname:9443}] o.eclipse.jetty.server.AbstractConnector
java.io.IOException: Too many open files__
We tried to fix the problem my means of the best practice configurations
([https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices])
but the problem persists.
After some research we found out that a possible cause might be the use of the
processor FetchSFTP that we use in our flow. It creates always new files during
SFTP connections (https://issues.apache.org/jira/browse/NIFI-7222). We would
like to substitute the .nar file you attached to jira but, unfortunately, it is
no more available.
Based on your experience, is it possible that the bug found in NiFi 11.1.4 and
1.12.0 could be still present in the 1.12.1?
Thank you in advance for your support and let me know if you need further
details
> NiFi 1.12.1 : Too many open files
> ---------------------------------
>
> Key: NIFI-8384
> URL: https://issues.apache.org/jira/browse/NIFI-8384
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.12.1
> Environment: RHEL 7.8
> java version 1.8.0_281
> Reporter: Roberta
> Priority: Major
>
> Hi All,
> Hope everything is fine. I’m writing you as we are experiencing a problem in
> Nifi 1.12.1 on a RHEL 7.8 with java version "1.8.0_281" .
> It is a single node, secured, without any load balancer upstream. However, it
> does have a s2s (it process provenance from another machine), ListSFTP +
> FetchSFTP processors as well as the ExecuteStreamCommand processor.
> After few days running NiFi suddenly shuts down reporting the following
> message:
> _INFO [main]_ _org.apache.nifi.bootstrap.Command Apache NiFi is running at
> PID XXXX but is not responding to ping requests_
> Looking at the log file we are facing the following WARN:
> _WARN [NiFi Web Server-XX-acceptor-X@XXXX -ServerConnector@XXXX
> {SSL,[ssl, http/1.1]}\{hostname:9443}]
> o.eclipse.jetty.server.AbstractConnector java.io.IOException: Too many open
> files_
> We tried to fix the problem my means of the best practice configurations
> ([https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices])
> but the problem persists.
> After some research we found out that a possible cause might be the use of
> the processor FetchSFTP that we use in our flow. It creates always new files
> during SFTP connections (https://issues.apache.org/jira/browse/NIFI-7222). We
> would like to substitute the .nar file you attached to jira but,
> unfortunately, it is no more available.
> Based on your experience, is it possible that the bug found in NiFi 11.1.4
> and 1.12.0 could be still present in the 1.12.1?
> Thank you in advance for your support and let me know if you need further
> details
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
