Hello Mark,
I’m using a NiFi 1.13.2 cluster with a CRON strategy «0 15 1 1/1 * ? *».
I will add the QuartzSchedulingAgent on logback.
I recently add specific log for ListSFTP processor using this logback
configuration :
<!-- Begin add/ListSFTP -->
<appender name="ListSFTP_FILE"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>/var/log/nifi/listsftp-events.log</file>
<rollingPolicy
class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
<fileNamePattern>/var/log/nifi/listsftp-events_%d{yyyy-MM-dd_HH}.%i.log</fileNamePattern>
<maxFileSize>5MB</maxFileSize>
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder
class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
<pattern>%date %level [%thread] %logger{40} %msg%n</pattern>
</encoder>
</appender>
<!-- End add/ListSFTP -->
<!-- Begin add/ListSFTP -->
<logger name="org.apache.nifi.processors.standard.ListSFTP"
level="TRACE" additivity="false">
<appender-ref ref="ListSFTP_FILE" />
</logger>
<!-- End add/ListSFTP -->
Actually I have this log about a ListSFTP processor which should have run
at 6:00pm yesterday :
./listsftp-events_2023-11-15_18.0.log:1:2023-11-15 18:00:00,684 DEBUG
[Timer-Driven Process Thread-7] o.a.nifi.processors.standard.ListSFTP
ListSFTP[id=488f2a4a-b9a8-3505-905e-db8366542b25] has chosen to yield its
resources; will not be scheduled to run again for 1000 milliseconds.
What does this message mean? If I understand correctly, it didn't start.
How can I find out the reason?
Best regards,
Quentin HORNEMAN GUTTON
Le mar. 14 nov. 2023 à 15:27, Mark Payne <marka...@hotmail.com> a écrit :
> Hi Quentin,
>
> What is the CRON schedule that you configured? What version of NiFi are
> you running?
>
> You’ll not see any debug related logs for that Processor by changing its
> log level, as the Processor is not responsible for scheduling itself. But
> you can enable DEBUG level logs for
> org.apache.nifi.controller.scheduling.QuartzSchedulingAgent and that will
> provide a debug log each time the Processor runs, indicating when it’s
> expected to run again.
>
> Thanks
> -Mark
>
>
> > On Nov 14, 2023, at 2:28 AM, Quentin HORNEMAN GUTTON <
> qhornemangut...@gmail.com> wrote:
> >
> > Hello,
> >
> > I am facing an issue that I am having difficulty resolving. I have a
> ListSFTP processor that is supposed to run every day at 12:15 AM, but it is
> not launching. I added TRACE logs to this type of processor, but since it
> is not launching, I cannot determine what is happening. If I change the
> launch time of the processor (for example, to 04:00 PM), it launches
> successfully. This is a NiFi cluster running on Redhat. Does anyone have an
> idea of how I can identify the root cause of this processor not launching ?
> >
> > Best regards,
>
>
