Re: Crash on startup due to Output port issue

2022-08-01 Thread Joe Witt
Benji Probably built on 11 but you're running on 8anyway given we know now the issue has to do with the json file and you're back in business it is probably best to leave the debug nar alone. Thanks Matt for your willingness to help unpack more details. Does seem like we should do this on ma

Re: Crash on startup due to Output port issue

2022-08-01 Thread BeNJ
Hi Matt, Issues with the NAR i assume: --- 2022-08-01 15:30:32,065 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi/nifi-current/./work/nar/extensions/nifi-spring-nar-1.16.0.nar-unpacked as class loader org.apache.nifi.nar.NarClassLo

Re: Crash on startup due to Output port issue

2022-08-01 Thread Matt Burgess
Benji, I've built a custom framework NAR [1] that has additional logging to identify which components, process groups, etc. are causing the issue. If you'd like, please feel free to save off your existing framework NAR and replace it with this, then share the relevant section of the log (matching

Re: Crash on startup due to Output port issue

2022-08-01 Thread Mark Payne
Benji, Fantastic, thanks for following up! We’ve clearly got something to address but I’m very happy that we’ve found a way to get you unblocked for now. Thanks Mark Sent from my iPhone On Aug 1, 2022, at 12:46 PM, BeNJ wrote:  Updates: Mark: Deleting the json allows nifi to start up(!!) -

Re: Crash on startup due to Output port issue

2022-08-01 Thread BeNJ
Updates: Mark: Deleting the json allows nifi to start up(!!) - note that restarting (with the newly generated json in place) causes the same issue on startup. Joe: I'm happy to run custom debug nars to help figure out how to resolve this. Thank you, I really appreciate everyone's help with this! B

Re: Crash on startup due to Output port issue

2022-08-01 Thread Joe Witt
Ben I didn't see any log levels that would help narrow this down. If Mark's suggestion does not address it it will likely require updating the flow configuration manually or a patched framework nar to do better logging. I'm also wondering if the json form of the flow could be imported on a clean

Re: Crash on startup due to Output port issue

2022-08-01 Thread Mark Payne
Benji, I would recommend you try to remove (or rename) the flow.json.gz - but not the flow.xml.gz. See if that makes any difference. Thanks -Mark Sent from my iPhone On Jul 31, 2022, at 11:35 PM, BeNJ wrote:  Also please see the attached nifi.properties Thanks, Benji On Sun, Jul 31, 2022

Re: Crash on startup due to Output port issue

2022-07-31 Thread BeNJ
Also please see the attached nifi.properties Thanks, Benji On Sun, Jul 31, 2022 at 4:28 PM BeNJ wrote: > Hi Joe, > Stack with a couple of info logs from before and after, and the final exit > shortly after. > >

Re: Crash on startup due to Output port issue

2022-07-31 Thread BeNJ
Hi Joe, Stack with a couple of info logs from before and after, and the final exit shortly after. -- 2022-07-31 16:20:35,311 INFO [main] o.a.n.g.StandardProcessGroupSynchronizer Added Connection[ID=cfee198f-3d2b

Re: Crash on startup due to Output port issue

2022-07-31 Thread Joe Witt
Benji What would be helpful to see is the full stacktrace like shown in this stackoverflow post https://stackoverflow.com/questions/72459434/apache-nifi-1-16-0-windows-server-closes-immediately This class changes often so I want to make sure we check the right one for your version. Thanks On Su

Re: Crash on startup due to Output port issue

2022-07-31 Thread David Early via users
Benji, Can you share your nifi.properties file? This problem can show up if the disk fills up but depends on the configuration. Also, what does df -h show for your disks (assuming you are running on Linux)? Dave On Sun, Jul 31, 2022, 2:21 PM Benji Benning wrote: > Not really around the belo

Re: Crash on startup due to Output port issue

2022-07-31 Thread Benji Benning
Not really around the below error. Anything I can move to debug or trace in logback.xml to add some color around this? Thanks, Benji Sent from my iPhone > On Jul 31, 2022, at 15:12, Joe Witt wrote: > >  > Benji > > Is there more with the logs like component uuids and such? > > Thanks > >>

Re: Crash on startup due to Output port issue

2022-07-31 Thread Joe Witt
Benji Is there more with the logs like component uuids and such? Thanks On Sun, Jul 31, 2022 at 1:08 PM Benji Benning wrote: > Hi Joe, > Unfortunately it does indeed contain sensitive info. > Is there any debug info I can provide? > > Thanks, > Benji > > Sent from my iPhone > > On Jul 31, 2022

Re: Crash on startup due to Output port issue

2022-07-31 Thread Benji Benning
Hi Joe, Unfortunately it does indeed contain sensitive info. Is there any debug info I can provide? Thanks, Benji Sent from my iPhone > On Jul 31, 2022, at 12:25, Joe Witt wrote: > >  > Can you share the flow or does it contain sensitve info? > >> On Sun, Jul 31, 2022 at 10:01 AM BeNJ wrote

Re: Crash on startup due to Output port issue

2022-07-31 Thread Joe Witt
Can you share the flow or does it contain sensitve info? On Sun, Jul 31, 2022 at 10:01 AM BeNJ wrote: > Hi, > I'm a little at a loss so I figured maybe someone here would have an idea > of how to get out of this situation. > My NiFI is crashing on startup with the following: > --

Crash on startup due to Output port issue

2022-07-31 Thread BeNJ
Hi, I'm a little at a loss so I figured maybe someone here would have an idea of how to get out of this situation. My NiFI is crashing on startup with the following: -- 2022-07-31 03:10:05,448 INFO [main] o.a.n.c.s.AffectedComponentSet Starting the following comp