You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Ryan H <ry...@gmail.com> on 2019/01/24 15:11:17 UTC
Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key Was Provided
Hi All,
We are currently in the process of upgrading from NiFi 1.5 to 1.8. After
making the binary changes and restarting the cluster (a secure cluster
setup), we are getting the following error:
ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
properties key was provided Specify a unique key in nifi.properties for
nifi.sensitive.props.key
The Encrypt Config Tool in NiFi Toolkit can be used to migrate the flow to
the new key.
We are using all the same config that was in the 1.5 setup, including a
blank key for nifi.sensitive.props.key which wasn't an issue before, but
now it seems that it is. I didn't see this as a known issue in any of the
migration guides or release notes. Can anyone provide any insight on this?
Steps to remediate? Is the cause exactly what the error message says,
having a blank value for this config prop?
Cheers,
Ryan H
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Ryan H <ry...@gmail.com>.
Hi Andy,
Thanks for the response. We had our log levels set to ERROR, so the real
issue was flushed out once I brought the log levels down to INFO instead to
debug. One thing that kind of puzzles me is that the item that caused the
web server to not start came thru as WARN messages instead of ERROR. There
was a missing dependency which caused the Flow Controller to not start. I
would've expected that to be an ERROR and not a WARN.
Some of the log output from nifi-app.log:
2019-01-24 17:43:35,185 WARN [main] org.apache.nifi.web.server.JettyServer
Failed to start web server... shutting down.
org.apache.nifi.web.NiFiCoreException: Unable to start Flow Controller.
at
org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:97)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:953)
....
at org.apache.nifi.NiFi.main(NiFi.java:296)
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'ourMissingClass': FactoryBean threw exception on
object creation; nested exception is java.lang.ClassCastException: class
our.missing.class
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:185)
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1640)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
at
org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1086)
at
org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:93)
... 33 common frames omitted
Caused by: java.lang.ClassCastException: class our.missing.class
at
org.apache.nifi.web.security.spring.LoginIdentityProviderFactoryBean.loadExtendedLoginIdentityProviderClass(LoginIdentityProviderFactoryBean.java:239)
at
org.apache.nifi.web.security.spring.LoginIdentityProviderFactoryBean.createLoginIdentityProvider(LoginIdentityProviderFactoryBean.java:162)
at
org.apache.nifi.web.security.spring.LoginIdentityProviderFactoryBean.getObject(LoginIdentityProviderFactoryBean.java:113)
at
org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:178)
... 39 common frames omitted
salesforce-send-connector 2019-01-24 17:43:35,267 INFO [Thread-1]
org.apache.nifi.NiFi Initiating shutdown of Jetty web server...
All the same we got it worked out. I was just a bit confused that the above
came thru as a WARN instead of an ERROR.
Cheers,
Ryan H
On Thu, Jan 24, 2019 at 12:54 PM Andy LoPresto <al...@apache.org> wrote:
> Ryan,
>
> I added that warning [1], and Joe’s right, it should have been at a WARN
> severity. However, it definitely isn’t blocking the access to the canvas
> (intentionally). Like Joe said, if you can provide a full stacktrace, and
> possibly your config files (redacting sensitive information as necessary),
> we can try to diagnose.
>
> [1]
> https://github.com/apache/nifi/commit/744b15b4a7a7533ef81fc2333df0cd212c3779eb#diff-c12a63700e2b9a86823209f49e04dd04R216
>
> Andy LoPresto
> alopresto@apache.org
> *alopresto.apache@gmail.com <al...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Jan 24, 2019, at 9:38 AM, Ryan H <ry...@gmail.com>
> wrote:
>
> Hi Joe,
>
> Yes here are the only logs that I am seeing here as of now (I will
> probably turn on DEBUG levels to get more):
>
> ***nifi-app.log***
> 2019-01-24 17:32:51,583 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
> properties key was provided *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * Specify a
> unique key in nifi.properties *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * for
> nifi.sensitive.props.key *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor *
> *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
> Tool in NiFi Toolkit can be used to *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * migrate the
> flow to the new key *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:53,283 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
> properties key was provided *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * Specify a
> unique key in nifi.properties *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * for
> nifi.sensitive.props.key *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor *
> *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
> Tool in NiFi Toolkit can be used to *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * migrate the
> flow to the new key *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:53,589 INFO [main] org.wali.MinimalLockingWriteAheadLog
> org.wali.MinimalLockingWriteAheadLog@7ee45cbe finished recovering
> records. Performing Checkpoint to ensure proper state of Partitions before
> updates
> 2019-01-24 17:32:53,667 INFO [main] org.wali.MinimalLockingWriteAheadLog
> Successfully recovered 0 records in 81 milliseconds
> 2019-01-24 17:32:53,678 INFO [main] org.wali.MinimalLockingWriteAheadLog
> org.wali.MinimalLockingWriteAheadLog@7ee45cbe checkpointed with 0 Records
> and 0 Swap Files in 10 milliseconds (Stop-the-world time = 3 milliseconds,
> Clear Edit Logs time = 2 millis), max Transaction ID -1
> 2019-01-24 17:33:06,286 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
> Starting
> 2019-01-24 17:33:06,410 INFO [main-EventThread]
> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
> 2019-01-24 17:33:06,467 INFO [Curator-Framework-0]
> o.a.c.f.imps.CuratorFrameworkImpl backgroundOperationsLoop exiting
> 2019-01-24 17:33:06,485 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
> Starting
> 2019-01-24 17:33:06,501 INFO [main-EventThread]
> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
>
> ***nifi-bootstrap.log***
> 2019-01-24 17:33:08,476 ERROR [NiFi logging handler]
> org.apache.nifi.StdErr Failed to start web server: Unable to start Flow
> Controller.
> 2019-01-24 17:33:08,479 ERROR [NiFi logging handler]
> org.apache.nifi.StdErr Shutting down...
>
>
> -Ryan H
>
> On Thu, Jan 24, 2019 at 11:48 AM Joe Witt <jo...@gmail.com> wrote:
>
>> ryan
>>
>> right...i think you are facing something else. We have locked down on
>> some headers, etc.. They are mentioned in the migration guide.
>>
>> Can you share the logs from a full startup run?
>>
>> thanks
>>
>> On Thu, Jan 24, 2019, 11:21 AM Ryan H <ryan.howell.development@gmail.com
>> wrote:
>>
>>> Hi Joe,
>>>
>>> Thanks for the reply. Agreed on the secure setup and we will definitely
>>> look to add value(s) for these properties. The issue we hit was that we
>>> weren't able to access the UI, and I was thinking that this error was
>>> preventing this. You think that this error shouldn't block accessing the
>>> canvas though?
>>>
>>> -Ryan
>>>
>>> On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <jo...@gmail.com> wrote:
>>>
>>>> Ryan,
>>>>
>>>> That block of text that shows up in the log could arguably said "WARN"
>>>> because the flow will continue to function as it did before.
>>>>
>>>> However, the reason it is an error is that you really should follow its
>>>> advice and specifically follow the secure nifi configuration guidance.
>>>>
>>>> By not following that you have a setup which is not secure.
>>>>
>>>> We're doing all we can as a community to move to 'secure by default'
>>>> configurations which will take time. It requires improved tooling out of
>>>> the box and we want the 'initial up and running experience' to be as smooth
>>>> as possible and similar to how it works now.
>>>>
>>>> Anyway, hopefully that helps explain.
>>>>
>>>> Thanks
>>>> Joe
>>>>
>>>> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <
>>>> ryan.howell.development@gmail.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> We are currently in the process of upgrading from NiFi 1.5 to 1.8.
>>>>> After making the binary changes and restarting the cluster (a secure
>>>>> cluster setup), we are getting the following error:
>>>>>
>>>>> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank
>>>>> sensitive properties key was provided Specify a unique key in
>>>>> nifi.properties for nifi.sensitive.props.key
>>>>> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the
>>>>> flow to the new key.
>>>>>
>>>>> We are using all the same config that was in the 1.5 setup, including
>>>>> a blank key for nifi.sensitive.props.key which wasn't an issue before, but
>>>>> now it seems that it is. I didn't see this as a known issue in any of the
>>>>> migration guides or release notes. Can anyone provide any insight on this?
>>>>> Steps to remediate? Is the cause exactly what the error message says,
>>>>> having a blank value for this config prop?
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Ryan H
>>>>>
>>>>
>
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Andy LoPresto <al...@apache.org>.
Ryan,
I added that warning [1], and Joe’s right, it should have been at a WARN severity. However, it definitely isn’t blocking the access to the canvas (intentionally). Like Joe said, if you can provide a full stacktrace, and possibly your config files (redacting sensitive information as necessary), we can try to diagnose.
[1] https://github.com/apache/nifi/commit/744b15b4a7a7533ef81fc2333df0cd212c3779eb#diff-c12a63700e2b9a86823209f49e04dd04R216
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jan 24, 2019, at 9:38 AM, Ryan H <ry...@gmail.com> wrote:
>
> Hi Joe,
>
> Yes here are the only logs that I am seeing here as of now (I will probably turn on DEBUG levels to get more):
>
> ***nifi-app.log***
> 2019-01-24 17:32:51,583 ERROR [main] org.apache.nifi.encrypt.StringEncryptor ********************************************************************************
> 2019-01-24 17:32:51,586 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank sensitive properties key was provided *
> 2019-01-24 17:32:51,586 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * Specify a unique key in nifi.properties *
> 2019-01-24 17:32:51,586 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * for nifi.sensitive.props.key *
> 2019-01-24 17:32:51,586 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * *
> 2019-01-24 17:32:51,586 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config Tool in NiFi Toolkit can be used to *
> 2019-01-24 17:32:51,586 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * migrate the flow to the new key *
> 2019-01-24 17:32:51,586 ERROR [main] org.apache.nifi.encrypt.StringEncryptor ********************************************************************************
> 2019-01-24 17:32:53,283 ERROR [main] org.apache.nifi.encrypt.StringEncryptor ********************************************************************************
> 2019-01-24 17:32:53,284 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank sensitive properties key was provided *
> 2019-01-24 17:32:53,284 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * Specify a unique key in nifi.properties *
> 2019-01-24 17:32:53,284 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * for nifi.sensitive.props.key *
> 2019-01-24 17:32:53,284 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * *
> 2019-01-24 17:32:53,284 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config Tool in NiFi Toolkit can be used to *
> 2019-01-24 17:32:53,284 ERROR [main] org.apache.nifi.encrypt.StringEncryptor * migrate the flow to the new key *
> 2019-01-24 17:32:53,284 ERROR [main] org.apache.nifi.encrypt.StringEncryptor ********************************************************************************
> 2019-01-24 17:32:53,589 INFO [main] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@7ee45cbe finished recovering records. Performing Checkpoint to ensure proper state of Partitions before updates
> 2019-01-24 17:32:53,667 INFO [main] org.wali.MinimalLockingWriteAheadLog Successfully recovered 0 records in 81 milliseconds
> 2019-01-24 17:32:53,678 INFO [main] org.wali.MinimalLockingWriteAheadLog org.wali.MinimalLockingWriteAheadLog@7ee45cbe checkpointed with 0 Records and 0 Swap Files in 10 milliseconds (Stop-the-world time = 3 milliseconds, Clear Edit Logs time = 2 millis), max Transaction ID -1
> 2019-01-24 17:33:06,286 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl Starting
> 2019-01-24 17:33:06,410 INFO [main-EventThread] o.a.c.f.state.ConnectionStateManager State change: CONNECTED
> 2019-01-24 17:33:06,467 INFO [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl backgroundOperationsLoop exiting
> 2019-01-24 17:33:06,485 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl Starting
> 2019-01-24 17:33:06,501 INFO [main-EventThread] o.a.c.f.state.ConnectionStateManager State change: CONNECTED
>
> ***nifi-bootstrap.log***
> 2019-01-24 17:33:08,476 ERROR [NiFi logging handler] org.apache.nifi.StdErr Failed to start web server: Unable to start Flow Controller.
> 2019-01-24 17:33:08,479 ERROR [NiFi logging handler] org.apache.nifi.StdErr Shutting down...
>
>
> -Ryan H
>
> On Thu, Jan 24, 2019 at 11:48 AM Joe Witt <joe.witt@gmail.com <ma...@gmail.com>> wrote:
> ryan
>
> right...i think you are facing something else. We have locked down on some headers, etc.. They are mentioned in the migration guide.
>
> Can you share the logs from a full startup run?
>
> thanks
>
> On Thu, Jan 24, 2019, 11:21 AM Ryan H <ryan.howell.development@gmail.com <ma...@gmail.com> wrote:
> Hi Joe,
>
> Thanks for the reply. Agreed on the secure setup and we will definitely look to add value(s) for these properties. The issue we hit was that we weren't able to access the UI, and I was thinking that this error was preventing this. You think that this error shouldn't block accessing the canvas though?
>
> -Ryan
>
> On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <joe.witt@gmail.com <ma...@gmail.com>> wrote:
> Ryan,
>
> That block of text that shows up in the log could arguably said "WARN" because the flow will continue to function as it did before.
>
> However, the reason it is an error is that you really should follow its advice and specifically follow the secure nifi configuration guidance.
>
> By not following that you have a setup which is not secure.
>
> We're doing all we can as a community to move to 'secure by default' configurations which will take time. It requires improved tooling out of the box and we want the 'initial up and running experience' to be as smooth as possible and similar to how it works now.
>
> Anyway, hopefully that helps explain.
>
> Thanks
> Joe
>
> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <ryan.howell.development@gmail.com <ma...@gmail.com>> wrote:
> Hi All,
>
> We are currently in the process of upgrading from NiFi 1.5 to 1.8. After making the binary changes and restarting the cluster (a secure cluster setup), we are getting the following error:
>
> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank sensitive properties key was provided Specify a unique key in nifi.properties for nifi.sensitive.props.key
> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the flow to the new key.
>
> We are using all the same config that was in the 1.5 setup, including a blank key for nifi.sensitive.props.key which wasn't an issue before, but now it seems that it is. I didn't see this as a known issue in any of the migration guides or release notes. Can anyone provide any insight on this? Steps to remediate? Is the cause exactly what the error message says, having a blank value for this config prop?
>
>
> Cheers,
>
> Ryan H
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Joe Witt <jo...@gmail.com>.
cool - no worries. glad you're back on track.
On Thu, Jan 24, 2019 at 12:47 PM Ryan H <ry...@gmail.com>
wrote:
> Hey Joe,
>
> (As I smack my hand on my head) We had the log levels set to ERROR, which
> I forgot about. I set it back for more chatter and found the issue
> (completely unrelated to initial post) (and yes, a smoking gun). We can
> mark this issue as resolved as it has nothing to do with the initial error
> I thought it was. Thanks for the quick response and help!
>
> Cheers,
>
> Ryan H
>
> On Thu, Jan 24, 2019 at 12:41 PM Joe Witt <jo...@gmail.com> wrote:
>
>> Ryan,
>>
>> Got ya ... so bootstrap log seems to indicate badness. Can you please
>> share more of the nifi-app.log as there will almost certainly be a smoking
>> gun in there. You shouldn't have to enable to any special logging to see
>> what keeps it from starting.
>>
>> Thanks
>>
>> On Thu, Jan 24, 2019 at 12:38 PM Ryan H <
>> ryan.howell.development@gmail.com> wrote:
>>
>>> Hi Joe,
>>>
>>> Yes here are the only logs that I am seeing here as of now (I will
>>> probably turn on DEBUG levels to get more):
>>>
>>> ***nifi-app.log***
>>> 2019-01-24 17:32:51,583 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor
>>> ********************************************************************************
>>> 2019-01-24 17:32:51,586 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
>>> properties key was provided *
>>> 2019-01-24 17:32:51,586 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * Specify a
>>> unique key in nifi.properties *
>>> 2019-01-24 17:32:51,586 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * for
>>> nifi.sensitive.props.key *
>>> 2019-01-24 17:32:51,586 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor *
>>> *
>>> 2019-01-24 17:32:51,586 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
>>> Tool in NiFi Toolkit can be used to *
>>> 2019-01-24 17:32:51,586 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * migrate the
>>> flow to the new key *
>>> 2019-01-24 17:32:51,586 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor
>>> ********************************************************************************
>>> 2019-01-24 17:32:53,283 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor
>>> ********************************************************************************
>>> 2019-01-24 17:32:53,284 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
>>> properties key was provided *
>>> 2019-01-24 17:32:53,284 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * Specify a
>>> unique key in nifi.properties *
>>> 2019-01-24 17:32:53,284 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * for
>>> nifi.sensitive.props.key *
>>> 2019-01-24 17:32:53,284 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor *
>>> *
>>> 2019-01-24 17:32:53,284 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
>>> Tool in NiFi Toolkit can be used to *
>>> 2019-01-24 17:32:53,284 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor * migrate the
>>> flow to the new key *
>>> 2019-01-24 17:32:53,284 ERROR [main]
>>> org.apache.nifi.encrypt.StringEncryptor
>>> ********************************************************************************
>>> 2019-01-24 17:32:53,589 INFO [main] org.wali.MinimalLockingWriteAheadLog
>>> org.wali.MinimalLockingWriteAheadLog@7ee45cbe finished recovering
>>> records. Performing Checkpoint to ensure proper state of Partitions before
>>> updates
>>> 2019-01-24 17:32:53,667 INFO [main] org.wali.MinimalLockingWriteAheadLog
>>> Successfully recovered 0 records in 81 milliseconds
>>> 2019-01-24 17:32:53,678 INFO [main] org.wali.MinimalLockingWriteAheadLog
>>> org.wali.MinimalLockingWriteAheadLog@7ee45cbe checkpointed with 0
>>> Records and 0 Swap Files in 10 milliseconds (Stop-the-world time = 3
>>> milliseconds, Clear Edit Logs time = 2 millis), max Transaction ID -1
>>> 2019-01-24 17:33:06,286 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
>>> Starting
>>> 2019-01-24 17:33:06,410 INFO [main-EventThread]
>>> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
>>> 2019-01-24 17:33:06,467 INFO [Curator-Framework-0]
>>> o.a.c.f.imps.CuratorFrameworkImpl backgroundOperationsLoop exiting
>>> 2019-01-24 17:33:06,485 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
>>> Starting
>>> 2019-01-24 17:33:06,501 INFO [main-EventThread]
>>> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
>>>
>>> ***nifi-bootstrap.log***
>>> 2019-01-24 17:33:08,476 ERROR [NiFi logging handler]
>>> org.apache.nifi.StdErr Failed to start web server: Unable to start Flow
>>> Controller.
>>> 2019-01-24 17:33:08,479 ERROR [NiFi logging handler]
>>> org.apache.nifi.StdErr Shutting down...
>>>
>>>
>>> -Ryan H
>>>
>>> On Thu, Jan 24, 2019 at 11:48 AM Joe Witt <jo...@gmail.com> wrote:
>>>
>>>> ryan
>>>>
>>>> right...i think you are facing something else. We have locked down on
>>>> some headers, etc.. They are mentioned in the migration guide.
>>>>
>>>> Can you share the logs from a full startup run?
>>>>
>>>> thanks
>>>>
>>>> On Thu, Jan 24, 2019, 11:21 AM Ryan H <
>>>> ryan.howell.development@gmail.com wrote:
>>>>
>>>>> Hi Joe,
>>>>>
>>>>> Thanks for the reply. Agreed on the secure setup and we will
>>>>> definitely look to add value(s) for these properties. The issue we hit was
>>>>> that we weren't able to access the UI, and I was thinking that this error
>>>>> was preventing this. You think that this error shouldn't block accessing
>>>>> the canvas though?
>>>>>
>>>>> -Ryan
>>>>>
>>>>> On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <jo...@gmail.com> wrote:
>>>>>
>>>>>> Ryan,
>>>>>>
>>>>>> That block of text that shows up in the log could arguably said
>>>>>> "WARN" because the flow will continue to function as it did before.
>>>>>>
>>>>>> However, the reason it is an error is that you really should follow
>>>>>> its advice and specifically follow the secure nifi configuration guidance.
>>>>>>
>>>>>> By not following that you have a setup which is not secure.
>>>>>>
>>>>>> We're doing all we can as a community to move to 'secure by default'
>>>>>> configurations which will take time. It requires improved tooling out of
>>>>>> the box and we want the 'initial up and running experience' to be as smooth
>>>>>> as possible and similar to how it works now.
>>>>>>
>>>>>> Anyway, hopefully that helps explain.
>>>>>>
>>>>>> Thanks
>>>>>> Joe
>>>>>>
>>>>>> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <
>>>>>> ryan.howell.development@gmail.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> We are currently in the process of upgrading from NiFi 1.5 to 1.8.
>>>>>>> After making the binary changes and restarting the cluster (a secure
>>>>>>> cluster setup), we are getting the following error:
>>>>>>>
>>>>>>> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank
>>>>>>> sensitive properties key was provided Specify a unique key in
>>>>>>> nifi.properties for nifi.sensitive.props.key
>>>>>>> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the
>>>>>>> flow to the new key.
>>>>>>>
>>>>>>> We are using all the same config that was in the 1.5 setup,
>>>>>>> including a blank key for nifi.sensitive.props.key which wasn't an issue
>>>>>>> before, but now it seems that it is. I didn't see this as a known issue in
>>>>>>> any of the migration guides or release notes. Can anyone provide any
>>>>>>> insight on this? Steps to remediate? Is the cause exactly what the error
>>>>>>> message says, having a blank value for this config prop?
>>>>>>>
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Ryan H
>>>>>>>
>>>>>>
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Ryan H <ry...@gmail.com>.
Hey Joe,
(As I smack my hand on my head) We had the log levels set to ERROR, which I
forgot about. I set it back for more chatter and found the issue
(completely unrelated to initial post) (and yes, a smoking gun). We can
mark this issue as resolved as it has nothing to do with the initial error
I thought it was. Thanks for the quick response and help!
Cheers,
Ryan H
On Thu, Jan 24, 2019 at 12:41 PM Joe Witt <jo...@gmail.com> wrote:
> Ryan,
>
> Got ya ... so bootstrap log seems to indicate badness. Can you please
> share more of the nifi-app.log as there will almost certainly be a smoking
> gun in there. You shouldn't have to enable to any special logging to see
> what keeps it from starting.
>
> Thanks
>
> On Thu, Jan 24, 2019 at 12:38 PM Ryan H <ry...@gmail.com>
> wrote:
>
>> Hi Joe,
>>
>> Yes here are the only logs that I am seeing here as of now (I will
>> probably turn on DEBUG levels to get more):
>>
>> ***nifi-app.log***
>> 2019-01-24 17:32:51,583 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor
>> ********************************************************************************
>> 2019-01-24 17:32:51,586 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
>> properties key was provided *
>> 2019-01-24 17:32:51,586 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * Specify a
>> unique key in nifi.properties *
>> 2019-01-24 17:32:51,586 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * for
>> nifi.sensitive.props.key *
>> 2019-01-24 17:32:51,586 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor *
>> *
>> 2019-01-24 17:32:51,586 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
>> Tool in NiFi Toolkit can be used to *
>> 2019-01-24 17:32:51,586 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * migrate the
>> flow to the new key *
>> 2019-01-24 17:32:51,586 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor
>> ********************************************************************************
>> 2019-01-24 17:32:53,283 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor
>> ********************************************************************************
>> 2019-01-24 17:32:53,284 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
>> properties key was provided *
>> 2019-01-24 17:32:53,284 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * Specify a
>> unique key in nifi.properties *
>> 2019-01-24 17:32:53,284 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * for
>> nifi.sensitive.props.key *
>> 2019-01-24 17:32:53,284 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor *
>> *
>> 2019-01-24 17:32:53,284 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
>> Tool in NiFi Toolkit can be used to *
>> 2019-01-24 17:32:53,284 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor * migrate the
>> flow to the new key *
>> 2019-01-24 17:32:53,284 ERROR [main]
>> org.apache.nifi.encrypt.StringEncryptor
>> ********************************************************************************
>> 2019-01-24 17:32:53,589 INFO [main] org.wali.MinimalLockingWriteAheadLog
>> org.wali.MinimalLockingWriteAheadLog@7ee45cbe finished recovering
>> records. Performing Checkpoint to ensure proper state of Partitions before
>> updates
>> 2019-01-24 17:32:53,667 INFO [main] org.wali.MinimalLockingWriteAheadLog
>> Successfully recovered 0 records in 81 milliseconds
>> 2019-01-24 17:32:53,678 INFO [main] org.wali.MinimalLockingWriteAheadLog
>> org.wali.MinimalLockingWriteAheadLog@7ee45cbe checkpointed with 0
>> Records and 0 Swap Files in 10 milliseconds (Stop-the-world time = 3
>> milliseconds, Clear Edit Logs time = 2 millis), max Transaction ID -1
>> 2019-01-24 17:33:06,286 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
>> Starting
>> 2019-01-24 17:33:06,410 INFO [main-EventThread]
>> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
>> 2019-01-24 17:33:06,467 INFO [Curator-Framework-0]
>> o.a.c.f.imps.CuratorFrameworkImpl backgroundOperationsLoop exiting
>> 2019-01-24 17:33:06,485 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
>> Starting
>> 2019-01-24 17:33:06,501 INFO [main-EventThread]
>> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
>>
>> ***nifi-bootstrap.log***
>> 2019-01-24 17:33:08,476 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Failed to start web server: Unable to start Flow
>> Controller.
>> 2019-01-24 17:33:08,479 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Shutting down...
>>
>>
>> -Ryan H
>>
>> On Thu, Jan 24, 2019 at 11:48 AM Joe Witt <jo...@gmail.com> wrote:
>>
>>> ryan
>>>
>>> right...i think you are facing something else. We have locked down on
>>> some headers, etc.. They are mentioned in the migration guide.
>>>
>>> Can you share the logs from a full startup run?
>>>
>>> thanks
>>>
>>> On Thu, Jan 24, 2019, 11:21 AM Ryan H <ryan.howell.development@gmail.com
>>> wrote:
>>>
>>>> Hi Joe,
>>>>
>>>> Thanks for the reply. Agreed on the secure setup and we will definitely
>>>> look to add value(s) for these properties. The issue we hit was that we
>>>> weren't able to access the UI, and I was thinking that this error was
>>>> preventing this. You think that this error shouldn't block accessing the
>>>> canvas though?
>>>>
>>>> -Ryan
>>>>
>>>> On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <jo...@gmail.com> wrote:
>>>>
>>>>> Ryan,
>>>>>
>>>>> That block of text that shows up in the log could arguably said "WARN"
>>>>> because the flow will continue to function as it did before.
>>>>>
>>>>> However, the reason it is an error is that you really should follow
>>>>> its advice and specifically follow the secure nifi configuration guidance.
>>>>>
>>>>> By not following that you have a setup which is not secure.
>>>>>
>>>>> We're doing all we can as a community to move to 'secure by default'
>>>>> configurations which will take time. It requires improved tooling out of
>>>>> the box and we want the 'initial up and running experience' to be as smooth
>>>>> as possible and similar to how it works now.
>>>>>
>>>>> Anyway, hopefully that helps explain.
>>>>>
>>>>> Thanks
>>>>> Joe
>>>>>
>>>>> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <
>>>>> ryan.howell.development@gmail.com> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> We are currently in the process of upgrading from NiFi 1.5 to 1.8.
>>>>>> After making the binary changes and restarting the cluster (a secure
>>>>>> cluster setup), we are getting the following error:
>>>>>>
>>>>>> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank
>>>>>> sensitive properties key was provided Specify a unique key in
>>>>>> nifi.properties for nifi.sensitive.props.key
>>>>>> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the
>>>>>> flow to the new key.
>>>>>>
>>>>>> We are using all the same config that was in the 1.5 setup, including
>>>>>> a blank key for nifi.sensitive.props.key which wasn't an issue before, but
>>>>>> now it seems that it is. I didn't see this as a known issue in any of the
>>>>>> migration guides or release notes. Can anyone provide any insight on this?
>>>>>> Steps to remediate? Is the cause exactly what the error message says,
>>>>>> having a blank value for this config prop?
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Ryan H
>>>>>>
>>>>>
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Joe Witt <jo...@gmail.com>.
Ryan,
Got ya ... so bootstrap log seems to indicate badness. Can you please
share more of the nifi-app.log as there will almost certainly be a smoking
gun in there. You shouldn't have to enable to any special logging to see
what keeps it from starting.
Thanks
On Thu, Jan 24, 2019 at 12:38 PM Ryan H <ry...@gmail.com>
wrote:
> Hi Joe,
>
> Yes here are the only logs that I am seeing here as of now (I will
> probably turn on DEBUG levels to get more):
>
> ***nifi-app.log***
> 2019-01-24 17:32:51,583 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
> properties key was provided *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * Specify a
> unique key in nifi.properties *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * for
> nifi.sensitive.props.key *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor *
> *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
> Tool in NiFi Toolkit can be used to *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * migrate the
> flow to the new key *
> 2019-01-24 17:32:51,586 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:53,283 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
> properties key was provided *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * Specify a
> unique key in nifi.properties *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * for
> nifi.sensitive.props.key *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor *
> *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
> Tool in NiFi Toolkit can be used to *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor * migrate the
> flow to the new key *
> 2019-01-24 17:32:53,284 ERROR [main]
> org.apache.nifi.encrypt.StringEncryptor
> ********************************************************************************
> 2019-01-24 17:32:53,589 INFO [main] org.wali.MinimalLockingWriteAheadLog
> org.wali.MinimalLockingWriteAheadLog@7ee45cbe finished recovering
> records. Performing Checkpoint to ensure proper state of Partitions before
> updates
> 2019-01-24 17:32:53,667 INFO [main] org.wali.MinimalLockingWriteAheadLog
> Successfully recovered 0 records in 81 milliseconds
> 2019-01-24 17:32:53,678 INFO [main] org.wali.MinimalLockingWriteAheadLog
> org.wali.MinimalLockingWriteAheadLog@7ee45cbe checkpointed with 0 Records
> and 0 Swap Files in 10 milliseconds (Stop-the-world time = 3 milliseconds,
> Clear Edit Logs time = 2 millis), max Transaction ID -1
> 2019-01-24 17:33:06,286 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
> Starting
> 2019-01-24 17:33:06,410 INFO [main-EventThread]
> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
> 2019-01-24 17:33:06,467 INFO [Curator-Framework-0]
> o.a.c.f.imps.CuratorFrameworkImpl backgroundOperationsLoop exiting
> 2019-01-24 17:33:06,485 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
> Starting
> 2019-01-24 17:33:06,501 INFO [main-EventThread]
> o.a.c.f.state.ConnectionStateManager State change: CONNECTED
>
> ***nifi-bootstrap.log***
> 2019-01-24 17:33:08,476 ERROR [NiFi logging handler]
> org.apache.nifi.StdErr Failed to start web server: Unable to start Flow
> Controller.
> 2019-01-24 17:33:08,479 ERROR [NiFi logging handler]
> org.apache.nifi.StdErr Shutting down...
>
>
> -Ryan H
>
> On Thu, Jan 24, 2019 at 11:48 AM Joe Witt <jo...@gmail.com> wrote:
>
>> ryan
>>
>> right...i think you are facing something else. We have locked down on
>> some headers, etc.. They are mentioned in the migration guide.
>>
>> Can you share the logs from a full startup run?
>>
>> thanks
>>
>> On Thu, Jan 24, 2019, 11:21 AM Ryan H <ryan.howell.development@gmail.com
>> wrote:
>>
>>> Hi Joe,
>>>
>>> Thanks for the reply. Agreed on the secure setup and we will definitely
>>> look to add value(s) for these properties. The issue we hit was that we
>>> weren't able to access the UI, and I was thinking that this error was
>>> preventing this. You think that this error shouldn't block accessing the
>>> canvas though?
>>>
>>> -Ryan
>>>
>>> On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <jo...@gmail.com> wrote:
>>>
>>>> Ryan,
>>>>
>>>> That block of text that shows up in the log could arguably said "WARN"
>>>> because the flow will continue to function as it did before.
>>>>
>>>> However, the reason it is an error is that you really should follow its
>>>> advice and specifically follow the secure nifi configuration guidance.
>>>>
>>>> By not following that you have a setup which is not secure.
>>>>
>>>> We're doing all we can as a community to move to 'secure by default'
>>>> configurations which will take time. It requires improved tooling out of
>>>> the box and we want the 'initial up and running experience' to be as smooth
>>>> as possible and similar to how it works now.
>>>>
>>>> Anyway, hopefully that helps explain.
>>>>
>>>> Thanks
>>>> Joe
>>>>
>>>> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <
>>>> ryan.howell.development@gmail.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> We are currently in the process of upgrading from NiFi 1.5 to 1.8.
>>>>> After making the binary changes and restarting the cluster (a secure
>>>>> cluster setup), we are getting the following error:
>>>>>
>>>>> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank
>>>>> sensitive properties key was provided Specify a unique key in
>>>>> nifi.properties for nifi.sensitive.props.key
>>>>> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the
>>>>> flow to the new key.
>>>>>
>>>>> We are using all the same config that was in the 1.5 setup, including
>>>>> a blank key for nifi.sensitive.props.key which wasn't an issue before, but
>>>>> now it seems that it is. I didn't see this as a known issue in any of the
>>>>> migration guides or release notes. Can anyone provide any insight on this?
>>>>> Steps to remediate? Is the cause exactly what the error message says,
>>>>> having a blank value for this config prop?
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Ryan H
>>>>>
>>>>
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Ryan H <ry...@gmail.com>.
Hi Joe,
Yes here are the only logs that I am seeing here as of now (I will probably
turn on DEBUG levels to get more):
***nifi-app.log***
2019-01-24 17:32:51,583 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor
********************************************************************************
2019-01-24 17:32:51,586 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
properties key was provided *
2019-01-24 17:32:51,586 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * Specify a
unique key in nifi.properties *
2019-01-24 17:32:51,586 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * for
nifi.sensitive.props.key *
2019-01-24 17:32:51,586 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor *
*
2019-01-24 17:32:51,586 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
Tool in NiFi Toolkit can be used to *
2019-01-24 17:32:51,586 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * migrate the
flow to the new key *
2019-01-24 17:32:51,586 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor
********************************************************************************
2019-01-24 17:32:53,283 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor
********************************************************************************
2019-01-24 17:32:53,284 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
properties key was provided *
2019-01-24 17:32:53,284 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * Specify a
unique key in nifi.properties *
2019-01-24 17:32:53,284 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * for
nifi.sensitive.props.key *
2019-01-24 17:32:53,284 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor *
*
2019-01-24 17:32:53,284 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * The Encrypt Config
Tool in NiFi Toolkit can be used to *
2019-01-24 17:32:53,284 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor * migrate the
flow to the new key *
2019-01-24 17:32:53,284 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor
********************************************************************************
2019-01-24 17:32:53,589 INFO [main] org.wali.MinimalLockingWriteAheadLog
org.wali.MinimalLockingWriteAheadLog@7ee45cbe finished recovering records.
Performing Checkpoint to ensure proper state of Partitions before updates
2019-01-24 17:32:53,667 INFO [main] org.wali.MinimalLockingWriteAheadLog
Successfully recovered 0 records in 81 milliseconds
2019-01-24 17:32:53,678 INFO [main] org.wali.MinimalLockingWriteAheadLog
org.wali.MinimalLockingWriteAheadLog@7ee45cbe checkpointed with 0 Records
and 0 Swap Files in 10 milliseconds (Stop-the-world time = 3 milliseconds,
Clear Edit Logs time = 2 millis), max Transaction ID -1
2019-01-24 17:33:06,286 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
Starting
2019-01-24 17:33:06,410 INFO [main-EventThread]
o.a.c.f.state.ConnectionStateManager State change: CONNECTED
2019-01-24 17:33:06,467 INFO [Curator-Framework-0]
o.a.c.f.imps.CuratorFrameworkImpl backgroundOperationsLoop exiting
2019-01-24 17:33:06,485 INFO [main] o.a.c.f.imps.CuratorFrameworkImpl
Starting
2019-01-24 17:33:06,501 INFO [main-EventThread]
o.a.c.f.state.ConnectionStateManager State change: CONNECTED
***nifi-bootstrap.log***
2019-01-24 17:33:08,476 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Failed to start web server: Unable to start Flow Controller.
2019-01-24 17:33:08,479 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Shutting down...
-Ryan H
On Thu, Jan 24, 2019 at 11:48 AM Joe Witt <jo...@gmail.com> wrote:
> ryan
>
> right...i think you are facing something else. We have locked down on
> some headers, etc.. They are mentioned in the migration guide.
>
> Can you share the logs from a full startup run?
>
> thanks
>
> On Thu, Jan 24, 2019, 11:21 AM Ryan H <ryan.howell.development@gmail.com
> wrote:
>
>> Hi Joe,
>>
>> Thanks for the reply. Agreed on the secure setup and we will definitely
>> look to add value(s) for these properties. The issue we hit was that we
>> weren't able to access the UI, and I was thinking that this error was
>> preventing this. You think that this error shouldn't block accessing the
>> canvas though?
>>
>> -Ryan
>>
>> On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <jo...@gmail.com> wrote:
>>
>>> Ryan,
>>>
>>> That block of text that shows up in the log could arguably said "WARN"
>>> because the flow will continue to function as it did before.
>>>
>>> However, the reason it is an error is that you really should follow its
>>> advice and specifically follow the secure nifi configuration guidance.
>>>
>>> By not following that you have a setup which is not secure.
>>>
>>> We're doing all we can as a community to move to 'secure by default'
>>> configurations which will take time. It requires improved tooling out of
>>> the box and we want the 'initial up and running experience' to be as smooth
>>> as possible and similar to how it works now.
>>>
>>> Anyway, hopefully that helps explain.
>>>
>>> Thanks
>>> Joe
>>>
>>> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <
>>> ryan.howell.development@gmail.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We are currently in the process of upgrading from NiFi 1.5 to 1.8.
>>>> After making the binary changes and restarting the cluster (a secure
>>>> cluster setup), we are getting the following error:
>>>>
>>>> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank
>>>> sensitive properties key was provided Specify a unique key in
>>>> nifi.properties for nifi.sensitive.props.key
>>>> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the flow
>>>> to the new key.
>>>>
>>>> We are using all the same config that was in the 1.5 setup, including a
>>>> blank key for nifi.sensitive.props.key which wasn't an issue before, but
>>>> now it seems that it is. I didn't see this as a known issue in any of the
>>>> migration guides or release notes. Can anyone provide any insight on this?
>>>> Steps to remediate? Is the cause exactly what the error message says,
>>>> having a blank value for this config prop?
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Ryan H
>>>>
>>>
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Joe Witt <jo...@gmail.com>.
ryan
right...i think you are facing something else. We have locked down on some
headers, etc.. They are mentioned in the migration guide.
Can you share the logs from a full startup run?
thanks
On Thu, Jan 24, 2019, 11:21 AM Ryan H <ryan.howell.development@gmail.com
wrote:
> Hi Joe,
>
> Thanks for the reply. Agreed on the secure setup and we will definitely
> look to add value(s) for these properties. The issue we hit was that we
> weren't able to access the UI, and I was thinking that this error was
> preventing this. You think that this error shouldn't block accessing the
> canvas though?
>
> -Ryan
>
> On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <jo...@gmail.com> wrote:
>
>> Ryan,
>>
>> That block of text that shows up in the log could arguably said "WARN"
>> because the flow will continue to function as it did before.
>>
>> However, the reason it is an error is that you really should follow its
>> advice and specifically follow the secure nifi configuration guidance.
>>
>> By not following that you have a setup which is not secure.
>>
>> We're doing all we can as a community to move to 'secure by default'
>> configurations which will take time. It requires improved tooling out of
>> the box and we want the 'initial up and running experience' to be as smooth
>> as possible and similar to how it works now.
>>
>> Anyway, hopefully that helps explain.
>>
>> Thanks
>> Joe
>>
>> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <
>> ryan.howell.development@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We are currently in the process of upgrading from NiFi 1.5 to 1.8. After
>>> making the binary changes and restarting the cluster (a secure cluster
>>> setup), we are getting the following error:
>>>
>>> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank
>>> sensitive properties key was provided Specify a unique key in
>>> nifi.properties for nifi.sensitive.props.key
>>> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the flow
>>> to the new key.
>>>
>>> We are using all the same config that was in the 1.5 setup, including a
>>> blank key for nifi.sensitive.props.key which wasn't an issue before, but
>>> now it seems that it is. I didn't see this as a known issue in any of the
>>> migration guides or release notes. Can anyone provide any insight on this?
>>> Steps to remediate? Is the cause exactly what the error message says,
>>> having a blank value for this config prop?
>>>
>>>
>>> Cheers,
>>>
>>> Ryan H
>>>
>>
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Ryan H <ry...@gmail.com>.
Hi Joe,
Thanks for the reply. Agreed on the secure setup and we will definitely
look to add value(s) for these properties. The issue we hit was that we
weren't able to access the UI, and I was thinking that this error was
preventing this. You think that this error shouldn't block accessing the
canvas though?
-Ryan
On Thu, Jan 24, 2019 at 10:39 AM Joe Witt <jo...@gmail.com> wrote:
> Ryan,
>
> That block of text that shows up in the log could arguably said "WARN"
> because the flow will continue to function as it did before.
>
> However, the reason it is an error is that you really should follow its
> advice and specifically follow the secure nifi configuration guidance.
>
> By not following that you have a setup which is not secure.
>
> We're doing all we can as a community to move to 'secure by default'
> configurations which will take time. It requires improved tooling out of
> the box and we want the 'initial up and running experience' to be as smooth
> as possible and similar to how it works now.
>
> Anyway, hopefully that helps explain.
>
> Thanks
> Joe
>
> On Thu, Jan 24, 2019 at 10:11 AM Ryan H <ry...@gmail.com>
> wrote:
>
>> Hi All,
>>
>> We are currently in the process of upgrading from NiFi 1.5 to 1.8. After
>> making the binary changes and restarting the cluster (a secure cluster
>> setup), we are getting the following error:
>>
>> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
>> properties key was provided Specify a unique key in nifi.properties for
>> nifi.sensitive.props.key
>> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the flow
>> to the new key.
>>
>> We are using all the same config that was in the 1.5 setup, including a
>> blank key for nifi.sensitive.props.key which wasn't an issue before, but
>> now it seems that it is. I didn't see this as a known issue in any of the
>> migration guides or release notes. Can anyone provide any insight on this?
>> Steps to remediate? Is the cause exactly what the error message says,
>> having a blank value for this config prop?
>>
>>
>> Cheers,
>>
>> Ryan H
>>
>
Re: Migrate NiFi 1.5 to 1.8 Error - A Blank Sensitive Properties Key
Was Provided
Posted by Joe Witt <jo...@gmail.com>.
Ryan,
That block of text that shows up in the log could arguably said "WARN"
because the flow will continue to function as it did before.
However, the reason it is an error is that you really should follow its
advice and specifically follow the secure nifi configuration guidance.
By not following that you have a setup which is not secure.
We're doing all we can as a community to move to 'secure by default'
configurations which will take time. It requires improved tooling out of
the box and we want the 'initial up and running experience' to be as smooth
as possible and similar to how it works now.
Anyway, hopefully that helps explain.
Thanks
Joe
On Thu, Jan 24, 2019 at 10:11 AM Ryan H <ry...@gmail.com>
wrote:
> Hi All,
>
> We are currently in the process of upgrading from NiFi 1.5 to 1.8. After
> making the binary changes and restarting the cluster (a secure cluster
> setup), we are getting the following error:
>
> ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
> properties key was provided Specify a unique key in nifi.properties for
> nifi.sensitive.props.key
> The Encrypt Config Tool in NiFi Toolkit can be used to migrate the flow to
> the new key.
>
> We are using all the same config that was in the 1.5 setup, including a
> blank key for nifi.sensitive.props.key which wasn't an issue before, but
> now it seems that it is. I didn't see this as a known issue in any of the
> migration guides or release notes. Can anyone provide any insight on this?
> Steps to remediate? Is the cause exactly what the error message says,
> having a blank value for this config prop?
>
>
> Cheers,
>
> Ryan H
>