It looks like NiFi Registry is already running on 127.0.0.1:19443? Attempts to start it again are showing failing to bind in the bootstrap log:
2023-01-12 11:02:58,113 ERROR [NiFi logging handler] org.apache.nifi.registry.StdErr Failed to start web server: Failed to bind to 127.0.0.1 :19443 I suggest trying a different bind port or figuring out why you're unable to bind on the interface/address/hostname you've chosen. You might already have a registry instance running or some other service. If running linux you should be able to check with sudo lsof -i -P -n | grep 19443 If the registry service is running but you're unable to access it, I would kill the process and try and start registry up again. As far as I can tell your authorizers.xml file is fine. Nathan On Thu, Jan 12, 2023 at 11:23 AM EDISON FABRICIO NARANJO ESPIN < efnara...@telconet.ec> wrote: > Dear Nathan, > > This is the output when nifi registry starts. The service stays active for > around 20 seconds and then stops working. > > > 1:06 edinaranjoespin@EFNARANJO-LT:bin $./nifi-registry.sh start > > Java home: /usr/lib/jvm/java-11-openjdk-amd64/ > NiFi Registry home: /home/edinaranjoespin/NiFi/nifi-registry-1.19.0 > > Bootstrap Config File: > /home/edinaranjoespin/NiFi/nifi-registry-1.19.0/conf/bootstrap.conf > > > 11:07 edinaranjoespin@EFNARANJO-LT:bin $./nifi-registry.sh status > > Java home: /usr/lib/jvm/java-11-openjdk-amd64/ > NiFi Registry home: /home/edinaranjoespin/NiFi/nifi-registry-1.19.0 > > Bootstrap Config File: > /home/edinaranjoespin/NiFi/nifi-registry-1.19.0/conf/bootstrap.conf > > 2023-01-12 11:07:08,260 INFO [main] > o.apache.nifi.registry.bootstrap.Command Apache NiFi Registry is currently > running, listening to Bootstrap on port 42503, PID=15011 > > 11:07 edinaranjoespin@EFNARANJO-LT:bin $./nifi-registry.sh status > > Java home: /usr/lib/jvm/java-11-openjdk-amd64/ > NiFi Registry home: /home/edinaranjoespin/NiFi/nifi-registry-1.19.0 > > Bootstrap Config File: > /home/edinaranjoespin/NiFi/nifi-registry-1.19.0/conf/bootstrap.conf > > 2023-01-12 11:07:12,839 INFO [main] > o.apache.nifi.registry.bootstrap.Command Apache NiFi Registry is currently > running, listening to Bootstrap on port 42503, PID=15011 > > 11:07 edinaranjoespin@EFNARANJO-LT:bin $./nifi-registry.sh status > > Java home: /usr/lib/jvm/java-11-openjdk-amd64/ > NiFi Registry home: /home/edinaranjoespin/NiFi/nifi-registry-1.19.0 > > Bootstrap Config File: > /home/edinaranjoespin/NiFi/nifi-registry-1.19.0/conf/bootstrap.conf > > 2023-01-12 11:07:17,734 INFO [main] > o.apache.nifi.registry.bootstrap.Command Apache NiFi Registry is currently > running, listening to Bootstrap on port 42503, PID=15011 > > 11:07 edinaranjoespin@EFNARANJO-LT:bin $./nifi-registry.sh status > > Java home: /usr/lib/jvm/java-11-openjdk-amd64/ > NiFi Registry home: /home/edinaranjoespin/NiFi/nifi-registry-1.19.0 > > Bootstrap Config File: > /home/edinaranjoespin/NiFi/nifi-registry-1.19.0/conf/bootstrap.conf > > 2023-01-12 11:07:24,044 INFO [main] > o.apache.nifi.registry.bootstrap.Command Apache NiFi Registry is not running > > > Additionally, I send the logs and the files nifi-registry.properties and > authorizers.xml > > Best Regards, > ------------------------------ > *From: *"Nathan Gough" <thena...@apache.org> > *To: *"dev" <dev@nifi.apache.org> > *Cc: *"ANTHONY YOSHIHITO ADACHI CORDERO" <aada...@telconet.ec>, "EDISON > FABRICIO NARANJO ESPIN" <efnara...@telconet.ec> > *Sent: *Thursday, January 12, 2023 10:03:08 AM > *Subject: *Re: Problem with NIFI registry using ssl certificates > > Those parts of the config look fine. > Can you share more of the failure log message and/or your > nifi-registry.properties file? > > > > On Thu, Jan 12, 2023, 9:34 AM EDISON FABRICIO NARANJO ESPIN < > efnara...@telconet.ec> wrote: > >> Dear Nathan >> >> This is the configuration >> >> nifi.registry.web.http.host= >> nifi.registry.web.http.port= >> nifi.registry.web.https.host=127.0.0.1 >> nifi.registry.web.https.port=19443 >> >> >> Best Regards, >> ------------------------------ >> *From: *"Nathan Gough" <thena...@apache.org> >> *To: *"dev" <dev@nifi.apache.org> >> *Cc: *"EDISON FABRICIO NARANJO ESPIN" <efnara...@telconet.ec>, "ANTHONY >> YOSHIHITO ADACHI CORDERO" <aada...@telconet.ec> >> *Sent: *Wednesday, January 11, 2023 6:35:23 PM >> *Subject: *Re: Problem with NIFI registry using ssl certificates >> >> Hi Edison, >> >> It sounds like your nifi-registry.properties file may have issues. Can >> you share this section of configuration nifi.registry.web.https.host=? >> nifi.registry.web.https.port=? >> >> This guide should be able to help: >> >> https://community.cloudera.com/t5/Community-Articles/Setting-Up-a-Secure-Apache-NiFi-Registry/ta-p/247753 >> <https://fm.telconet.net/fmlurlsvc/?fewReq=:B:JVs5MjYyOSV1PjEtMyVqZz4zMjkzMiVwamRtYnd2cWY+MTE2NDUzOjdnNjE3OjpiMDU1ZzFhZjY1MjdgZTU2YWdhNjUwZmA7ZyV3PjI1NDA3OzMyNTslcmpnPjAzQU1iNE9iMzE6NTE2LjAzQU1iNE9gMzE6NTE2JXFgc3c+ZmVtYnFibWlsQ3dmb2BsbWZ3LWZgJWA+NjEla2dvPjM=&url=https%3a%2f%2fcommunity.cloudera.com%2ft5%2fCommunity-Articles%2fSetting-Up-a-Secure-Apache-NiFi-Registry%2fta-p%2f247753> >> >> There may be more exception information you can share with us that's >> above/below the message you provided. >> >> Nathan >> >> >> On Wed, Jan 11, 2023, 6:21 PM EDISON FABRICIO NARANJO ESPIN < >> efnara...@telconet.ec> wrote: >> >>> Dear, >>> >>> After configuring the security parameters in the nifi registry, its >>> operation cannot be started since the logs indicate that the jetty web >>> server could not be started. Is there a solution for this issue or you must >>> work with a special version of the product so that it can be deployed with >>> https. >>> >>> Attached log output >>> >>> ==> nifi-registry-app_2023-01-11_12.0.log <== >>> at >>> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344) >>> ... 9 common frames omitted >>> Caused by: java.nio.channels.UnresolvedAddressException: null >>> at java.base/sun.nio.ch.Net.checkAddress(Net.java:131) >>> at >>> java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222) >>> at >>> java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:80) >>> ... 10 common frames omitted >>> 2023-01-11 12:56:44,477 INFO [Thread-0] >>> org.apache.nifi.registry.NiFiRegistry Initiating shutdown of Jetty web >>> server... >>> 2023-01-11 12:56:44,479 INFO [Thread-0] >>> o.eclipse.jetty.server.AbstractConnector Stopped >>> ServerConnector@19e4653c{SSL, >>> (ssl, http/1.1)}{localhost :18443} >>> 2023-01-11 12:56:44,479 INFO [Thread-0] org.eclipse.jetty.server.session >>> node0 Stopped scavenging >>> >>> >>> Best regards, >>> -- >>> Edison F. Naranjo E. >>> Seguridad Lógica >>> TELCONET LATAM >>> Cel: +593998608233 >>> Quito-Ecuador >>> efnara...@telconet.ec >>> >>> Toda la información contenida en este correo electrónico es confidencial >>> y podrá ser usada únicamente por los destinatarios. No imprimir a menos que >>> sea imprescindible. >>> >>> >> >> >> -- >> Edison F. Naranjo E. >> Seguridad Lógica >> TELCONET LATAM >> Quito-Ecuador >> efnara...@telconet.ec >> >> >> Toda la información contenida en este correo electrónico es confidencial >> y podrá ser usada únicamente por los destinatarios. No imprimir a menos que >> sea imprescindible. >> >> > > > -- > Edison F. Naranjo E. > Seguridad Lógica > TELCONET LATAM > Quito-Ecuador > efnara...@telconet.ec > > > Toda la información contenida en este correo electrónico es confidencial y > podrá ser usada únicamente por los destinatarios. No imprimir a menos que > sea imprescindible. > >
