Joe, thank you very much for your reply. They appear to be running with nifi 1.14.
I am remote from this team and so it has proven difficult to investigate their configuration. I began to comb through their configuration as best I could access it and when I looked in bootstrap.conf I stumbled across this: run.as= , set to nothing. I believe any changes they were trying to make through the UI to their flows were attempting to anonymously write to flow.xml.gz. And since that wasn't compliant with the perms on flow.xml.gz, I asked the user to set that bootstrap.conf parm. We then recycled her nifi service. She made a few simple changes to her flow, stopped and restarted her service, and her changes now persisted. On Thu, Jun 30, 2022 at 12:04 PM Joe Witt <[email protected]> wrote: > Jim, > > If I think back a very very long time I can think of when this might have > occurred/been possible but it certainly isn't something I've heard of in a > very long time. > > We'd need to understand the nifi version, the os/version, java version as > a starter. But also please look in the nifi-app.log as it would be > extremely unlikely any such issue could occur with no signs of correlated > trouble there. > > Thanks > > On Thu, Jun 30, 2022 at 7:20 AM James McMahon <[email protected]> > wrote: > >> Hello. I am trying to help a fellow nifi user who is finding that none of >> the changes she makes to her canvas are persisting to flow.xml.gz . Oddly, >> she has no group or use policies on her single-node nifi instance. I don't >> see that they have much security at all yet on her host at this point. >> >> The nifi process runs as her userid, and her user has rwx on the conf >> directory. Specifically, the perms on conf are drwxr-sr-x . >> >> We Dropped a single MonitorActivity on her NiFi Flow canvas. We then >> tested to see if it was saved by shutting down and (re)starting her nifi >> service. Her MonitorActivity was not part of her canvas. This tells me >> changes she is making are not being written to flow.xml.gz. >> >> This is very odd because she has been able to make changes in the past. >> What are the elements that must be configured so that flow.xml.gz may be >> updated? What can I help her check? Are there parms in nifi.properties that >> must be checked to ensure she can write to flow.xml.gz? >> >> Thanks in advance for any help. >> >
