The right way to do this is I think to not try to use pidproxy at all. Instead
more recent versions of Pound allow you to prevent them from being daemonized
via an option in the config file (which is the right way to run it under
supervisor):
Daemon 0|1
Have Pound run in the foreground (if 0) or as a daemon (if 1).
By default Pound runs as a daemon (detaches itself from the con-
trolling terminal and puts itself in the background). By speci-
fying this option you can force Pound to work like a regular
process. Useful for debugging or if you want to use something
like daemontools.
HTH,
- C
Erik Myllymaki wrote:
> Ron DuPlain wrote:
>> On Wed, Jul 2, 2008 at 10:14 PM, Erik Myllymaki
>> <[EMAIL PROTECTED]> wrote:
>>
>>> I'm using supervisor 3.0a6 on ubuntu 7.04:
>>>
>>> Python 2.4.4 (#2, Mar 7 2008, 03:56:06)
>>> [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2
>>>
>>> It is working very well for controlling zeo, zope clients and varnish
>>> but not quite with pound:
>>>
>>> [program:pound]
>>> command = /opt/intranet/bin/pidproxy.py
>>> /opt/intranet/parts/poundconfig/var/pound.pid
>>> /opt/intranet/parts/poundbuild/sbin/pound -f
>>> /opt/intranet/parts/poundconfig/etc/pound.cfg
>>> process_name = pound
>>> priority = 20
>>> redirect_stderr = true
>>> stdout_logfile = /opt/intranet/var/log/pound.log
>>> stderr_logfile = /opt/intranet/var/log/pound.err
>>>
>>>
>>> This does start pound and pound is running fine, however the supervisor
>>> web interface and supervisorctl report that it has exited.
>>>
>>> Any advice appreciated.
>>>
>>> Thanks,
>>>
>>>
>>> Erik Myllymaki
>>>
>>>
>>>
>> I don't use pound, but I suggest that that you verify the pound.pid
>> file is actually being created by the pound executable, and reflects
>> the actual pid of pound.
>>
>> Also, I presume the line feeds with the command key don't actually
>> appear in the config file; that might cause problems. :-P
>>
>> BTW, the stderr_logfile key is useless with redirect_stderr = true,
>> but that's harmless.
>>
>> I found this blog article which uses supervisord with pound:
>> http://blog.delaguardia.com.mx/index.php?op=ViewArticle&articleId=106&blogId=1
>>
>> """
>> [program:pound]
>> command = bin/pidproxy %(here)s/../parts/pound/var/pound.pid
>> %(here)s/../bin/pound
>> priority = 40
>> redirect_stderr = true
>> """
>>
>
> Thanks for the reply.
>
> I had seen that blog posting and was using it as an example.
>
> It does look like the pid file is created properly:
>
> [EMAIL PROTECTED]:/opt/intranet# ps ax
> 8013 ? Ss 0:00 /opt/intranet/parts/poundbuild/sbin/pound -f
> /opt/intranet/parts/poundconfig/etc/pound.cfg -p
> /opt/intranet/parts/poundconfig/var/pound.pid
> 8014 ? Sl 0:00 /opt/intranet/parts/poundbuild/sbin/pound -f
> /opt/intranet/parts/poundconfig/etc/pound.cfg -p
> /opt/intranet/parts/poundconfig/var/pound.pid
> [EMAIL PROTECTED]:/opt/intranet# cat
> /opt/intranet/parts/poundconfig/var/pound.pid
> 8013
>
>
> (I had forgotten to tell pound where to make the pid file, and I have
> now with the -p option).
>
> _______________________________________________
> Supervisor-users mailing list
> [email protected]
> http://lists.supervisord.org/mailman/listinfo/supervisor-users
>
_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users
