On 12/16/2015 11:09 AM, Jonathan Vanasco wrote:
>
>
> On Wednesday, December 16, 2015 at 3:00:08 AM UTC-5, Robin Harms
> Oredsson wrote:
>
> OK thanks, I'll try to increase logging verbosity some way. The
> permission part is something I've managed to rule out :/
>
>
> Just to be sure.
On Wednesday, December 16, 2015 at 3:00:08 AM UTC-5, Robin Harms Oredsson
wrote:
>
> OK thanks, I'll try to increase logging verbosity some way. The permission
> part is something I've managed to rule out :/
>
Just to be sure... did you switch to the user that supervisor runs as, and
were abl
OK thanks, I'll try to increase logging verbosity some way. The permission
part is something I've managed to rule out :/
Regards,
Robin
2015-12-16 4:54 GMT+01:00 Jonathan Vanasco :
> Then the only things I can think of are:
>
> * user/permissions error on supervisor starting the process
> * an e
Then the only things I can think of are:
* user/permissions error on supervisor starting the process
* an environment variable missing/unset/overwritten in supervisor
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this grou
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
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, an
