[Setup] Re: How to use supervisor in the unified installer buildout?

Mirto Silvio Busico mirtosilvio.busico at fastwebnet.it
Tue Jun 9 12:29:21 UTC 2009


Raphael Ritz ha scritto:
> Mirto Silvio Busico wrote:
>> Hi all,
>
> Hi Mirto,
>
> I'll comment inline below what I think you are missing.
Hi Raphael,
I tried and, see below.
>
>>
> [..]
>
>
>>
>> programs =
>>    10 zeoserver ${buildout:directory}/bin/zeoserver 
>> ${zeoserver:location}
>
> Change the above to use 'runzeo' instead
Well the unified installe buildout doesn't generate any runzeo
In the bin directory I have:
buildout  clusterstatus.sh  pound-build   poundrun           
restartcluster.sh   supervisorctl  zeopack
client1   paster            poundcontrol  repozo             
shutdowncluster.sh  supervisord    zeoserver
client2   plonectl          poundctl      restartclients.sh  
startcluster.sh     varnish        zopepy

Which one I have to use? Or I have to change the buildout.cfg?
>
>>    20 client1 ${buildout:directory}/bin/client1 ${client1:location}
>>    30 client2 ${buildout:directory}/bin/client2 ${client2:location}
>>    40 varnish ${buildout:directory}/bin/varnish ${buildout:directory}
>>    50 pound ${buildout:directory}/bin/poundrun ${buildout:directory}
>
> To these four above add 'true' to the call
Done
now I have:
programs =
    10 zeoserver ${buildout:directory}/bin/zeoserver 
${zeoserver:location} (I'll correct later)
    20 client1 ${buildout:directory}/bin/client1 ${client1:location} true
    30 client2 ${buildout:directory}/bin/client2 ${client2:location} true
    40 varnish ${buildout:directory}/bin/varnish ${buildout:directory} true
    50 pound ${buildout:directory}/bin/poundrun ${buildout:directory} true

>
>>
>> [varnish-build]
>> recipe = zc.recipe.cmmi
>> url = http://downloads.sourceforge.net/varnish/varnish-2.0.2.tar.gz
>>
>> [varnish]
>> recipe = plone.recipe.varnish
>> daemon = ${buildout:directory}/parts/varnish-build/sbin/varnishd
>> bind = 0.0.0.0:8000
>> backends = 127.0.0.1:8001
>> telnet = 127.0.0.1:8002
>> cache-size = 1G
>
> add: mode = foreground
Done
>
> Does this make a difference?
Well, seems that now varnish starts correctly, but there are a lot of 
other problems: pound doesn't start and client1 client2 seems started 
but the instances doesn't respond.
I'll start another tread because the problem is: the scripts generated 
by the unified installers are not usable as supervisor commands.
>
> BTW: all these changes are to make sure that the processes managed
> by supervisor are run in foreground mode to enable supervisor to
> take care of the daemonizing itself.
>
> HTH
>
>     Raphael
Thanks
    Mirto

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mirtosilvio_busico.vcf
Type: text/x-vcard
Size: 272 bytes
Desc: not available
Url : http://lists.plone.org/pipermail/setup/attachments/20090609/cb09fa9d/mirtosilvio_busico.vcf


More information about the Setup mailing list