<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>The Wombelix Post - Debug</title><link href="https://dominik.wombacher.cc/" rel="alternate"/><link href="/feeds/tag_debug.atom.xml" rel="self"/><id>https://dominik.wombacher.cc/</id><updated>2021-05-12T00:00:00+02:00</updated><entry><title>Sophos Anti-Virus for Linux - Hidden On-Access Scan debug option</title><link href="https://dominik.wombacher.cc/posts/sophos-anti-virus-for-linux-hidden-on-access-scan-debug-option.html" rel="alternate"/><published>2021-05-12T00:00:00+02:00</published><updated>2021-05-12T00:00:00+02:00</updated><author><name>Dominik Wombacher</name></author><id>tag:dominik.wombacher.cc,2021-05-12:/posts/sophos-anti-virus-for-linux-hidden-on-access-scan-debug-option.html</id><summary type="html">&lt;!-- SPDX-FileCopyrightText: 2023 Dominik Wombacher &lt;dominik@wombacher.cc&gt; --&gt;
&lt;!--  --&gt;
&lt;!-- SPDX-License-Identifier: CC-BY-SA-4.0 --&gt;
&lt;p&gt;I had to learn that it can be quite challenging to troubleshoot performance issues related Sophos Anti-Virus for Linux or to identify paths with high I/O load that might  ... &lt;a class="read-more" href="/posts/sophos-anti-virus-for-linux-hidden-on-access-scan-debug-option.html"&gt; [read more]&lt;/a&gt;&lt;/p&gt;</summary><content type="html">&lt;!-- SPDX-FileCopyrightText: 2023 Dominik Wombacher &lt;dominik@wombacher.cc&gt; --&gt;
&lt;!--  --&gt;
&lt;!-- SPDX-License-Identifier: CC-BY-SA-4.0 --&gt;
&lt;p&gt;I had to learn that it can be quite challenging to troubleshoot performance issues related Sophos Anti-Virus for Linux or to identify paths with high I/O load that might require an adjusted Policy or even Exclude.&lt;/p&gt;
&lt;p&gt;In a Situation were SAV processes generate 100% load on one or more CPU Cores, there is definitely something wrong that need a closer look.&lt;/p&gt;
&lt;p&gt;Sophos does provide a lot of config settings but just very limited debug capabilities, at least when you trust the official manual and knowledge base.&lt;/p&gt;
&lt;p&gt;But there is a hidden and not public documented config setting to log all On-Access Scan activities. For sure that might generate a huge amount of data and therefore should only activated a limited time during an ongoing troubleshooting session.&lt;/p&gt;
&lt;p&gt;Activate:&lt;/p&gt;
&lt;pre class="code text literal-block"&gt;
/opt/sophos-av/bin/savconfig set OnAccessRecordAllScans enable

systemctl restart sav-protect

&lt;/pre&gt;
&lt;p&gt;Log files will be written to &lt;strong&gt;/opt/sophos-av/tmp/&lt;/strong&gt;, you should stop &lt;em&gt;sav-protect&lt;/em&gt; and copy the logs to another location before deativating the debug mode.&lt;/p&gt;
&lt;p&gt;Deactivate:&lt;/p&gt;
&lt;pre class="code text literal-block"&gt;
/opt/sophos-av/bin/savconfig set OnAccessRecordAllScans disable

systemctl restart sav-protect

&lt;/pre&gt;
&lt;p&gt;It would actually be way easier if Sophos would cover such topics in their own documentation.&lt;/p&gt;
</content><category term="Misc"/><category term="Sophos"/><category term="Anti-Virus"/><category term="Linux"/><category term="Debug"/></entry></feed>