Hi, sorry if this is mildly off-topic, but I'm hoping for some leniency :) I've run different production environments with ZEO + some kind of client + supervisor for ages. I'm using the same setup with Pyramid, but rebooting and starting supervisord stopped working for some reason a while back.
I've been pulling my hair with this so I'm hoping someone here knows a good solution for this. Here's my supervisor conf file running first a ZEO and then a pretty standard Pyramid instance. [unix_http_server] file=%(here)s/../var/supervisor.sock [supervisord] logfile=%(here)s/../var/log/supervisord.log logfile_maxbytes=10MB logfile_backups=20 loglevel=info pidfile=%(here)s/../var/supervisord.pid nodaemon=false [rpcinterface:supervisor] supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface [supervisorctl] serverurl=unix://%(here)s/../var/supervisor.sock [program:m2m] command = %(here)s/../bin/pserve %(here)s/../etc/production.ini redirect_stderr = true stdout_logfile=%(here)s/../var/log/%(program_name)s-%(process_num)01d.log stdout_capture_maxbytes=10MB stdout_logfile_backups=20 [program:zeo] command = %(here)s/../bin/runzeo -C %(here)s/zeo.conf redirect_stderr = true stdout_capture_maxbytes=10MB stdout_logfile_backups=20 ---- After installation I've added supervisord to user crontab with the @reboot statement. I've also tried standard Debian init.d scripts. The result is the same - the ZEO storage fails. If I try to restart it manually, supervisor will raise a "Spawn Error". If i shut down supervisor with supervisorctl shutdown and run supervisord, it works. I've verified that it runs as the correct user. Does anyone have a similar problem or solution? Thanks a lot in advance, Robin -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.