You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/04/11 08:16:25 UTC
[jira] [Commented] (NIFI-1746) NiFi will not start when 'conf'
directory is a symbolic link
[ https://issues.apache.org/jira/browse/NIFI-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234541#comment-15234541 ]
ASF subversion and git services commented on NIFI-1746:
-------------------------------------------------------
Commit 5625686ea4abdd38cc168607157ac34622e7b105 in nifi's branch refs/heads/master from [~boardm26]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5625686 ]
NIFI-1746 avoid exceptions if configuration dir is a symbolic link
Signed-off-by: Joe Skora <js...@apache.org>
> NiFi will not start when 'conf' directory is a symbolic link
> ------------------------------------------------------------
>
> Key: NIFI-1746
> URL: https://issues.apache.org/jira/browse/NIFI-1746
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.0
> Reporter: Michael Moser
> Assignee: Michael Moser
> Priority: Trivial
> Fix For: 1.0.0, 0.7.0
>
> Attachments: NIFI-1746.patch
>
>
> Yes this case is probably rare, but people try many things to make upgrading NiFi easier for themselves. When the directory containing the flow.xml.gz (nifi.properties nifi.flow.configuration.file=./conf/flow.xml.gz) is actually a symbolic link to another directory AND the flow.xml.gz doesn't yet exist in that directory, then NiFi throws an exception and fails to start.
> 2016-04-08 13:14:54,239 WARN [main] org.eclipse.jetty.webapp.WebAppContext Failed startup of context o.e.j.w.WebAppContext@a407e8f{/
> nifi-api,file:/local/mosermw/nifi-0.6.1/work/jetty/nifi-web-api-0.6.1.war/webapp/,STARTING}{./work/nar/framework/nifi-framework-nar-
> 0.6.1.nar-unpacked/META-INF/bundled-dependencies/nifi-web-api-0.6.1.war}
> org.apache.nifi.web.NiFiCoreException: Unable to start Flow Controller.
> ...
> Caused by: java.nio.file.FileAlreadyExistsException: ./conf
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:88) ~[na:1.7.0_80]
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[na:1.7.0_80]
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[na:1.7.0_80]
> at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:383) ~[na:1.7.0_80]
> at java.nio.file.Files.createDirectory(Files.java:630) ~[na:1.7.0_80]
> at java.nio.file.Files.createAndCheckIsDirectory(Files.java:734) ~[na:1.7.0_80]
> at java.nio.file.Files.createDirectories(Files.java:683) ~[na:1.7.0_80]
> at org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.<init>(StandardXMLFlowConfigurationDAO.java:56) ~[nifi-framew
> ork-core-0.6.1.jar:0.6.1]
> at org.apache.nifi.controller.StandardFlowService.<init>(StandardFlowService.java:167) ~[nifi-framework-core-0.6.1.jar:0.6.1
> ]
> at org.apache.nifi.controller.StandardFlowService.createStandaloneInstance(StandardFlowService.java:131) ~[nifi-framework-co
> re-0.6.1.jar:0.6.1]
> at org.apache.nifi.spring.StandardFlowServiceFactoryBean.getObject(StandardFlowServiceFactoryBean.java:63) ~[nifi-framework-
> core-0.6.1.jar:0.6.1]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)