Skip to main content
phadkev
phadkev
Silver ⭐️⭐️
November 19, 2024
Solved

Nifi not starting because of OnScheduled()

2024-11-19 04:52:41,378 WARN [Monitor Processor Lifecycle Thread-1] o.a.n.controller.StandardProcessorNode Timed out while waiting for OnScheduled of ExecuteScript[id=acb441ba-c36b-1fdd-53f2-3a4821d43833] to finish. An attempt is made to cancel the task via Thread.interrupt(). However it does not guarantee that the task will be canceled since the code inside current OnScheduled operation may have been written to ignore interrupts which may result in a runaway thread. This could lead to more issues, eventually requiring NiFi to be restarted. This is usually a bug in the target Processor 'ExecuteScript[id=acb441ba-c36b-1fdd-53f2-3a4821d43833]' that needs to be documented, reported and eventually fixed.

MattWho
MattWhoAnswer
Titanium ⭐️⭐️⭐️
November 19, 2024

@phadkev 

Would need to see more of the nifi-app.log to better understand what is going on here.

Are you seeing the same org.apache.nifi.controller.StandardProcessorNode Timed out while waiting for OnScheduled exception for other components or just this executeScript processor?

The exception itself is generic and could be thrown for any processor class.

Are you ever seeing the log line telling you the NiFi UI is available at the following urls?
If so NiFi is up.

Are you seeing NiFi shut back down with some exception and stack trace in the nifi-app.log.

What you shared implies NiFi is having issues scheduling this specific processor to execute.  This could very well be caused by an issue with the custom script that was build and used in this processor.

If you NiFi is really not coming up, you could modify the nifi.properties file by changing 
"nifi.flowcontroller.autoResumeState=true" to "nifi.flowcontroller.autoResumeState=false".  This will allow you NiFi to start without starting any processors.  You could then search the UI for the ExecuteScript component processor with id "acb441ba-c36b-1fdd-53f2-3a4821d43833".    Disable it and start all your other processors.  Restart your NiFi to see if you still have any issues.   This isolates the issue to this processor and your script.

Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

 

View in thread

3 replies

VidyaSargur
Community Manager
VidyaSargur
Community Manager
November 19, 2024

@phadkev, Welcome to our community! To help you get the best possible answer, I have tagged our NiFi experts @satz @MattWho who may be able to assist you further.

Please feel free to provide any additional information or details about your query, and we hope that you will find a satisfactory solution to your question.w

Translate
Regards, Vidya Sargur, Community Manager Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.
satz
Gold ⭐️
satz
Gold ⭐️
November 19, 2024

@phadkev Thank you for posting your query. 

These WARN messages which we are seeing probably could be due to the script which is configured on ExecuteScript processor

Does that script runs fine on schedules ?

Translate
Thanks, Satz
    MattWho
    Titanium ⭐️⭐️⭐️
    MattWhoAnswer
    Titanium ⭐️⭐️⭐️
    November 19, 2024

    @phadkev 

    Would need to see more of the nifi-app.log to better understand what is going on here.

    Are you seeing the same org.apache.nifi.controller.StandardProcessorNode Timed out while waiting for OnScheduled exception for other components or just this executeScript processor?

    The exception itself is generic and could be thrown for any processor class.

    Are you ever seeing the log line telling you the NiFi UI is available at the following urls?
    If so NiFi is up.

    Are you seeing NiFi shut back down with some exception and stack trace in the nifi-app.log.

    What you shared implies NiFi is having issues scheduling this specific processor to execute.  This could very well be caused by an issue with the custom script that was build and used in this processor.

    If you NiFi is really not coming up, you could modify the nifi.properties file by changing 
    "nifi.flowcontroller.autoResumeState=true" to "nifi.flowcontroller.autoResumeState=false".  This will allow you NiFi to start without starting any processors.  You could then search the UI for the ExecuteScript component processor with id "acb441ba-c36b-1fdd-53f2-3a4821d43833".    Disable it and start all your other processors.  Restart your NiFi to see if you still have any issues.   This isolates the issue to this processor and your script.

    Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

    Thank you,
    Matt

     

    Translate
      Terms & ConditionsAccessibility statement