--089e0149c50645ec7704f8eb1d07
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir="ltr"><div class="markdown-here-wrapper" id="markdown-here-wrapper-122808" style><p style="margin:1.2em 0px!important">I’d suggest checking your <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;display:inline">/etc/supervisord.conf</code> to be sure that the following two config entries match up:</p>


<pre style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;font-size:1em;line-height:1.2em;margin:1.2em 0px"><code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;display:inline;white-space:pre;overflow:auto;border-top-left-radius:3px;border-top-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radius:3px;border:1px solid rgb(204,204,204);padding:0.5em 0.7em;display:block!important;display:block;padding:0.5em;color:rgb(51,51,51);background-color:rgb(248,248,255);background-repeat:initial initial">[unix_http_server]
file=/tmp/supervisord.sock ; (the path to the socket file)

[supervisorctl]
serverurl=unix:///tmp/supervisord.sock </code></pre><p style="margin:1.2em 0px!important">Matt</p> <p style="margin:1.2em 0px!important"><br>On 9 May 2014 07:52, Paul Fox &lt;<a href="mailto:***@foxharp.boston.ma.us" target="_blank">***@foxharp.boston.ma.us</a>&gt; wrote:<br></p>
<p style="margin:1.2em 0px!important"></p><div class="markdown-here-exclude"><p></p><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

i&#39;m running a relatively old version of supervisor, so if this has<br>
been fixed in a later release, i&#39;ll live with it -- upgrading this<br>
particular system is difficult at the moment.<br>
<br>
i have a supervisord process that&#39;s been running for over 32 days,<br>
since april 6th.  it&#39;s still running, and will happily restart<br>
processes if i kill them manually.  the web interface (on port 9001)<br>
is also working fine.<br>
<br>
but if i try and talk to it with supervisorctl, i get:<br>
<br>
    # supervisorctl status<br>
    unix:///var/tmp/supervisor.sock no such file<br>
<br>
the socket file is indeed not present in /var/tmp.<br>
<br>
this happened sometime between 3:01am yesterday, and 3:01am today.  i<br>
know this because there&#39;s one process i restart every night at that<br>
time via cron, and this morning i got a failure message, whereas<br>
yesterday i did not.<br>
<br>
is this a familar, known, bug?<br>
<br>
since everything&#39;s kind of working right now, i&#39;m happy to leave the<br>
system in this state in case someone has a debugging idea -- i&#39;m not<br>
particularly skilled with python, but can follow directions well.  :-)<br>
<br>
on the other hand, if the answer is &quot;upgrade&quot;, then i&#39;ll just restart<br>
it and see if it happens again.<br>
<br>
paul<br>
<br>
p.s. here&#39;s the fedora version info:<br>
    # yum info supervisor<br>
    Installed Packages<br>
    Name        : supervisor<br>
    Arch        : noarch<br>
    Version     : 3.0<br>
    Release     : 1.fc18<br>
    Size        : 2.5 M<br>
    Repo        : installed<br>