[erlang-questions] Lager fatal errors when starting an application using erlsrv, but not werl

[Jim Rosenblum]

Thanks, removing the console back end solves my problem. 

Sent from my iPhone

> On Feb 3, 2015, at 8:59 PM, Sean Cribbs <sean@REDACTED> wrote:
> 
> Hi Jim,
> 
> When you run headless, there is no console/tty/stdio/etc. In Riak, we solve this using run_erl, which creates UNIX FIFO files that can be attached to separately and replace the standard in/out. I suspect there's nothing similar on Windows and this is the problem you're running into. Unfortunately we don't yet run on Windows.
> 
> However, we also found console output to have a significant impact on performance in many cases, so in production deploys we generally exclude it and just send it to a file instead.
> 
>> On Tue, Feb 3, 2015 at 1:47 PM, jim rosenblum <jim.rosenblum@REDACTED> wrote:
>> I have an application that uses Lager. I have created packages for Mac OSx, RedHat, Ubuntu and Windows and I have a problem that *only* manifests itself on Windows when my application is started via erlsrv - starting with werl.exe is fine.
>> 
>> I register the process via the cmd file produced by Rebar, called jc.cmd in my case. 
>> When I start it in a console (i.e., 1> jc.cmd console), all is good, but when I start via '2> jc.cmd start' I get the following errors:
>> 2015-02-03 08:07:31.394 [error] <0.73.0>@lager_handler_watcher:98 Lager fatally failed to install handler lager_console_backend into lager_event, NOT retrying: old_shell
>> 
>> 2015-02-03 08:07:31.394 [warning] <0.68.0>@lager_console_backend:64 Lager's console backend is incompatible with the 'old' shell, not enabling it
>> 
>> The console command uses werl.exe, the start command uses erlsrv.
>> 
>> 
>> 
>> Can anyone help?
>> 
>> 
>> 
>> thanks
>> 
>> 
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
> 
> 
> 
> -- 
> Sean Cribbs <sean@REDACTED>
> Sr. Software Engineer
> Basho Technologies, Inc.
> http://basho.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150204/d357203b/attachment.htm>