[erlang-questions] Slave node terminating

t ty tty.erlang@REDACTED
Wed Nov 29 19:00:55 CET 2006

What I had was

           -sasl sasl_error_logger '{file, \"/var/log/slave.log}\"

as Args to slave:start_link.

I also traped exit and found the exit status was normal.

For some reason if I used slave:start_link with the embedded Yaws the
slave nodes would terminate but if I use slave:start it works fine (as
in running overnight).

I'll give your options a try.



On 11/29/06, Chandru <chandrashekhar.mullaparthi@REDACTED> wrote:
> On 28/11/06, t ty <tty.erlang@REDACTED> wrote:
> >
> > How can I get the slave nodes to indicate why they are terminating ? I
> > tried running sasl on the slave nodes but did not get any extra info.
> >
> Did you configure sasl to specify where it should write it's log
> files? We have something like this in our sys.config
>  {sasl,         [{error_logger_mf_dir,
> "/export/home/otpuser/blahblah/sasl_logfiles/"},
>                    {error_logger_mf_maxbytes, 100000},
>                    {error_logger_mf_maxfiles, 8}]}
> This then produces binary log files which can be "read" using the rb module.
> Chandru

More information about the erlang-questions mailing list