Storm Management and Maintenance - Real-time Analytics with Storm and Cassandra - page 200

Storm logs
The next place to debug if things don't go as expected is the Storm log. First of all, one
needs to know the location for Storm logs, which also update the path on cluster.xml
at storm-0.9.2-incubating.zip\apache-
storm-0.9.2-incubating\logback\cluster.xml :
<appender
class="ch.qos.logback.core.rolling.RollingFileAppender"
name="A1">
<!—update this as below <file>${storm.home}/logs/
${logfile.name}</file> -->
<file>/mnt/app_logs/storm/storm_logs/${logfile.name}</file>
<rollingPolicy
class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
<fileNamePattern>${storm.home}/logs/${logfile.name}.%i
</fileNamePattern>
<minIndex>1</minIndex>
<maxIndex>9</maxIndex>
</rollingPolicy>
<triggeringPolicy
class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
<maxFileSize>100MB</maxFileSize>
</triggeringPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss} %c{1} [%p]
%m%n</pattern>
</encoder>
</appender>
Now the line in bold gets you the path/location where the Storm logs will be created. Let's
take a closer look to find out what kinds of logs are created by different Storm daemons.
The Nimbus node logs can be obtained by using the following commands on shell:
Cd /mnt/my_logs/strom/storm_logs
ls-lart
The listing of the Nimbus log directory is shown in the following screenshot: