@Dilan86 ,   You can try enabling Kerberos debug log and waiting for it to happen again: -Dsun.security.krb5.debug=true   What kind of applications is this? Is it a long running application? Have you noticed any patterns like "the application fails after running for x hours/days"?   André ... View more

@Dilan86 ,   If the application is not being affected and you only see this a few times a month, I wouldn't worry about it. It might be due to some intermittent issue, like network connectivity glitches, for example.   Unless it's hurting I would just ignore it.   André   ... View more

@Dilan86    Are you specifying a jaas.conf file for your application, through the java.security.auth.login.config property? If so, could you please provide the configuration in it?   If not, create a file with your authentication details (principal and keytab) like the example below, save in a location that the application has access to and pass that property to the application using -Djava.security.auth.login.config=/path/to/jaas.conf   Client { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true keyTab="/path/to/appuser.keytab" storeKey=true useTicketCache=false principal="appuser@YOUR-REALM"; };   Cheers, André     ... View more

Hi, @templarian ,   Instead of changing the root log level, you can modify it for a single class or package using the following entry (one for each class/package): <logger name="com.sun.mail.smtp" level="DEBUG" additivity="false"> <appender-ref ref="APP_FILE"/> </logger>   Also note that if your configuration file has configuration scan enabled with the following, NiFi will scan the logback.xml file at the specified interval and if there are changes to it it will reload the configuration without the need for a restart: # beggining of file <configuration scan="true" scanPeriod="30 seconds"> ... </configuration> # end of file   Cheers, André ... View more

@CookieCream ,   Which Java version to you have in your machine? Could you please run the following command and provide the output?   java -version Cheers, André   ... View more

The number of columns in the schema doesn't actually need to be exact if you're happy to ignore the ones after the last one specified in the schema. ... View more

Hi, @sachin_32 ,   I guess this is coming as a CSV file, right? You can achieve what you want with the following approach:   Configure your CSV Reader to ignore and skip the header line (if any) Configure your CSV Read to use the following schema:   { "type": "record", "name": "SensorReading", "namespace": "com.cloudera.example", "doc": "This is a sample sensor reading", "fields": [ { "name": "c1", "type": "string" }, { "name": "c2", "type": "string" }, { "name": "c3", "type": "string" } ] }​     Ensure you use a schema with the exact number of columns that your input file has.   In your QueryRecord you can then refer to the columns as c1, c2, etc...:   select c1, c2, c3 from flowfile​         Cheers, André   ... View more

@yagoaparecidoti    Are you able to access Cloudera Manager from your browser?   André   ... View more

@Abhishek27Apple ,   Could you also please share the SAML properties in your nifi.properties file?   André ... View more