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 <[email protected]> wrote: > 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 <[email protected]> wrote: > > > Benji > > Is there more with the logs like component uuids and such? > > Thanks > > On Sun, Jul 31, 2022 at 1:08 PM Benji Benning <[email protected]> > 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, at 12:25, Joe Witt <[email protected]> wrote: >> >> >> >> Can you share the flow or does it contain sensitve info? >> >> On Sun, Jul 31, 2022 at 10:01 AM BeNJ <[email protected]> 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: >>> -------------------------------------- >>> 2022-07-31 03:10:05,448 INFO [main] o.a.n.c.s.AffectedComponentSet >>> Starting the following components: AffectedComponentSet[inputPorts=[], >>> outputPorts=[], remoteInputPorts=[], remoteOutputPorts=[], processors=[], >>> controllerServices=[], reportingTasks=[]] >>> 2022-07-31 03:10:05,452 WARN [main] >>> org.eclipse.jetty.webapp.WebAppContext Failed startup of context >>> o.e.j.w.WebAppContext@3ed03652 >>> {nifi-api,/nifi-api,file:///opt/nifi/nifi-current/work/jetty/nifi-web-api-1.16.0.war/webapp/,UNAVAILABLE}{./work/nar/extensions/nifi-server-nar-1.16.0.nar-unpacked/NAR-INF/bundled-dependencies/nifi-web-api-1.16.0.war} >>> org.apache.nifi.controller.serialization.FlowSynchronizationException: >>> java.lang.IllegalStateException: Cannot add Connection to Process Group >>> because source is an Output Port that does not belong to a child Process >>> Group >>> -------------------------------------- >>> I only restarted because out of nowhere i started seeing the following >>> errors repeating: >>> Processors cannot write to Content Repo: Unable to write flowfile >>> content to content repository container default due to archive file size >>> constraints; waiting for archive cleanup >>> >>> To resolve this issue, someone said online to set >>> nifi.content.repository.archive.enabled to false. I restarted and nifi >>> wouldn't come up again. >>> >>> I've tried reverting the flow.xml.gz to the oldest one in the archive >>> folder (was from 7pm yesterday), no luck. >>> it's a large config (1000+ active processors). >>> I would try to disable / delete the offending output port, but I don't >>> see how to find it from the logs. >>> >>> Any direction would be greatly appreciated. >>> >>> Thanks, >>> Benji >>> >>
