<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Firewall message log file in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/101340#M19657</link>
    <description>&lt;P&gt;What is the proper way to run e2fsck during a maintenance window? Unfortunately, I have yet to find any official documentation on how to properly run a file system check so any direction is greatly appreciated.&lt;/P&gt;&lt;P&gt;I've found &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk92442" target="_self"&gt;sk92442&lt;/A&gt; that indicates fsck can be ran from maintenance mode. I've also found an &lt;A href="https://www.cpug.org/forums/showthread.php/22756-fsck-on-the-next-reboot-in-R77-30" target="_self"&gt;old forum post&lt;/A&gt; that indicates fsck can be run doing the boot process if it's been long enough between checks. Being that my firewall has an uptime of 708 days, I'm guessing that a reboot will likely check the file system upon boot and resolve this error? Or is unmounting the filesystem and running fsck manually the way to go?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am aware of the extremely high uptime, these units will be upgraded to R80.40 soon.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Expert@FW01]# tune2fs -l /dev/mapper/vg_splat-lv_current | egrep -i 'check|mount'&lt;BR /&gt;Last mounted on: &amp;lt;not available&amp;gt;&lt;BR /&gt;Default mount options: (none)&lt;BR /&gt;Last mount time: Wed Nov 28 19:23:32 2018&lt;BR /&gt;Mount count: 3&lt;BR /&gt;Maximum mount count: 39&lt;BR /&gt;Last checked: Wed Nov 28 18:59:43 2018&lt;BR /&gt;Check interval: 15552000 (6 months)&lt;BR /&gt;Next check after: Mon May 27 19:59:43 2019&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;[Expert@FW01]# uptime&lt;BR /&gt;12:20:58 up 708 days, 16:57, 5 users, load average: 0.80, 0.85, 0.82&lt;/P&gt;&lt;DIV class="SnapLinksContainer"&gt;&lt;DIV class="SL_SelectionRect"&gt;&lt;DIV class="SL_SelectionLabel"&gt;0 Links&lt;/DIV&gt;&lt;/DIV&gt;&lt;!--  Used for easily cloning the properly namespaced rect  --&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 06 Nov 2020 20:36:43 GMT</pubDate>
    <dc:creator>lbcadenco10</dc:creator>
    <dc:date>2020-11-06T20:36:43Z</dc:date>
    <item>
      <title>Firewall message log file</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/47051#M9160</link>
      <description>&lt;P&gt;I have seen the following messages in /var/log/messages on a&amp;nbsp;23500 system running R77.30, which appears to be a Linux related message rather then Checkpoint. Do I need to worry about this?&lt;/P&gt;&lt;P&gt;ar 12 18:40:33 2019 &lt;FONT color="#ffffff"&gt;slgadca1&lt;/FONT&gt; kernel: kjournald starting.&amp;nbsp; Commit interval 5 seconds&lt;BR /&gt;Mar 12 18:40:33 2019 &lt;FONT color="#ffffff"&gt;slgadca1&lt;/FONT&gt; kernel: EXT3-fs warning: checktime reached, running e2fsck is recommended&lt;BR /&gt;Mar 12 18:40:33 2019 &lt;FONT color="#ffffff"&gt;slgadca1&lt;/FONT&gt; kernel: EXT3 FS on dm-4, internal journal&lt;BR /&gt;Mar 12 18:40:33 2019 &lt;FONT color="#ffffff"&gt;slgadca1&lt;/FONT&gt; kernel: EXT3-fs: mounted filesystem with ordered data mode.&lt;BR /&gt;Mar 12 18:42:49 2019 &lt;FONT color="#ffffff"&gt;slgadca1&lt;/FONT&gt; kernel: device-mapper: table: 253:4: linear: dm-linear: Device lookup failed&lt;BR /&gt;Mar 12 18:42:49 2019&lt;FONT color="#ffffff"&gt; slgadca1&lt;/FONT&gt; kernel: device-mapper: ioctl: error adding target to table&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have white out the device name.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 12:12:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/47051#M9160</guid>
      <dc:creator>Craig_Wilkie</dc:creator>
      <dc:date>2019-03-15T12:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall message log file</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/47103#M9170</link>
      <description>I believe these can be safely ignored. May be worth doing an e2fsck during a maintenance window, though.</description>
      <pubDate>Fri, 15 Mar 2019 17:28:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/47103#M9170</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-03-15T17:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall message log file</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/101340#M19657</link>
      <description>&lt;P&gt;What is the proper way to run e2fsck during a maintenance window? Unfortunately, I have yet to find any official documentation on how to properly run a file system check so any direction is greatly appreciated.&lt;/P&gt;&lt;P&gt;I've found &lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk92442" target="_self"&gt;sk92442&lt;/A&gt; that indicates fsck can be ran from maintenance mode. I've also found an &lt;A href="https://www.cpug.org/forums/showthread.php/22756-fsck-on-the-next-reboot-in-R77-30" target="_self"&gt;old forum post&lt;/A&gt; that indicates fsck can be run doing the boot process if it's been long enough between checks. Being that my firewall has an uptime of 708 days, I'm guessing that a reboot will likely check the file system upon boot and resolve this error? Or is unmounting the filesystem and running fsck manually the way to go?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am aware of the extremely high uptime, these units will be upgraded to R80.40 soon.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Expert@FW01]# tune2fs -l /dev/mapper/vg_splat-lv_current | egrep -i 'check|mount'&lt;BR /&gt;Last mounted on: &amp;lt;not available&amp;gt;&lt;BR /&gt;Default mount options: (none)&lt;BR /&gt;Last mount time: Wed Nov 28 19:23:32 2018&lt;BR /&gt;Mount count: 3&lt;BR /&gt;Maximum mount count: 39&lt;BR /&gt;Last checked: Wed Nov 28 18:59:43 2018&lt;BR /&gt;Check interval: 15552000 (6 months)&lt;BR /&gt;Next check after: Mon May 27 19:59:43 2019&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;[Expert@FW01]# uptime&lt;BR /&gt;12:20:58 up 708 days, 16:57, 5 users, load average: 0.80, 0.85, 0.82&lt;/P&gt;&lt;DIV class="SnapLinksContainer"&gt;&lt;DIV class="SL_SelectionRect"&gt;&lt;DIV class="SL_SelectionLabel"&gt;0 Links&lt;/DIV&gt;&lt;/DIV&gt;&lt;!--  Used for easily cloning the properly namespaced rect  --&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 06 Nov 2020 20:36:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/101340#M19657</guid>
      <dc:creator>lbcadenco10</dc:creator>
      <dc:date>2020-11-06T20:36:43Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall message log file</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/101479#M19684</link>
      <description>&lt;P&gt;Follow the SK recommendations, ignore CPUG discussion&lt;/P&gt;</description>
      <pubDate>Mon, 09 Nov 2020 10:30:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Firewall-message-log-file/m-p/101479#M19684</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2020-11-09T10:30:42Z</dc:date>
    </item>
  </channel>
</rss>

