ZEO never really starts - supervisor raises a "Spawn Error". So no, nothing in the logs either. I've tried priority too, as far as i understand it doesn't really matter. The key part here is that it works if i exit it and simply start it again manually or with an init script. It has something to do with the boot process I'm guessing. But since I don't get any other useful error messages, and AFAIK spawn errors shouldn't occur unless i try to launch more than 1024 instances...
The problem didn't occur prior to supervisor v3.0 i think. Regards, Robin 2015-12-15 18:29 GMT+01:00 Jonathan Vanasco <jonat...@findmeon.com>: > What does "zeo storage fails" mean? Is the service not starting, is > pyramid not connecting to it? > > Have the logs suggested anything ? > > Anyways, I'm unclear if there is a race condition involved between the > storage engine and your pyramid app. If pyramid needs the storage engine > to start up, and thereby needs to run AFTER zeo (I assume this might be > happening), then you can use a `priority` config setting on each app to > affect the startup/shutdown order. > > > -- > 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 pylons-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/pylons-devel. > For more options, visit https://groups.google.com/d/optout. > -- Betahaus phone: +46 70-333 00 10 web: http://www.betahaus.net -- 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 pylons-devel@googlegroups.com. Visit this group at https://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
