O $8.1.3 $HTTPRead – Crashes Omnis (Unknown WebEnabler error -1192)
On Tue, Dec 12, 2017 at 4:11 AM, Tech <firstname.lastname@example.org> wrote:
> Hi Kelly
> I also think it’s a socketing issue.
> I’ll test more tomorrow but this thread provides a hint about the
> contemporaneous console error.
> Service exited due to signal: Broken pipe 13
A “Broken pipe 13” is unlikely to be the cause of your problems. It’s
likely to be an effect of the daemon dying, though the wording of the error
implies otherwise. SIGPIPE just means that writing failed because there
were no processes left which could read from the pipe. I see that error
sometimes when I kill the built-in Django development server with a Ctrl-C
and it’s not a big deal at all.
If the AppNap thing that others have mentioned doesn’t do the trick, you
may want to instrument Omnis with dtrace to see what Omnis is up to when it
dies. See this: < 8thlight.com/blog/colin-jones/2015/11/06/dtrace-even-better-than-strace-for-osx.html
Manage your list subscriptions at lists.omnis-dev.com