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

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


No need to start another thread.
The solution is to set the supervisor lines to:
__________________________________________________________________________________________

[supervisor]
recipe = collective.recipe.supervisor

port = localhost:9001
user = admin
password = drillococco

programs =
    10 zeoserver ${zeoserver:location}/bin/runzeo ${zeoserver:location}
    20 client1 ${client1:location}/bin/runzope ${client1:location} true
    30 client2 ${client2:location}/bin/runzope ${client2:location} true
    40 varnish ${buildout:directory}/bin/varnish ${buildout:directory} true
    50 pound ${buildout:directory}/bin/poundrun ${buildout:directory} true

__________________________________________________________________________________________________


Thanks a lot Raphael
    Mirto


Raphael Ritz ha scritto:
> Mirto Silvio Busico wrote:
>> Hi all,
>
> Hi Mirto,
>
> I'll comment inline below what I think you are missing.
>
>>
> [..]
>
>
>>
>> programs =
>>    10 zeoserver ${buildout:directory}/bin/zeoserver 
>> ${zeoserver:location}
>
> Change the above to use 'runzeo' instead
>
>>    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
>
>>
>> [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
>
> Does this make a difference?
>
> 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
>
>
>> ______________________________________________________
>>
>> When I start supervisord, supervisorctl says:
>>
>> _______________________________________________________
>> mirto at msb02:/usr/local/Plone/zeocluster$ sudo bin/supervisorctl
>> [sudo] password for mirto:
>> client1                          RUNNING    pid 10248, uptime 0:00:17
>> client2                          RUNNING    pid 10253, uptime 0:00:17
>> pound                            RUNNING    pid 10255, uptime 0:00:17
>> varnish                          FATAL      Exited too quickly 
>> (process log may have details)
>> zeoserver                        FATAL      Exited too quickly 
>> (process log may have details)
>> supervisor> quit
>> _______________________________________________________
>>
>> But ps -el says that there are 2 varnish process and a zeoserver 
>> process running.
>>
>> What I'm doing wrong?
>>
>> Thanks
>>    Mirto
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> _______________________________________________
> Setup mailing list
> Setup at lists.plone.org
> http://lists.plone.org/mailman/listinfo/setup
>

-------------- 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/8df27a8b/mirtosilvio_busico.vcf


More information about the Setup mailing list