Hello, i have problems starting nifi it gives me a 502 Bad Gateway and i saw that they are certificate problems. Could someone tell me how to set up these certificates? Thank you
Hello,
If you need to generate certificates take a look at Security — CogStack-Nifi latest documentation . You will need to edit the env files if you want to customize settings.
NiFi itself takes a bit of time to start, you may need to turn on full logs : NiFi — CogStack-Nifi latest documentation
Hello,
thanks for your reply, i generated the certificates using create-root-ca-cert.sh, do i need to generate others for nifi to work? i also turn on full logs. Could you please tell me all the steps to make cogstack work? thank u
Hello,
That’s perfectly fine, normally after generating create-root-ca-cert.sh you’d need to recreate opensearch certificates too (if you plan to use it) other Security — CogStack-Nifi latest documentation. . You can check the NiFi log and paste it here, you can execute something like : “docker logs -f --tail 1000 cogstack-nifi > my_log_file.txt” to capture the output easily.
Hello, that is what i have in my log file:
20:47:37,016 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [org.apache.nifi.StdErr] to false
20:47:37,016 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [BOOTSTRAP_FILE] to Logger[org.apache.nifi.StdErr]
20:47:37,016 |-INFO in ch.qos.logback.classic.model.processor.RootLoggerModelHandler - Setting level of ROOT logger to WARN
20:47:37,016 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating WARN level on Logger[ROOT] onto the JUL framework
20:47:37,016 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [APP_FILE] to Logger[ROOT]
20:47:37,017 |-INFO in ch.qos.logback.core.model.processor.DefaultProcessor@3745e5c6 - End of configuration.
20:47:37,019 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@5e4c8041 - Registering current configuration as safe fallback point
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.web.https.port]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.web.https.host]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.web.proxy.host]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.remote.input.host]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.remote.input.socket.port]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.remote.input.secure]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.cluster.protocol.is.secure]
File [/root/.nifi-cli.nifi.properties] replacing [baseUrl]
File [/root/.nifi-cli.nifi.properties] replacing [keystore]
File [/root/.nifi-cli.nifi.properties] replacing [keystoreType]
File [/root/.nifi-cli.nifi.properties] replacing [truststore]
File [/root/.nifi-cli.nifi.properties] replacing [truststoreType]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.variable.registry.properties]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.cluster.is.node]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.cluster.node.address]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.cluster.node.protocol.port]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.cluster.node.protocol.max.threads]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.zookeeper.connect.string]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.zookeeper.root.node]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.cluster.flow.election.max.wait.time]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.cluster.flow.election.max.candidates]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.web.proxy.context.path]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.analytics.predict.enabled]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.analytics.predict.interval]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.analytics.query.interval]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.analytics.connection.model.implementation]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.analytics.connection.model.score.name]
File [/opt/nifi/nifi-current/conf/nifi.properties] replacing [nifi.analytics.connection.model.score.threshold]
NiFi running with PID 38.
Java home: /opt/java/openjdk
NiFi home: /opt/nifi/nifi-current
Bootstrap Config File: /opt/nifi/nifi-current/conf/bootstrap.conf
20:47:42,564 |-INFO in ch.qos.logback.classic.LoggerContext[default] - This is logback-classic version 1.3.5
20:47:42,630 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
20:47:42,631 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/opt/nifi/nifi-current/conf/logback.xml]
20:47:43,167 |-INFO in ch.qos.logback.classic.model.processor.ConfigurationModelHandler - Registering a new ReconfigureOnChangeTask ReconfigureOnChangeTask(born:1688413663167)
20:47:43,172 |-INFO in ch.qos.logback.classic.model.processor.ConfigurationModelHandler - Will scan for changes in [file:/opt/nifi/nifi-current/conf/logback.xml]
20:47:43,172 |-INFO in ch.qos.logback.classic.model.processor.ConfigurationModelHandler - Setting ReconfigureOnChangeTask scanning period to 30 seconds
20:47:43,181 |-INFO in ch.qos.logback.classic.model.processor.LoggerContextListenerModelHandler - Adding LoggerContextListener of type [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
20:47:43,227 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating DEBUG level on Logger[ROOT] onto the JUL framework
20:47:43,228 |-INFO in ch.qos.logback.classic.model.processor.LoggerContextListenerModelHandler - Starting LoggerContextListener
20:47:43,236 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [APP_FILE]
20:47:43,236 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
20:47:43,261 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@1790421142 - setting totalSizeCap to 128 GB
20:47:43,267 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@1790421142 - Archive files will be limited to [128 MB] each.
20:47:43,329 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@1790421142 - No compression will be used
20:47:43,331 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@1790421142 - Will use the pattern /opt/nifi/nifi-current/logs/nifi-app_%d{yyyy-MM-dd_HH}.%i.log for the active file
20:47:43,395 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@327b636c - The date pattern is ‘yyyy-MM-dd_HH’ from file name pattern ‘/opt/nifi/nifi-current/logs/nifi-app_%d{yyyy-MM-dd_HH}.%i.log’.
20:47:43,395 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@327b636c - Roll-over at the top of every hour.
20:47:43,410 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@327b636c - Setting initial period to Fri Jun 16 13:07:40 BST 2023
20:47:43,417 |-INFO in c.q.l.core.rolling.SizeAndTimeBasedRollingPolicy@1790421142 - Cleaning on start up
20:47:43,421 |-INFO in c.q.l.core.rolling.helper.TimeBasedArchiveRemover - first clean up after appender initialization
20:47:43,422 |-INFO in c.q.l.core.rolling.helper.TimeBasedArchiveRemover - Multiple periods, i.e. 336 periods, seem to have elapsed. This is expected at application start.
20:47:43,457 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - Active log file name: /opt/nifi/nifi-current/logs/nifi-app.log
20:47:43,457 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[APP_FILE] - File property is set to [/opt/nifi/nifi-current/logs/nifi-app.log]
20:47:43,458 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [USER_FILE]
20:47:43,458 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
20:47:43,459 |-WARN in ch.qos.logback.core.model.processor.ImplicitModelHandler - Ignoring unknown property [maxFileSize] in [ch.qos.logback.core.rolling.TimeBasedRollingPolicy]
20:47:43,460 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1172131546 - setting totalSizeCap to 128 GB
20:47:43,460 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1172131546 - No compression will be used
20:47:43,460 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1172131546 - Will use the pattern /opt/nifi/nifi-current/logs/nifi-user_%d.log for the active file
20:47:43,462 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is ‘yyyy-MM-dd’ from file name pattern ‘/opt/nifi/nifi-current/logs/nifi-user_%d.log’.
20:47:43,462 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight.
20:47:43,463 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Sun Jun 18 11:43:23 BST 2023
20:47:43,463 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1172131546 - Cleaning on start up
20:47:43,464 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[USER_FILE] - Active log file name: /opt/nifi/nifi-current/logs/nifi-user.log
20:47:43,464 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[USER_FILE] - File property is set to [/opt/nifi/nifi-current/logs/nifi-user.log]
20:47:43,464 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [BOOTSTRAP_FILE]
20:47:43,464 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
20:47:43,464 |-WARN in ch.qos.logback.core.model.processor.ImplicitModelHandler - Ignoring unknown property [maxFileSize] in [ch.qos.logback.core.rolling.TimeBasedRollingPolicy]
20:47:43,465 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1616974404 - setting totalSizeCap to 128 GB
20:47:43,465 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1616974404 - No compression will be used
20:47:43,465 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1616974404 - Will use the pattern /opt/nifi/nifi-current/logs/nifi-bootstrap_%d.log for the active file
20:47:43,466 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is ‘yyyy-MM-dd’ from file name pattern ‘/opt/nifi/nifi-current/logs/nifi-bootstrap_%d.log’.
20:47:43,466 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight.
20:47:43,466 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Mon Jul 03 20:47:37 BST 2023
20:47:43,466 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1616974404 - Cleaning on start up
20:47:43,468 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[BOOTSTRAP_FILE] - Active log file name: /opt/nifi/nifi-current/logs/nifi-bootstrap.log
20:47:43,468 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[BOOTSTRAP_FILE] - File property is set to [/opt/nifi/nifi-current/logs/nifi-bootstrap.log]
20:47:43,468 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - Processing appender named [CONSOLE]
20:47:43,468 |-INFO in ch.qos.logback.core.model.processor.AppenderModelHandler - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
20:47:43,472 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi] to DEBUG
20:47:43,472 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating DEBUG level on Logger[org.apache.nifi] onto the JUL framework
20:47:43,474 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.processors] to ERROR
20:47:43,474 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.nifi.processors] onto the JUL framework
20:47:43,474 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.processors.standard.LogAttribute] to ERROR
20:47:43,474 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.nifi.processors.standard.LogAttribute] onto the JUL framework
20:47:43,474 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.processors.standard.LogMessage] to ERROR
20:47:43,474 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.nifi.processors.standard.LogMessage] onto the JUL framework
20:47:43,474 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.controller.repository.StandardProcessSession] to ERROR
20:47:43,474 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.nifi.controller.repository.StandardProcessSession] onto the JUL framework
20:47:43,475 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.zookeeper.ClientCnxn] to ERROR
20:47:43,475 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.zookeeper.ClientCnxn] onto the JUL framework
20:47:43,475 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.zookeeper.server.NIOServerCnxn] to ERROR
20:47:43,475 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.zookeeper.server.NIOServerCnxn] onto the JUL framework
20:47:43,475 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.zookeeper.server.NIOServerCnxnFactory] to ERROR
20:47:43,475 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.zookeeper.server.NIOServerCnxnFactory] onto the JUL framework
20:47:43,475 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.zookeeper.server.NettyServerCnxnFactory] to ERROR
20:47:43,475 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.zookeeper.server.NettyServerCnxnFactory] onto the JUL framework
20:47:43,476 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.zookeeper.server.quorum] to ERROR
20:47:43,476 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.zookeeper.server.quorum] onto the JUL framework
20:47:43,476 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.zookeeper.ZooKeeper] to ERROR
20:47:43,476 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.zookeeper.ZooKeeper] onto the JUL framework
20:47:43,476 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.zookeeper.server.PrepRequestProcessor] to ERROR
20:47:43,476 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.zookeeper.server.PrepRequestProcessor] onto the JUL framework
20:47:43,476 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.controller.reporting.LogComponentStatuses] to ERROR
20:47:43,476 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.nifi.controller.reporting.LogComponentStatuses] onto the JUL framework
20:47:43,477 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.calcite.runtime.CalciteException] to OFF
20:47:43,477 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating OFF level on Logger[org.apache.calcite.runtime.CalciteException] onto the JUL framework
20:47:43,477 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.curator.framework.recipes.leader.LeaderSelector] to OFF
20:47:43,477 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating OFF level on Logger[org.apache.curator.framework.recipes.leader.LeaderSelector] onto the JUL framework
20:47:43,477 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.curator.ConnectionState] to OFF
20:47:43,477 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating OFF level on Logger[org.apache.curator.ConnectionState] onto the JUL framework
20:47:43,477 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.cluster] to ERROR
20:47:43,477 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.nifi.cluster] onto the JUL framework
20:47:43,477 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.server.JettyServer] to ERROR
20:47:43,477 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.nifi.server.JettyServer] onto the JUL framework
20:47:43,478 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.eclipse.jetty] to ERROR
20:47:43,478 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.eclipse.jetty] onto the JUL framework
20:47:43,478 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.springframework] to ERROR
20:47:43,478 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.springframework] onto the JUL framework
20:47:43,481 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.glassfish.jersey.internal.Errors] to ERROR
20:47:43,481 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.glassfish.jersey.internal.Errors] onto the JUL framework
20:47:43,481 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.eclipse.jetty.annotations.AnnotationParser] to ERROR
20:47:43,481 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.eclipse.jetty.annotations.AnnotationParser] onto the JUL framework
20:47:43,482 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [net.schmizz.sshj] to ERROR
20:47:43,482 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[net.schmizz.sshj] onto the JUL framework
20:47:43,482 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.hierynomus.sshj] to ERROR
20:47:43,482 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[com.hierynomus.sshj] onto the JUL framework
20:47:43,482 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.hierynomus.smbj] to ERROR
20:47:43,482 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[com.hierynomus.smbj] onto the JUL framework
20:47:43,482 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [com.amazonaws.services.kinesis] to ERROR
20:47:43,482 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[com.amazonaws.services.kinesis] onto the JUL framework
20:47:43,482 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.atlas] to ERROR
20:47:43,482 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating ERROR level on Logger[org.apache.atlas] onto the JUL framework
20:47:43,483 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.web.security.requests] to INFO
20:47:43,483 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating INFO level on Logger[org.apache.nifi.web.security.requests] onto the JUL framework
20:47:43,483 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting additivity of logger [org.apache.nifi.web.security.requests] to false
20:47:43,483 |-INFO in ch.qos.logback.core.model.processor.AppenderRefModelHandler - Attaching appender named [APP_FILE] to Logger[org.apache.nifi.web.security.requests]
20:47:43,484 |-INFO in ch.qos.logback.classic.model.processor.LoggerModelHandler - Setting level of logger [org.apache.nifi.web.security] to WARN
20:47:43,484 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@15761df8 - Propagating WARN level on Logger[org.apache.nifi.web.security] onto the JUL framework
Hello, thank you. I sent the logs, I’m waiting for an admin to validate my post, when I go to https:localhost:8443 it always gives me a 502 Bad Gateway
I’m a bit confused, I wanted to know something, I saw in the documentation a link to the Nifi site for configuring security, there are 2 ways: securing NiFi with provided certificates and securing Nifi with TLS Toolkit. if i use the first way i should generate the certificates using create_root_ca_cert.sh if i use the second way i should use the nifi_toolkit_security.sh script, which of the 2 should i use to make nifi work?
You would use create_root_ca_cert.sh first, after which you can use nifi_toolkit_security to re-generate the NiFi specific certs and config. I’ll make it more explicit in the docs as this part is covered in two separate sections.
1 Like
Thank you for your reply,
I started all over doing the 2 steps as you said, but it’s the same thing it always gives me 502 bad error and nifi is always restarting.
The nifi logs don’t show any errors, they just show the configurations it’s doing but it never starts the container, the nginx ones shows as error : **[error] 20#20: 24 connect() failed (113: No route to host) while connecting to upstream, client: …, server: nginx.local, request: “GET / HTTP/1.1”, upstream: …", host: “localhost:8443”.
I think its because nifi is always restarting and i don’t know why. I don’t know if the problem is related to the area because I’m in Italy.
I’m trying to do the thesis on this topic but I don’t know if it can work.
I fix the problem by finding that the server was out of memory, i reduce the configured JVM setting for the NiFi process in the nifi-bootsrap.conf file.
2 Likes