subject:"nifi error"

Re: NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

2021-01-05 Thread Sushil Kumar

Hello Karthikeyan

As Chris has pointed out, you would need to add node identities
in authorizations.xml

This is required to establish node identity with NiFi cluster.

Thanks
Sushil Kumar

On Tue, Jan 5, 2021 at 7:52 AM MUTHUKRISHNAN, KARTHIKEYAN 
wrote:

> Hi Team,
>
> Can you help us to troubleshoot this issue ?
>
>
> Thanks & Regards,
> M.Karthikeyan.
>
>
> 
> From: MUTHUKRISHNAN, KARTHIKEYAN
> Sent: Tuesday, December 22, 2020 7:08 PM
> To: dev@nifi.apache.org 
> Cc: RANJAN, RAJIV ; RAJU, JOSEPH 
> Subject: NiFi Error on SSL Setup for cluster UI not loading - Insufficient
> Permissions Untrusted proxy
>
> Hi Team,
>
> I have created a NiFi cluster with 3 nodes and configured SSL for all 3
> eith self signed certs generated for all 3 nodes and a admin user cert. I
> have also configured authorization.xml and nifi.properties acordingly as
> prescribed. I can see users.xml and authorizers.xml getting generated
> properly with Initial Admin configured with cert admin id. All looks good
> in my config files. But i am getting following error in ui : Insufficient
> Permissions Untrusted proxy CN=.YY.ZZ.com, OU=NIFI
>
> nifi-user Logs looks as with below errors,
>
> 2020-12-22 13:05:27,375 INFO [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (CN=nifi-admin)
> GET https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip:
> xx.xx.xx.xxx)
> 2020-12-22 13:05:27,380 INFO [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Authentication success for CN=nifi-admin
> 2020-12-22 13:05:53,219 INFO [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Attempting request for
> () GET
> https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip:
> 130.6.168.62)
> 2020-12-22 13:05:53,226 WARN [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Rejecting access to web api: Untrusted
> proxy CN=.YY.ZZ.com, OU=NIFI
>
> Could you please help me to narrow down if i am missing anything other
> than specified on documentations ?
>
>
> Thanks & Regards,
> M.Karthikeyan.
>
>

Re: NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

2021-01-05 Thread MUTHUKRISHNAN, KARTHIKEYAN

Hi Team,

Can you help us to troubleshoot this issue ?


Thanks & Regards,
M.Karthikeyan.



From: MUTHUKRISHNAN, KARTHIKEYAN
Sent: Tuesday, December 22, 2020 7:08 PM
To: dev@nifi.apache.org 
Cc: RANJAN, RAJIV ; RAJU, JOSEPH 
Subject: NiFi Error on SSL Setup for cluster UI not loading - Insufficient 
Permissions Untrusted proxy

Hi Team,

I have created a NiFi cluster with 3 nodes and configured SSL for all 3 eith 
self signed certs generated for all 3 nodes and a admin user cert. I have also 
configured authorization.xml and nifi.properties acordingly as prescribed. I 
can see users.xml and authorizers.xml getting generated properly with Initial 
Admin configured with cert admin id. All looks good in my config files. But i 
am getting following error in ui : Insufficient Permissions Untrusted proxy 
CN=.YY.ZZ.com, OU=NIFI

nifi-user Logs looks as with below errors,

2020-12-22 13:05:27,375 INFO [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (CN=nifi-admin) GET 
https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip: xx.xx.xx.xxx)
2020-12-22 13:05:27,380 INFO [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Authentication success for CN=nifi-admin
2020-12-22 13:05:53,219 INFO [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Attempting request for 
() GET 
https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip: 130.6.168.62)
2020-12-22 13:05:53,226 WARN [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Rejecting access to web api: Untrusted proxy 
CN=.YY.ZZ.com, OU=NIFI

Could you please help me to narrow down if i am missing anything other than 
specified on documentations ?


Thanks & Regards,
M.Karthikeyan.

Re: NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

2020-12-22 Thread Chris Sampson

Have you added each Node's identity to the Authorizers list (see
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#cluster-node-identities
)?

Note that the Nodes have to appear in the userGroupProvider section as an
"Initial User Identity" as well as in the accessPolicyProvider as "Node
Identity" elements.

These additions should mark each of the NiFi nodes as having "Proxy"
permissions within the cluster, which means users can then connect through
any of the nodes (where they will be identified and granted any assigned
policies).


---
*Chris Sampson*
IT Consultant
chris.samp...@naimuri.com



On Tue, 22 Dec 2020 at 13:41, MUTHUKRISHNAN, KARTHIKEYAN 
wrote:

> Hi Team,
>
> I have created a NiFi cluster with 3 nodes and configured SSL for all 3
> eith self signed certs generated for all 3 nodes and a admin user cert. I
> have also configured authorization.xml and nifi.properties acordingly as
> prescribed. I can see users.xml and authorizers.xml getting generated
> properly with Initial Admin configured with cert admin id. All looks good
> in my config files. But i am getting following error in ui : Insufficient
> Permissions Untrusted proxy CN=.YY.ZZ.com, OU=NIFI
>
> nifi-user Logs looks as with below errors,
>
> 2020-12-22 13:05:27,375 INFO [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (CN=nifi-admin)
> GET https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip:
> xx.xx.xx.xxx)
> 2020-12-22 13:05:27,380 INFO [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Authentication success for CN=nifi-admin
> 2020-12-22 13:05:53,219 INFO [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Attempting request for
> () GET
> https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip:
> 130.6.168.62)
> 2020-12-22 13:05:53,226 WARN [NiFi Web Server-61]
> o.a.n.w.s.NiFiAuthenticationFilter Rejecting access to web api: Untrusted
> proxy CN=.YY.ZZ.com, OU=NIFI
>
> Could you please help me to narrow down if i am missing anything other
> than specified on documentations ?
>
>
> Thanks & Regards,
> M.Karthikeyan.
>
>

NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

2020-12-22 Thread MUTHUKRISHNAN, KARTHIKEYAN

Hi Team,

I have created a NiFi cluster with 3 nodes and configured SSL for all 3 eith 
self signed certs generated for all 3 nodes and a admin user cert. I have also 
configured authorization.xml and nifi.properties acordingly as prescribed. I 
can see users.xml and authorizers.xml getting generated properly with Initial 
Admin configured with cert admin id. All looks good in my config files. But i 
am getting following error in ui : Insufficient Permissions Untrusted proxy 
CN=.YY.ZZ.com, OU=NIFI

nifi-user Logs looks as with below errors,

2020-12-22 13:05:27,375 INFO [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (CN=nifi-admin) GET 
https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip: xx.xx.xx.xxx)
2020-12-22 13:05:27,380 INFO [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Authentication success for CN=nifi-admin
2020-12-22 13:05:53,219 INFO [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Attempting request for 
() GET 
https://.YY.ZZ.com:9443/nifi-api/flow/current-user (source ip: 130.6.168.62)
2020-12-22 13:05:53,226 WARN [NiFi Web Server-61] 
o.a.n.w.s.NiFiAuthenticationFilter Rejecting access to web api: Untrusted proxy 
CN=.YY.ZZ.com, OU=NIFI

Could you please help me to narrow down if i am missing anything other than 
specified on documentations ?


Thanks & Regards,
M.Karthikeyan.

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-20 Thread Bryan Bende

nested exception is
org.apache.nifi.authorization.exception.AuthorizerCreationException:
org.apache.nifi.authorization.exception.AuthorizerCreationException: Unable
to locate node CN=ohlvnfiap004dd.oh.dev.dat.aws.vz-connect.net, OU=NIFI to
seed policies.

This means CN=ohlvnfiap004dd.oh.dev.dat.aws.vz-connect.net, OU=NIFI
was put in the Node Identities section in the policy provider, but it
wasn't defined as a user in the user group provider.

It needs to be listed in both places, same as initial admin.
On Thu, Sep 20, 2018 at 6:42 AM nifi-san  wrote:
>
> We have no wild cards in the certificates created.Each node certificate has a
> unique CN name same as that of the hostname.
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-20 Thread nifi-san

I deleted the authorizations.xml and user.xml files on all the nodes of the
cluster and restarted the nodes.
The Nifi nodes do not start up and I see the following errors int he logs
now:-

2018-09-20 08:20:09,003 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Failed to start web server: Error creating bean with name
'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
Unsatisfied dependency expressed through method
'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
org.springframework.beans.factory.BeanExpressionException: Expression
parsing failed; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name
'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied
dependency expressed through method 'setJwtAuthenticationProvider' parameter
0; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'jwtAuthenticationProvider' defined in class path resource
[nifi-web-security-context.xml]: Cannot resolve reference to bean
'authorizer' while setting constructor argument; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'authorizer': FactoryBean threw exception on object creation;
nested exception is
org.apache.nifi.authorization.exception.AuthorizerCreationException:
org.apache.nifi.authorization.exception.AuthorizerCreationException: Unable
to locate node CN=hostname, OU=NIFI to seed policies.
2018-09-20 08:20:09,003 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Shutting down...
2018-09-20 08:20:09,662 INFO [main] org.apache.nifi.bootstrap.RunNiFi A
shutdown was initiated. Will not restart NiFi
2018-09-20 08:20:10,291 INFO [main] org.apache.nifi.bootstrap.Command NiFi
has finished shutting down.
2018-09-20 08:20:13,739 INFO [main] o.a.n.b.NotificationServiceManager
Successfully loaded the following 0 services: []
2018-09-20 08:20:13,743 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STARTED
2018-09-20 08:20:13,743 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STOPPED
2018-09-20 08:20:13,743 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_DIED
2018-09-20 08:20:13,759 INFO [main] org.apache.nifi.bootstrap.Command
Starting Apache NiFi...
2018-09-20 08:20:13,760 INFO [main] org.apache.nifi.bootstrap.Command
Working Directory: /opt/app/nifi-1.7.1
2018-09-20 08:20:13,760 INFO [main] org.apache.nifi.bootstrap.Command
Command: java -classpath
/opt/app/nifi-1.7.1/./conf:/opt/app/nifi-1.7.1/./lib/javax.servlet-api-3.1.0.jar:/opt/app/nifi-1.7.1/./lib/jetty-schemas-3.1.jar:/opt/app/nifi-1.7.1/./lib/logback-classic-1.2.3.jar:/opt/app/nifi-1.7.1/./lib/logback-core-1.2.3.jar:/opt/app/nifi-1.7.1/./lib/slf4j-api-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/jcl-over-slf4j-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/jul-to-slf4j-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/log4j-over-slf4j-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/nifi-api-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-framework-api-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-runtime-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-nar-utils-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-properties-1.7.1.jar
-Dorg.apache.jasper.compiler.disablejsr199=true -Xms8g -Xms8g
-Djavax.security.auth.useSubjectCredsOnly=true
-Djava.security.egd=file:/dev/urandom
-Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
-Djava.awt.headless=true -XX:+UseG1GC
-Djava.protocol.handler.pkgs=sun.net.www.protocol
-Dnifi.properties.file.path=/opt/app/nifi-1.7.1/./conf/nifi.properties
-Dnifi.bootstrap.listen.port=40021 -Dapp=NiFi
-Dorg.apache.nifi.bootstrap.config.log.dir=/opt/app/nifi-1.7.1/logs
org.apache.nifi.NiFi
2018-09-20 08:20:13,784 INFO [main] org.apache.nifi.bootstrap.Command
Launched Apache NiFi with Process ID 19384
2018-09-20 08:20:14,481 INFO [NiFi Bootstrap Command Listener]
org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening for
Bootstrap requests on port 40283
2018-09-20 08:20:35,382 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Failed to start web server: Error creating bean with name
'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
Unsatisfied dependency expressed through method
'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
org.springframework.beans.factory.BeanExpressionException: Expression
parsing failed; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name
'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied
dependency expressed through method 'setJwtAuthenticationProvider' parameter
0; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-20 Thread nifi-san

We have no wild cards in the certificates created.Each node certificate has a
unique CN name same as that of the hostname.



--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-20 Thread nifi-san

Thanks for the suggestions.

I tried exactly the same step and deleted authorizations.xml and user.xml
from all the cluster nodes and tried starting the nodes.I am encountering
the below error while starting the nodes now and the node does not start
now.

2018-09-20 08:20:09,003 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Failed to start web server: Error creating bean with name
'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
Unsatisfied dependency expressed through method
'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
org.springframework.beans.factory.BeanExpressionException: Expression
parsing failed; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name
'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied
dependency expressed through method 'setJwtAuthenticationProvider' parameter
0; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'jwtAuthenticationProvider' defined in class path resource
[nifi-web-security-context.xml]: Cannot resolve reference to bean
'authorizer' while setting constructor argument; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'authorizer': FactoryBean threw exception on object creation;
nested exception is
org.apache.nifi.authorization.exception.AuthorizerCreationException:
org.apache.nifi.authorization.exception.AuthorizerCreationException: Unable
to locate node CN=hostname, OU=NIFI to seed policies.
2018-09-20 08:20:09,003 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Shutting down...
2018-09-20 08:20:09,662 INFO [main] org.apache.nifi.bootstrap.RunNiFi A
shutdown was initiated. Will not restart NiFi
2018-09-20 08:20:10,291 INFO [main] org.apache.nifi.bootstrap.Command NiFi
has finished shutting down.
2018-09-20 08:20:13,739 INFO [main] o.a.n.b.NotificationServiceManager
Successfully loaded the following 0 services: []
2018-09-20 08:20:13,743 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STARTED
2018-09-20 08:20:13,743 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_STOPPED
2018-09-20 08:20:13,743 INFO [main] org.apache.nifi.bootstrap.RunNiFi
Registered no Notification Services for Notification Type NIFI_DIED
2018-09-20 08:20:13,759 INFO [main] org.apache.nifi.bootstrap.Command
Starting Apache NiFi...
2018-09-20 08:20:13,760 INFO [main] org.apache.nifi.bootstrap.Command
Working Directory: /opt/app/nifi-1.7.1
2018-09-20 08:20:13,760 INFO [main] org.apache.nifi.bootstrap.Command
Command: java -classpath
/opt/app/nifi-1.7.1/./conf:/opt/app/nifi-1.7.1/./lib/javax.servlet-api-3.1.0.jar:/opt/app/nifi-1.7.1/./lib/jetty-schemas-3.1.jar:/opt/app/nifi-1.7.1/./lib/logback-classic-1.2.3.jar:/opt/app/nifi-1.7.1/./lib/logback-core-1.2.3.jar:/opt/app/nifi-1.7.1/./lib/slf4j-api-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/jcl-over-slf4j-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/jul-to-slf4j-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/log4j-over-slf4j-1.7.25.jar:/opt/app/nifi-1.7.1/./lib/nifi-api-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-framework-api-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-runtime-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-nar-utils-1.7.1.jar:/opt/app/nifi-1.7.1/./lib/nifi-properties-1.7.1.jar
-Dorg.apache.jasper.compiler.disablejsr199=true -Xms8g -Xms8g
-Djavax.security.auth.useSubjectCredsOnly=true
-Djava.security.egd=file:/dev/urandom
-Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true
-Djava.awt.headless=true -XX:+UseG1GC
-Djava.protocol.handler.pkgs=sun.net.www.protocol
-Dnifi.properties.file.path=/opt/app/nifi-1.7.1/./conf/nifi.properties
-Dnifi.bootstrap.listen.port=40021 -Dapp=NiFi
-Dorg.apache.nifi.bootstrap.config.log.dir=/opt/app/nifi-1.7.1/logs
org.apache.nifi.NiFi
2018-09-20 08:20:13,784 INFO [main] org.apache.nifi.bootstrap.Command
Launched Apache NiFi with Process ID 19384
2018-09-20 08:20:14,481 INFO [NiFi Bootstrap Command Listener]
org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening for
Bootstrap requests on port 40283
2018-09-20 08:20:35,382 ERROR [NiFi logging handler] org.apache.nifi.StdErr
Failed to start web server: Error creating bean with name
'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
Unsatisfied dependency expressed through method
'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
org.springframework.beans.factory.BeanExpressionException: Expression
parsing failed; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error
creating bean with name
'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied
dependency expressed through method 'setJwtAuthenticationProvider' parameter
0; nested exception is

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-19 Thread nifi-san

Thanks for the reply.Please find below the authorizations.xml and user.xml;-

Authorizations.xml:-


-
-
-


-


-


-


-


-


-


-


-


-


-


-





user.xml:-


-

-




Errors in the user logs:-

2018-09-19 05:25:14,267 INFO [NiFi Web Server-22]
o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException:
Kerberos ticket login not supported by this NiFi.. Returning Conflict
response.
2018-09-19 05:25:14,688 INFO [NiFi Web Server-18]
o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException:
OpenId Connect is not configured.. Returning Conflict response.
2018-09-19 05:25:15,073 INFO [NiFi Web Server-164]
o.a.n.w.s.NiFiAuthenticationFilter Attempting request for (CN=NADMIN,
OU=NIFI) GET https://hostname1:9443/nifi-api/flow/current-user (source ip:
10.253.220.155)
2018-09-19 05:25:15,074 INFO [NiFi Web Server-164]
o.a.n.w.s.NiFiAuthenticationFilter Authentication success for CN=NADMIN,
OU=NIFI
2018-09-19 05:25:15,149 INFO [NiFi Web Server-22]
o.a.n.w.s.NiFiAuthenticationFilter Attempting request for () GET
https://hostname1:9443/nifi-api/flow/current-user (source ip: 10.59.68.155)
2018-09-19 05:25:15,149 WARN [NiFi Web Server-22]
o.a.n.w.s.NiFiAuthenticationFilter Rejecting access to web api: Untrusted
proxy CN=hostname1:9443, OU=NIFI

Shouldn’t the authorizations.xml get automatically generated?
Strange this is, it works fine on the standalone node.






--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-18 Thread Andy LoPresto

A few things to note:

Between NiFi 1.3.0 and NiFi 1.7.0, the authorizer structure changed, as the 
user and group provider was separated from the policy provider. This means 
there are two components (UserGroupProvider) and (AccessPolicyProvider) that 
are defined independently and compose the ManagedAuthorizer. This means that 
for a cluster, the proxies must be defined in two locations in the 
authorizers.xml file (see below).

Also, in NiFi 1.7.1, there were changes to hostname verification and wildcard 
certificates are fixed but wildcard certificates are not supported. If you are 
using wildcard certificates in your cluster, you should convert these to 
unique, explicit certificates for each node. Each node certificate should also 
contain a SubjectAlternativeName entry with the explicit DNS name of the 
service. More information can be found in the Admin Guide [1] or the Migration 
Guidance [2].

Here is an example authorizers.xml file with the proxies defined in both 
locations.





file-user-group-provider
org.apache.nifi.authorization.FileUserGroupProvider
./conf/users.xml


CN=alopresto_NIFI-5370, 
OU=NIFI
CN=node1.nifi.apache.org, 
OU=NIFI
CN=node2.nifi.apache.org, 
OU=NIFI
CN=node3.nifi.apache.org, 
OU=NIFI


file-access-policy-provider
org.apache.nifi.authorization.FileAccessPolicyProvider
file-user-group-provider
./conf/authorizations.xml
CN=alopresto_NIFI-5370, 
OU=NIFI


CN=node1.nifi.apache.org, 
OU=NIFI
CN=node2.nifi.apache.org, 
OU=NIFI
CN=node3.nifi.apache.org, 
OU=NIFI


managed-authorizer
org.apache.nifi.authorization.StandardManagedAuthorizer
file-access-policy-provider



[1] 
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#tls-generation-toolkit
[2] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Sep 18, 2018, at 4:55 AM, Peter Wilcsinszky  
> wrote:
> 
> Hi,
> 
> are your hosts registered in LDAP properly? If you don't want them to come
> from LDAP then they should come from the file-user-group-provider as
> initial user identities in addition to your "Initial User Identity 1".
> 
> Peter
> 
> On Tue, Sep 18, 2018 at 11:54 AM nifi-san  wrote:
> 
>> Hello,
>> 
>> We are trying to integrate Nifi-7.1 with SSL and LDAP.
>> 
>> We have two different Nifi installation,one which is a standalone node and
>> the other which is a three node cluster.
>> 
>> Nifi Standalone:-
>> We were able to successfully integrate the Standalone node with SSL and
>> login to the Nifi UI with the client certificate.
>> 
>> Nifi Cluster:-
>> With the same configurations for authorizers.xml as is for the Nifi
>> standalone, on the Nifi cluster nodes,we get the below error:-
>> 
>> ERROR:-
>> 
>> Insufficient Permissions
>> Untrusted proxy CN=host1, OU=NIFI
>> 
>> 
>> The authorizers.xml configurations on the cluster is as follows:-
>> 
>> 
>> 
>>
>>file-user-group-provider
>>org.apache.nifi.authorization.FileUserGroupProvider
>>/opt/app/resources/nifi/users.xml
>>
>> 
>>CN=NADMIN,
>> OU=NIFI
>>
>>
>>file-access-policy-provider
>> 
>> org.apache.nifi.authorization.FileAccessPolicyProvider
>>file-user-group-provider
>>/opt/app/resources/nifi/authorizations.xml
>>CN=NADMIN,
>> OU=NIFI
>>
>> 
>>> name="ohlvnfiap002dd.oh.dev.dat.aws.vz-connect.net">
>>CN=host1, OU=NIFI
>> CN=host2, OU=NIFI
>> CN=host3, OU=NIFI
>>
>>
>>managed-authorizer
>> 
>> org.apache.nifi.authorization.StandardManagedAuthorizer
>>file-access-policy-provider
>>
>> 
>> 
>> We have checked the FQDN and the CN Name of the certificates generated and
>> all other configurations but could not identify anything specifically that
>> could be the root cause of the issue.
>> 
>> Apart from the above error with respect to privilege, we do not see any
>> other error in the logs.
>> 
>> The same configurations worked fine on Nifi-1.3,however, not sure why it
>> does not work on Nifi-1.7.
>> Also, it works fine on the standalone node but not on the cluster.
>> 
>> Appreciate if you could provide any assistance on this as it has already
>> been a while that we have been blocked because of this issue.
>> 
>> 
>> 
>> --
>> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-18 Thread Peter Wilcsinszky

Hi,

are your hosts registered in LDAP properly? If you don't want them to come
from LDAP then they should come from the file-user-group-provider as
initial user identities in addition to your "Initial User Identity 1".

Peter

On Tue, Sep 18, 2018 at 11:54 AM nifi-san  wrote:

> Hello,
>
> We are trying to integrate Nifi-7.1 with SSL and LDAP.
>
> We have two different Nifi installation,one which is a standalone node and
> the other which is a three node cluster.
>
> Nifi Standalone:-
> We were able to successfully integrate the Standalone node with SSL and
> login to the Nifi UI with the client certificate.
>
> Nifi Cluster:-
> With the same configurations for authorizers.xml as is for the Nifi
> standalone, on the Nifi cluster nodes,we get the below error:-
>
> ERROR:-
> 
> Insufficient Permissions
> Untrusted proxy CN=host1, OU=NIFI
> 
>
> The authorizers.xml configurations on the cluster is as follows:-
>
> 
> 
> 
> file-user-group-provider
> org.apache.nifi.authorization.FileUserGroupProvider
> /opt/app/resources/nifi/users.xml
> 
>
> CN=NADMIN,
> OU=NIFI
> 
> 
> file-access-policy-provider
>
> org.apache.nifi.authorization.FileAccessPolicyProvider
> file-user-group-provider
> /opt/app/resources/nifi/authorizations.xml
> CN=NADMIN,
> OU=NIFI
> 
>
>  name="ohlvnfiap002dd.oh.dev.dat.aws.vz-connect.net">
> CN=host1, OU=NIFI
> CN=host2, OU=NIFI
> CN=host3, OU=NIFI
> 
> 
> managed-authorizer
>
> org.apache.nifi.authorization.StandardManagedAuthorizer
> file-access-policy-provider
> 
> 
>
> We have checked the FQDN and the CN Name of the certificates generated and
> all other configurations but could not identify anything specifically that
> could be the root cause of the issue.
>
> Apart from the above error with respect to privilege, we do not see any
> other error in the logs.
>
> The same configurations worked fine on Nifi-1.3,however, not sure why it
> does not work on Nifi-1.7.
> Also, it works fine on the standalone node but not on the cluster.
>
> Appreciate if you could provide any assistance on this as it has already
> been a while that we have been blocked because of this issue.
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-18 Thread Pierre Villard

Sounds like a permission issue. Can you share the content of
/opt/app/resources/nifi/authorizations.xml to be sure that /proxy
permissions have been correctly set on the node entities?

Thanks,
Pierre

Le mar. 18 sept. 2018 à 11:54, nifi-san  a écrit :

> Hello,
>
> We are trying to integrate Nifi-7.1 with SSL and LDAP.
>
> We have two different Nifi installation,one which is a standalone node and
> the other which is a three node cluster.
>
> Nifi Standalone:-
> We were able to successfully integrate the Standalone node with SSL and
> login to the Nifi UI with the client certificate.
>
> Nifi Cluster:-
> With the same configurations for authorizers.xml as is for the Nifi
> standalone, on the Nifi cluster nodes,we get the below error:-
>
> ERROR:-
> 
> Insufficient Permissions
> Untrusted proxy CN=host1, OU=NIFI
> 
>
> The authorizers.xml configurations on the cluster is as follows:-
>
> 
> 
> 
> file-user-group-provider
> org.apache.nifi.authorization.FileUserGroupProvider
> /opt/app/resources/nifi/users.xml
> 
>
> CN=NADMIN,
> OU=NIFI
> 
> 
> file-access-policy-provider
>
> org.apache.nifi.authorization.FileAccessPolicyProvider
> file-user-group-provider
> /opt/app/resources/nifi/authorizations.xml
> CN=NADMIN,
> OU=NIFI
> 
>
>  name="ohlvnfiap002dd.oh.dev.dat.aws.vz-connect.net">
> CN=host1, OU=NIFI
> CN=host2, OU=NIFI
> CN=host3, OU=NIFI
> 
> 
> managed-authorizer
>
> org.apache.nifi.authorization.StandardManagedAuthorizer
> file-access-policy-provider
> 
> 
>
> We have checked the FQDN and the CN Name of the certificates generated and
> all other configurations but could not identify anything specifically that
> could be the root cause of the issue.
>
> Apart from the above error with respect to privilege, we do not see any
> other error in the logs.
>
> The same configurations worked fine on Nifi-1.3,however, not sure why it
> does not work on Nifi-1.7.
> Also, it works fine on the standalone node but not on the cluster.
>
> Appreciate if you could provide any assistance on this as it has already
> been a while that we have been blocked because of this issue.
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>

Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

2018-09-18 Thread nifi-san

Hello,

We are trying to integrate Nifi-7.1 with SSL and LDAP.

We have two different Nifi installation,one which is a standalone node and
the other which is a three node cluster.

Nifi Standalone:-
We were able to successfully integrate the Standalone node with SSL and
login to the Nifi UI with the client certificate.

Nifi Cluster:-
With the same configurations for authorizers.xml as is for the Nifi
standalone, on the Nifi cluster nodes,we get the below error:-

ERROR:-

Insufficient Permissions  
Untrusted proxy CN=host1, OU=NIFI  


The authorizers.xml configurations on the cluster is as follows:-




file-user-group-provider
org.apache.nifi.authorization.FileUserGroupProvider
/opt/app/resources/nifi/users.xml


CN=NADMIN,
OU=NIFI


file-access-policy-provider
   
org.apache.nifi.authorization.FileAccessPolicyProvider
file-user-group-provider
/opt/app/resources/nifi/authorizations.xml
CN=NADMIN,
OU=NIFI



CN=host1, OU=NIFI
CN=host2, OU=NIFI
CN=host3, OU=NIFI


managed-authorizer
   
org.apache.nifi.authorization.StandardManagedAuthorizer
file-access-policy-provider



We have checked the FQDN and the CN Name of the certificates generated and
all other configurations but could not identify anything specifically that
could be the root cause of the issue.

Apart from the above error with respect to privilege, we do not see any
other error in the logs.

The same configurations worked fine on Nifi-1.3,however, not sure why it
does not work on Nifi-1.7.
Also, it works fine on the standalone node but not on the cluster.

Appreciate if you could provide any assistance on this as it has already
been a while that we have been blocked because of this issue.



--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/

Re: APACHE NIFI error message details are not coming

2017-07-12 Thread Pierre Villard

Hi Vijaya,

I believe the endpoints you're trying are not correct. I'd suggest you to
base your requests on the API documentation:
https://nifi.apache.org/docs/nifi-docs/rest-api/

Thanks!
Pierre

2017-07-12 19:19 GMT+02:00 Vijaya Maddela :

> Hi Team
>
> On NIFI 1.3 version we are not able to access
>
>
>
> http://localhost:8080/nifi-api/controller/status
>
>
>
>
>
> http://localhost:8080/nifi-api/controller/process-groups/
>
>
>
>
>
> http://localhost:8080/nifi-api/controller/process-groups/
> 2cf65be8-015d-1000-b5a5-8be5924a5e4e/status?recursive=true
>
>
>
>
>
> Do we need to configure any parameter? Is it bug in NIFI 1.3 version?
>
>
>
>
>
>
>
>
>
> Thank You
>
> Much Respect
>
> Vijaya Kumar Reddy.Maddela
>
> vijay.re...@eaiesb.com
>
> 91-40-40119993|9704179993 <(970)%20417-9993>
>
> USA:978-306-3751 <(978)%20306-3751>
>
> [image: O_GoldPartner]
>
>
>

APACHE NIFI error message details are not coming

2017-07-12 Thread Vijaya Maddela

Hi Team

On NIFI 1.3 version we are not able to access 

 

http://localhost:8080/nifi-api/controller/status

 

 

http://localhost:8080/nifi-api/controller/process-groups/

 

 

http://localhost:8080/nifi-api/controller/process-groups/2cf65be8-015d-1000-
b5a5-8be5924a5e4e/status?recursive=true

 

 

Do we need to configure any parameter? Is it bug in NIFI 1.3 version?

 

 

 

 

Thank You

Much Respect

Vijaya Kumar Reddy.Maddela

  vijay.re...@eaiesb.com

91-40-40119993|9704179993

USA:978-306-3751

Re: NiFi error with embedded ZooKeeper for State Management

2016-03-14 Thread Mark Payne

Sumo,

I do believe that you should be okay leaving that java.arg.15 in, in that case. 
The ZooKeeper Client
will use the "Client" section of that file, if it is defined. In the example 
that you provided, that Client section
does not exist, so it is okay. What would not work in this case would be to use 
an Embedded ZooKeeper Server
without kerberos, but it sounds like that is not what you are after, so I 
believe you should be in
good shape with the setup that you described.

Of course, if you do run into specific issues running this way, please let us 
know!

Thanks
-Mark


> On Mar 14, 2016, at 2:18 PM, Sumanth Chinthagunta  wrote:
> 
> Thanks Mark. 
> I had java.arg.15 setting in bootstrap.conf  from NiFi 0.4.x to make putHDFS 
> processor work with my MapR cluster. If I remove it, putHDFS will fail. 
> 
> Now with NiFi 0.5.1, 
> if I set nifi.state.management.embedded.zookeeper.start=false , 
> can I point to dedicated external ZooKeeper in conf/state-management.xml 
> without interfering with java.arg.15 setting that is used by putHDFS?
> Thanks 
> Sumo 
> 
> 
>> On Mar 14, 2016, at 10:10 AM, Mark Payne  wrote:
>> 
>> Sumo,
>> 
>> If your intent is to use an external ZooKeeper, you should not be starting 
>> the embedded ZooKeeper.
>> You will also not want to set the java.arg.15 parameter there to point to a 
>> login config file, as that is
>> necessary only when enabling Kerberos - not for use when security disabled.
>> 
>> So you would want to change the following in your config:
>> - Remove the java.arg.15 parameter from bootstrap.conf
>> - Set the nifi.state.management.embedded.zookeeper.start property to false
>> - Change the conf/state-management.xml to point to the external ZooKeeper 
>> via the Connect String property.
>> 
>> Does all of this make sense?
>> 
>> Thanks
>> -Mark
>> 
>> 
>>> On Mar 14, 2016, at 12:59 PM, Sumanth Chinthagunta  
>>> wrote:
>>> 
>>> I am getting following error when  NiFi Cluster started with  embedded 
>>> ZooKeeper enabled.  
>>> I would like to configure external ZooKeeper for NiFi State Management  
>>> without interfering with java.security.auth.login.config setting for MapR 
>>> HDFS. Can somebody provide me instructions how to configure external 
>>> ZooKeeper for NiFi cluster State Management without security enabled? 
>>> 
>>> Env :
>>> NiFi 0.5.1 cluster (NCM, Node1, Node2)
>>> I have following line in  bootstrap.conf
>>> # ***For MapR HDFS***
>>> java.arg.15=-Djava.security.auth.login.config=/opt/mapr/conf/mapr.login.conf
>>> 
>>> /opt/mapr/conf/mapr.login.conf has
>>> /**
>>> * Used by Zookeeper
>>> */
>>> Server {
>>> com.mapr.security.maprsasl.MaprSecurityLoginModule required
>>>checkUGI=false
>>>cldbkeylocation="/opt/mapr/conf/cldb.key"
>>>debug=true;
>>> };
>>> 
>>> I have following in zookeeper.properties
>>> server.2=myhost2:2888:3888
>>> 
>>> 
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server environment:java.io.tmpdir=/tmp
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server environment:java.compiler=
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server environment:os.name=Linux
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server environment:os.arch=amd64
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server 
>>> environment:os.version=2.6.32-573.3.1.el6.x86_64
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server environment:user.name=sumo
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server environment:user.home=/home/ 
>>> sumo
>>> 2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer Server 
>>> environment:user.dir=/app/runtime/nifi-node2
>>> 2016-03-12 16:39:07,519 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer tickTime set to 2000
>>> 2016-03-12 16:39:07,519 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer minSessionTimeout set to -1
>>> 2016-03-12 16:39:07,519 INFO [Framework Task Thread Thread-1] 
>>> o.a.zookeeper.server.ZooKeeperServer maxSessionTimeout set to -1
>>> 2016-03-12 16:39:07,539 ERROR [Framework Task Thread Thread-1] 
>>> o.apache.nifi.controller.FlowController NiFi was connected to the cluster 
>>> but failed to start embedded ZooKeeper Server
>>> java.io.IOException: Failed to start embedded ZooKeeper Server
>>>  at 
>>> org.apache.nifi.controller.state.server.ZooKeeperStateServer.startStandalone(ZooKeeperStateServer.java:87)
>>>  ~[na:na]
>>>  at 
>>>

NiFi error with embedded ZooKeeper for State Management

2016-03-14 Thread Sumanth Chinthagunta

I am getting following error when  NiFi Cluster started with  embedded 
ZooKeeper enabled.  
I would like to configure external ZooKeeper for NiFi State Management  without 
interfering with java.security.auth.login.config setting for MapR HDFS. Can 
somebody provide me instructions how to configure external ZooKeeper for NiFi 
cluster State Management without security enabled? 
 
Env :
NiFi 0.5.1 cluster (NCM, Node1, Node2)
I have following line in  bootstrap.conf
# ***For MapR HDFS***
java.arg.15=-Djava.security.auth.login.config=/opt/mapr/conf/mapr.login.conf
 
/opt/mapr/conf/mapr.login.conf has
/**
* Used by Zookeeper
*/
Server {
  com.mapr.security.maprsasl.MaprSecurityLoginModule required
  checkUGI=false
  cldbkeylocation="/opt/mapr/conf/cldb.key"
  debug=true;
};
 
I have following in zookeeper.properties
server.2=myhost2:2888:3888
 
 
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server environment:java.io.tmpdir=/tmp
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server environment:java.compiler=
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server environment:os.name=Linux
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server environment:os.arch=amd64
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server 
environment:os.version=2.6.32-573.3.1.el6.x86_64
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server environment:user.name=sumo
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server environment:user.home=/home/ sumo
2016-03-12 16:39:07,518 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer Server 
environment:user.dir=/app/runtime/nifi-node2
2016-03-12 16:39:07,519 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer tickTime set to 2000
2016-03-12 16:39:07,519 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer minSessionTimeout set to -1
2016-03-12 16:39:07,519 INFO [Framework Task Thread Thread-1] 
o.a.zookeeper.server.ZooKeeperServer maxSessionTimeout set to -1
2016-03-12 16:39:07,539 ERROR [Framework Task Thread Thread-1] 
o.apache.nifi.controller.FlowController NiFi was connected to the cluster but 
failed to start embedded ZooKeeper Server
java.io.IOException: Failed to start embedded ZooKeeper Server
at 
org.apache.nifi.controller.state.server.ZooKeeperStateServer.startStandalone(ZooKeeperStateServer.java:87)
 ~[na:na]
at 
org.apache.nifi.controller.state.server.ZooKeeperStateServer.start(ZooKeeperStateServer.java:60)
 ~[na:na]
at 
org.apache.nifi.controller.FlowController$5.run(FlowController.java:3145) 
~[na:na]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_65]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_65]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [na:1.8.0_65]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_65]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
Caused by: java.io.IOException: Could not configure server because SASL 
configuration did not allow the  ZooKeeper server to authenticate itself 
properly: javax.security.auth.login.LoginException: unable to find LoginModule 
class: com.mapr.security.maprsasl.MaprSecurityLoginModule
at 
org.apache.zookeeper.server.ServerCnxnFactory.configureSaslLogin(ServerCnxnFactory.java:207)
 ~[na:na]
at 
org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:87)
 ~[na:na]
at 
org.apache.nifi.controller.state.server.ZooKeeperStateServer.startStandalone(ZooKeeperStateServer.java:81)
 ~[na:na]
... 9 common frames omitted
 
 Thanks 
Sumo

Re: nifi error

2015-09-08 Thread sagar gaikwad

Looks like your code repository has changes. I dont see nifi-parent directory
anymore. Also I checked the install instructions on your web page. It only
has 3 steps. set up jdk, set up maven and build the entire project.

I get the following error when I try to build the entire project. I have
used vagrant to set up an ubuntu machine, clone code from github, set up
maven and jdk.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
on project nifi: Error finding remote resources manifests:
/home/vagrant/nifi/target/maven-shared-archive-resources/META-INF/NOTICE (No
such file or directory) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException








--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/nifi-error-tp2240p2721.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: nifi error

2015-07-28 Thread Adam Taft

One possible option to help on this might be to commit a .gitattributes
file, which would basically name the problematic test files and mark them
to not modify their line endings.

http://git-scm.com/docs/gitattributes

I think the format would look something like:

/path/to/problematic/test/file -text

where the '-text' option would tell git to treat the file more like binary
and not convert line endings.



On Tue, Jul 28, 2015 at 11:15 AM, Mark Payne marka...@hotmail.com wrote:

 Excellent! Feel free to reach out if you run into any other issues.

 Thanks
 -Mark

 
  Date: Tue, 28 Jul 2015 07:37:42 -0700
  From: dattathreyulu.p...@capitalone.com
  To: d...@nifi.incubator.apache.org
  Subject: RE: nifi error
 
  thanks mark
 
  after running the
  git config --global core.autocrlf false
 
  and then i ran just the mvn clean install from the nifi folder and it
 worked
  and the build was successful.
 
 
 
 
 
  --
  View this message in context:
 http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/nifi-error-tp2240p2278.html
  Sent from the Apache NiFi (incubating) Developer List mailing list
 archive at Nabble.com.

Re: nifi error

2015-07-27 Thread sagar gaikwad

Aldrin,
I was able to get it working. It worked I ran the install command in
singular mode 

mvn clean install instead of mvn -T 2.0C clean install 


Also would it be possible to modify the relative path tab in your POM file.
It is not currently set up. Any reason why



--
View this message in context: 
http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/nifi-error-tp2240p2265.html
Sent from the Apache NiFi (incubating) Developer List mailing list archive at 
Nabble.com.

Re: nifi error

2015-07-27 Thread Joe Skora

For future reference, there is a section in the Contributor Guide that
captures relevant Git configuration options.


https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-Configureyourgitclient

On Mon, Jul 27, 2015 at 2:41 PM, Mark Payne marka...@hotmail.com wrote:

 Hello,

 I've seen this before when doing a git clone and not having the
 core.autocrlf property set to false.

 This will tell Git not to try to change line endings automatically. The
 problem is that Git will automatically change the line endings on the files
 that we use for unit testing. As a result, the unit tests fail because the
 files are not what it expects.

 If you run the following:

 git config --global core.autocrlf false

 That will tell git not to change the line feeds. You'll then need to
 checkout the standard-processors module again (an easy way to do this is to
 just delete the standard-processors directory and then from its parent run
 git checkout -- standard-processors).

 After that, I think you should be good to go.

 If you run into any other problems, please feel free to let us know!

 Thanks
 -Mark

 
  Date: Mon, 27 Jul 2015 11:05:09 -0700
  From: dattathreyulu.p...@capitalone.com
  To: d...@nifi.incubator.apache.org
  Subject: Re: nifi error
 
  Error we are getting after running mvn -T C2.0 clean install
 
  Line #1
  TestUnpackContent.testFlowFileStreamV2:127 FlowFile content differs from
  input
  at byte 20 with input having value 13 and FlowFile having value 10
  TestUnpackContent.testFlowFileStreamV3:104 FlowFile content differs from
  input
  at byte 20 with input having value 13 and FlowFile having value 10
  TestUnpackContent.testTar:58 FlowFile content differs from input at byte
  20 wi
  th input having value 13 and FlowFile having value 10
  TestUnpackContent.testZip:81 FlowFile content differs from input at byte
  20 wi
  th input having value 13 and FlowFile having value 10
 
 
 
  Tests run: 282, Failures: 19, Errors: 0, Skipped: 11
 
  [INFO]
  
  [INFO] Reactor Summary:
  [INFO]
  [INFO] nifi ... SUCCESS [
 1.887
  s]
  [INFO] nifi-api ... SUCCESS [
 19.807
  s]
  [INFO] nifi-commons ... SUCCESS [
 1.359
  s]
  [INFO] nifi-utils . SUCCESS [
 31.130
  s]
  [INFO] nifi-data-provenance-utils . SUCCESS [
 7.161
  s]
  [INFO] nifi-flowfile-packager . SUCCESS [
 11.046
  s]
  [INFO] nifi-expression-language ... SUCCESS [
 54.819
  s]
  [INFO] nifi-logging-utils . SUCCESS [
 4.233
  s]
  [INFO] nifi-properties  SUCCESS [
 12.479
  s]
  [INFO] nifi-security-utils  SUCCESS [
 5.817
  s]
  [INFO] nifi-socket-utils .. SUCCESS [
 13.313
  s]
  [INFO] nifi-web-utils . SUCCESS [
 9.387
  s]
  [INFO] nifi-processor-utils ... SUCCESS [
 16.229
  s]
  [INFO] nifi-write-ahead-log ... SUCCESS [
 38.448
  s]
  [INFO] nifi-nar-bundles ... SUCCESS [
 1.297
  s]
  [INFO] nifi-framework-bundle .. SUCCESS [
 1.436
  s]
  [INFO] nifi-framework . SUCCESS [
 0.281
  s]
  [INFO] nifi-client-dto  SUCCESS [
 15.894
  s]
  [INFO] nifi-site-to-site-client ... SUCCESS [
 23.376
  s]
  [INFO] nifi-hl7-query-language  SUCCESS [
 29.190
  s]
  [INFO] nifi-bootstrap . SUCCESS [
 7.889
  s]
  [INFO] nifi-mock .. SUCCESS [
 22.091
  s]
  [INFO] nifi-nar-utils . SUCCESS [
 17.907
  s]
  [INFO] nifi-framework-core-api  SUCCESS [
 19.074
  s]
  [INFO] nifi-documentation . SUCCESS [
 55.100
  s]
  [INFO] nifi-runtime ... SUCCESS [
 17.176
  s]
  [INFO] nifi-security .. SUCCESS [
 30.447
  s]
  [INFO] nifi-user-actions .. SUCCESS [
 7.611
  s]
  [INFO] nifi-administration  SUCCESS
 [01:08
  min]
  [INFO] nifi-site-to-site .. SUCCESS [
 38.387
  s]
  [INFO] nifi-framework-cluster-protocol  SUCCESS
 [01:21
  min]
  [INFO] nifi-framework-core  SUCCESS
 [03:33
  min]
  [INFO] nifi-framework-cluster-web . SUCCESS [
 8.979
  s]
  [INFO] nifi-web

nifi error

2015-07-24 Thread Peri, Dattathreyulu

Hi ,

I am trying to install NIFI and followed the instructions as suggested on 
http://nifi.apache.org/quickstart.html

I cloned the

git clone http://git-wip-us.apache.org/repos/asf/nifi.git

and tried to run the mvn clean install from  nifi-nar-maven-plugin directory 
but getting the below error.  Can you please let me know if I am missing 
anything here?.  I did set up the proxy variables and running this command from 
GIT bash session






$ mvn clean install
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/apache/nifi/nifi-parent/1.
0.0-incubating/nifi-parent-1.0.0-incubating.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.apache.nifi:nifi-nar-maven-plugin:1.0.
2-incubating-SNAPSHOT: Could not transfer artifact org.apache.nifi:nifi-parent:p
om:1.0.0-incubating from/to central (https://repo.maven.apache.org/maven2): Conn
ect to repo.maven.apache.org:443 [repo.maven.apache.org/23.235.44.215] failed: C
onnection timed out: connect and 'parent.relativePath' points at no local POM @
line 18, column 13
@
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR]   The project org.apache.nifi:nifi-nar-maven-plugin:1.0.2-incubating-SNA
PSHOT (c:\2014\nifi_test\nifi\nifi-nar-maven-plugin\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.apache.nifi:nifi-nar-maven-plugin:
1.0.2-incubating-SNAPSHOT: Could not transfer artifact org.apache.nifi:nifi-pare
nt:pom:1.0.0-incubating from/to central (https://repo.maven.apache.org/maven2):
Connect to repo.maven.apache.org:443 [repo.maven.apache.org/23.235.44.215] faile
d: Connection timed out: connect and 'parent.relativePath' points at no local PO
M @ line 18, column 13 - [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildin
gException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableMo
delException


Thanks
Dattu



The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

Re: NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

Re: NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

Re: NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

NiFi Error on SSL Setup for cluster UI not loading - Insufficient Permissions Untrusted proxy

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Nifi -1.7 -Insufficient Permissions Untrusted proxy CN=host1, OU=NIFI error on cluster node

Re: APACHE NIFI error message details are not coming

APACHE NIFI error message details are not coming

Re: NiFi error with embedded ZooKeeper for State Management

NiFi error with embedded ZooKeeper for State Management

Re: nifi error

Re: nifi error

Re: nifi error

Re: nifi error

nifi error

22 matches

Site Navigation

Mail list logo

Footer information