From: Claes W. <kl...@hy...> - 2015-10-26 19:36:40
|
Nothing interesting in the yaws error log from that point in time ? /klacke On 2015-10-24 14:58, Leo Liu wrote: > Hi there, > > My yaws was running with node name yaws@192.168.1.100 and then it > crashed, which has the following overview: > > Slogan Kernel pid terminated (application_controller) ({application_terminated,yaws,shutdown}) > Node name 'nonode@nohost' > Crashdump created on Sat Oct 24 20:36:52 2015 > System version Erlang/OTP 18 [erts-7.1] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:10] [hipe] [kernel-poll:true] > Compiled Tue Oct 6 18:48:14 2015 > Taints asn1rt_nif,crypto > Memory allocated 20.6M > Memory maximum > Atoms 14770 > Processes 3 > ETS tables 0 > Timers 0 > Funs 1442 > Calling Thread scheduler:1 > > with only 3 processes: > > <0.0.0> init Running 8253 13656 0 > <0.3.0> erl_prim_loader Waiting 971343 26448 0 > <0.6.0> error_logger Waiting 65542 372312 0 > > To sum up the crashdump doesn't like from yaws on a machine only yaws is > running, i.e. no other erlang nodes. Is there something that yaws does > that causes it to generate useless erl_crash.dump files? This is the > second time such crash dump was generated and I am all very confused. > > The full erl_crash.dump is here: https://bpaste.net/show/fc708a50ec4f > > Thanks, > Leo > > > ------------------------------------------------------------------------------ > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > |