[jira] [Updated] (NIFI-6980) NiFi can't use symlinks for some conf files
[ https://issues.apache.org/jira/browse/NIFI-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Sevener updated NIFI-6980: Affects Version/s: 1.11.4 1.12.1 > NiFi can't use symlinks for some conf files > --- > > Key: NIFI-6980 > URL: https://issues.apache.org/jira/browse/NIFI-6980 > Project: Apache NiFi > Issue Type: Bug > Components: Docker >Affects Versions: 1.10.0, 1.9.2, 1.11.4, 1.12.1 > Environment: Tested with docker, though this probably affects other > environments as well. >Reporter: James Sevener >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > Some files lend themselves to being ephemeral instead of persistent, but live > in the conf directory. Logback.xml is a great example, and moving the file to > the container and then symlinking works. This doesn't work for any files that > the various sh scripts call the prop_replace function in common.sh as the sed > call doesn't include --follow-symlinks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7084) Upgrade from 1.10 to 1.11 fails
[ https://issues.apache.org/jira/browse/NIFI-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029005#comment-17029005 ] James Sevener commented on NIFI-7084: - My configuration is based on this: [https://github.com/apache/nifi/blob/master/nifi-docker/dockerhub/Dockerfile] I've added more to support my environment, but this is the basis. > Upgrade from 1.10 to 1.11 fails > --- > > Key: NIFI-7084 > URL: https://issues.apache.org/jira/browse/NIFI-7084 > Project: Apache NiFi > Issue Type: Bug > Components: Docker >Affects Versions: 1.10.0, 1.11.0 > Environment: Docker version 19.03.2 > NiFi 1.10.0 and NiFi 1.11.0 >Reporter: James Sevener >Priority: Major > Attachments: nifi.1.11.stacktrace > > > Spun up a fresh NiFi 1.10 instance and created an InvokeHTTP processor, then > SSL context service. Then upgraded the instance from 1.10.0 to 1.11.0 and get > the following error. > Caused by: java.lang.IllegalStateException: > org.apache.nifi.ssl.StandardRestrictedSSLContextService from > org.apache.nifi:nifi-ssl-context-service-nar:1.10.0 is not known to this NiFi > instance. > > Attached is the full stack trace from the error to the instance shutdown. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7084) Upgrade from 1.10 to 1.11 fails
[ https://issues.apache.org/jira/browse/NIFI-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027020#comment-17027020 ] James Sevener commented on NIFI-7084: - conf is a volume, so the data is persistent. > Upgrade from 1.10 to 1.11 fails > --- > > Key: NIFI-7084 > URL: https://issues.apache.org/jira/browse/NIFI-7084 > Project: Apache NiFi > Issue Type: Bug > Components: Docker >Affects Versions: 1.10.0, 1.11.0 > Environment: Docker version 19.03.2 > NiFi 1.10.0 and NiFi 1.11.0 >Reporter: James Sevener >Priority: Major > Attachments: nifi.1.11.stacktrace > > > Spun up a fresh NiFi 1.10 instance and created an InvokeHTTP processor, then > SSL context service. Then upgraded the instance from 1.10.0 to 1.11.0 and get > the following error. > Caused by: java.lang.IllegalStateException: > org.apache.nifi.ssl.StandardRestrictedSSLContextService from > org.apache.nifi:nifi-ssl-context-service-nar:1.10.0 is not known to this NiFi > instance. > > Attached is the full stack trace from the error to the instance shutdown. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7084) Upgrade from 1.10 to 1.11 fails
[ https://issues.apache.org/jira/browse/NIFI-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026963#comment-17026963 ] James Sevener commented on NIFI-7084: - Hey Andrew, I redeployed my Docker stack using an updated image (1.11.0) So the flow.xml.gz is still in the conf directory. I have not tried it outside of docker, as that is where my current focus is. The SSL context was created at the Process Group level, and the InvokeHTTP Processor is referencing the SSL context service. Also of note, I've upgraded from 1.9.2 to 1.10 this same way without issue, however I can not downgrade from 1.10 to 1.9.2 without the same error. > Upgrade from 1.10 to 1.11 fails > --- > > Key: NIFI-7084 > URL: https://issues.apache.org/jira/browse/NIFI-7084 > Project: Apache NiFi > Issue Type: Bug > Components: Docker >Affects Versions: 1.10.0, 1.11.0 > Environment: Docker version 19.03.2 > NiFi 1.10.0 and NiFi 1.11.0 >Reporter: James Sevener >Priority: Major > Attachments: nifi.1.11.stacktrace > > > Spun up a fresh NiFi 1.10 instance and created an InvokeHTTP processor, then > SSL context service. Then upgraded the instance from 1.10.0 to 1.11.0 and get > the following error. > Caused by: java.lang.IllegalStateException: > org.apache.nifi.ssl.StandardRestrictedSSLContextService from > org.apache.nifi:nifi-ssl-context-service-nar:1.10.0 is not known to this NiFi > instance. > > Attached is the full stack trace from the error to the instance shutdown. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7084) Upgrade from 1.10 to 1.11 fails
James Sevener created NIFI-7084: --- Summary: Upgrade from 1.10 to 1.11 fails Key: NIFI-7084 URL: https://issues.apache.org/jira/browse/NIFI-7084 Project: Apache NiFi Issue Type: Bug Components: Docker Affects Versions: 1.11.0, 1.10.0 Environment: Docker version 19.03.2 NiFi 1.10.0 and NiFi 1.11.0 Reporter: James Sevener Attachments: nifi.1.11.stacktrace Spun up a fresh NiFi 1.10 instance and created an InvokeHTTP processor, then SSL context service. Then upgraded the instance from 1.10.0 to 1.11.0 and get the following error. Caused by: java.lang.IllegalStateException: org.apache.nifi.ssl.StandardRestrictedSSLContextService from org.apache.nifi:nifi-ssl-context-service-nar:1.10.0 is not known to this NiFi instance. Attached is the full stack trace from the error to the instance shutdown. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6980) NiFi can't use symlinks for some conf files
James Sevener created NIFI-6980: --- Summary: NiFi can't use symlinks for some conf files Key: NIFI-6980 URL: https://issues.apache.org/jira/browse/NIFI-6980 Project: Apache NiFi Issue Type: Bug Components: Docker Affects Versions: 1.9.2, 1.10.0 Environment: Tested with docker, though this probably affects other environments as well. Reporter: James Sevener Some files lend themselves to being ephemeral instead of persistent, but live in the conf directory. Logback.xml is a great example, and moving the file to the container and then symlinking works. This doesn't work for any files that the various sh scripts call the prop_replace function in common.sh as the sed call doesn't include --follow-symlinks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6667) Nifi Docker doesn't have a way to set sensitive props key
James Sevener created NIFI-6667:
---
Summary: Nifi Docker doesn't have a way to set sensitive props key
Key: NIFI-6667
URL: https://issues.apache.org/jira/browse/NIFI-6667
Project: Apache NiFi
Issue Type: Improvement
Components: Docker
Affects Versions: 1.9.2
Reporter: James Sevener
secure.sh doesn't accept a variable to set sensitive props key.
Something like to following works.
{code:java}
: ${SENSITIVE_PROPS_KEY:?"Must specify an encryption passphrase to be used for
sensitive properties."}
prop_replace 'nifi.sensitive.props.key'
"${SENSITIVE_PROPS_KEY}"{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (NIFI-6609) NiFi Docker can't load some JAR files
[
https://issues.apache.org/jira/browse/NIFI-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927714#comment-16927714
]
James Sevener edited comment on NIFI-6609 at 9/11/19 3:58 PM:
--
Changing
{code:java}
"${NIFI_HOME}/bin/nifi.sh" run &
{code}
to
{code:java}
"${NIFI_HOME}/bin/nifi.sh" start
{code}
in the start.sh file fixes this
was (Author: jamessevener):
Changing `"${NIFI_HOME}/bin/nifi.sh" run &` to `"${NIFI_HOME}/bin/nifi.sh"
start` in the start.sh file fixes this
> NiFi Docker can't load some JAR files
> -
>
> Key: NIFI-6609
> URL: https://issues.apache.org/jira/browse/NIFI-6609
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
>Affects Versions: 1.9.2
> Environment: Docker (tested on Docker Desktop, Windows)
>Reporter: James Sevener
>Priority: Minor
>
> When adding the Splunk Java Logging JAR and dependencies, and introducing the
> appender to the logback.xml config, a ClassNotFound error is produced. This
> config and JARs were pulled directly from a working instance of NiFi running
> on RHEL. Also, a workaround is to set the entry point to /bin/bash and then
> run ./bin/nifi.sh. This then successfully starts and sends logs to Splunk.
>
> Reproduceable by building the dockerfile here:
> [https://github.com/jamessevener/nifi/tree/master/nifi-docker/dockerhub]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (NIFI-6609) NiFi Docker can't load some JAR files
[
https://issues.apache.org/jira/browse/NIFI-6609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927714#comment-16927714
]
James Sevener commented on NIFI-6609:
-
Changing `"${NIFI_HOME}/bin/nifi.sh" run &` to `"${NIFI_HOME}/bin/nifi.sh"
start` in the start.sh file fixes this
> NiFi Docker can't load some JAR files
> -
>
> Key: NIFI-6609
> URL: https://issues.apache.org/jira/browse/NIFI-6609
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
>Affects Versions: 1.9.2
> Environment: Docker (tested on Docker Desktop, Windows)
>Reporter: James Sevener
>Priority: Minor
>
> When adding the Splunk Java Logging JAR and dependencies, and introducing the
> appender to the logback.xml config, a ClassNotFound error is produced. This
> config and JARs were pulled directly from a working instance of NiFi running
> on RHEL. Also, a workaround is to set the entry point to /bin/bash and then
> run ./bin/nifi.sh. This then successfully starts and sends logs to Splunk.
>
> Reproduceable by building the dockerfile here:
> [https://github.com/jamessevener/nifi/tree/master/nifi-docker/dockerhub]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (NIFI-6609) NiFi Docker can't load some JAR files
James Sevener created NIFI-6609: --- Summary: NiFi Docker can't load some JAR files Key: NIFI-6609 URL: https://issues.apache.org/jira/browse/NIFI-6609 Project: Apache NiFi Issue Type: Bug Components: Docker Affects Versions: 1.9.2 Environment: Docker (tested on Docker Desktop, Windows) Reporter: James Sevener When adding the Splunk Java Logging JAR and dependencies, and introducing the appender to the logback.xml config, a ClassNotFound error is produced. This config and JARs were pulled directly from a working instance of NiFi running on RHEL. Also, a workaround is to set the entry point to /bin/bash and then run ./bin/nifi.sh. This then successfully starts and sends logs to Splunk. Reproduceable by building the dockerfile here: [https://github.com/jamessevener/nifi/tree/master/nifi-docker/dockerhub] -- This message was sent by Atlassian Jira (v8.3.2#803003)
