<?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: System crash leaves stagnant pidfile in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116046#M99750</link>
    <description>&lt;P&gt;Awesome thanks. I wouldn't have even noticed except I'm running it in vmware workstation and my laptop has problems hibernating.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Sep 2016 18:08:28 GMT</pubDate>
    <dc:creator>chirss</dc:creator>
    <dc:date>2016-09-26T18:08:28Z</dc:date>
    <item>
      <title>System crash leaves stagnant pidfile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116038#M99748</link>
      <description>&lt;P&gt;In my setup if I have a os/system crash, it leaves behind a stagnant pidfile. This makes sense. However on startup minemeld is set up to start at boot/runlevel 3 or whatever run level. It seems the stagnant pidfile does not in fact get cleaned up so the processes do not start.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the pidfile were stored in /run then this would not be the fact since it is mounted as tmpfs as far as I understand it. Is this something which could be modified to account for the above scenario with stale pidfiles?&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2016 16:40:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116038#M99748</guid>
      <dc:creator>chirss</dc:creator>
      <dc:date>2016-09-26T16:40:24Z</dc:date>
    </item>
    <item>
      <title>Re: System crash leaves stagnant pidfile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116042#M99749</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/47112"&gt;@chirss﻿&lt;/a&gt;&amp;nbsp;you are right, it was an oversight on my side. I would create a directory owned by minemeld user in /run and replace /opt/minemeld/local/supervisor/run with a symbolic link to that directory. Or wait for the next update where I will fix this &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks !&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2016 16:59:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116042#M99749</guid>
      <dc:creator>lmori</dc:creator>
      <dc:date>2016-09-26T16:59:16Z</dc:date>
    </item>
    <item>
      <title>Re: System crash leaves stagnant pidfile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116046#M99750</link>
      <description>&lt;P&gt;Awesome thanks. I wouldn't have even noticed except I'm running it in vmware workstation and my laptop has problems hibernating.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2016 18:08:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116046#M99750</guid>
      <dc:creator>chirss</dc:creator>
      <dc:date>2016-09-26T18:08:28Z</dc:date>
    </item>
    <item>
      <title>Re: System crash leaves stagnant pidfile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116677#M99751</link>
      <description>&lt;P&gt;Should be fixed in the new version of the base apt package, auto update should automatically install it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2016 14:07:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116677#M99751</guid>
      <dc:creator>lmori</dc:creator>
      <dc:date>2016-09-29T14:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: System crash leaves stagnant pidfile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116971#M99752</link>
      <description>&lt;P&gt;Do I need to do anything after running dist-upgrade and it completing?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2016 14:39:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116971#M99752</guid>
      <dc:creator>chirss</dc:creator>
      <dc:date>2016-09-30T14:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: System crash leaves stagnant pidfile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116974#M99753</link>
      <description>&lt;P&gt;Hi chirsf,&lt;/P&gt;
&lt;P&gt;to update MineMeld you can simply run "sudo /usr/sbin/minemeld-auto-update", this is also referenced in a daily cron job so chance are your system was already up to date.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you have run a dist-upgrade you can check if the apt base package has been updatded (dpkg -l | grep minemeld), it should show version 0.9.6-1. Upgrading the base package automatically updates the MineMeld code, you can check if you are running the latest release (0.9.24) by doing &amp;nbsp;a "ls -l /opt/minemeld/engine". You should find symbolic link named "current" pointing to the directory 0.9.24.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2016 15:05:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/system-crash-leaves-stagnant-pidfile/m-p/116974#M99753</guid>
      <dc:creator>lmori</dc:creator>
      <dc:date>2016-09-30T15:05:50Z</dc:date>
    </item>
  </channel>
</rss>

