Ask the Community
Groups
How do I disable mynotify from running - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Steps to disable mynotify for troubleshooting purposes. Disabling mynotify is not intended to be a standard configuration.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <p>/usr/local/bin/mynotify uses high CPU utilization</p> <p>mynotify is used to monitor file system changes and track them in the /usr/bp/Journal. This information is used to minimize the required backup windows for differential and incremental backups.</p> <h3 data-id="n-a"> </h3> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <p>On Redhat based systems you will need to stop the service.<br><b>chkconfig mynotify off</b></p> <p>Remove the command from starting at boot time:</p> <blockquote class="blockquote"> <p># <b>cd /etc/rc.d/rc5.d/</b></p> <p># <b>rm –f S50notify_fs_event</b></p> </blockquote> <p>Remove the command from starting via crontab:</p> <blockquote class="blockquote"> <p># <b>crontab –e</b></p> <p>Remove the line with the command: <b>/etc/init.d/watchdog -e >/dev/null 2>&1</b></p> <p>to do this move to that line using arrow keys then type the d key twice</p> <p>type <b>:wq </b>to exit the editing session.</p> </blockquote> <p>Now disable the change journal in the linux client's profile:</p> <p> # <b>vi /usr/bp/bpinit/master.ini</b></p> <ol><li>Locate the section <b>[Incremental Forever] </b>and move to the end of the last line in this section.</li></ol><div><img alt="Master.ini UseJournal" src="https://us.v-cdn.net/6032361/uploads/migrated/NPWHSWM7AZKM/eid-ka03r0000015azl-feoid-00n40000003czqx-refid-0em1w000000g2vq." class="embedImage-img importedEmbed-img"></img></div> <ol start="2"><li>Press the <b>i </b>key to enter insert mode.</li> <li>Press <b>[Enter]</b> to add a new line add the following text on this line: <b>UseJournal=False</b> </li> <li>Press <b>[esc]</b> to exit insert mode.</li> <li>Type <b>:wq</b> to save the changes.</li> </ol><p> Finally, stop the mynotify service</p> <p> # <b>/usr/local/bin/mynotify stop</b></p> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p></p> <p>There are internal process that run at boot and at various times ensure that <b>mynotify</b> is running. The job request is also processed with the expectation that mynotify is in use. Killing the <b>mynotify</b> process is not enough.<br><br>You must follow the steps in the Resolution section to stop it from booting, stop it from being invoked, and tell the jobs to not expect the <b>mynotify</b> process for data acquisition.</p> <h2 data-id="notes"><strong>NOTES</strong></h2> <p></p> <p>An <b>Incremental Forever</b> backup strategy should not be used when <b>mynotify</b> is <b>disabled</b>.<br>Either a weekly Full with Daily Incremental or Differential is recommended.</p> <p>For <b>Novell OES</b> systems, <b>mynotify</b> should be disabled.<br>For more information, see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013260138">Linux Change Journal</a>.</p> </article> </main>