[erlang-questions] Problematic error: code server called the unloaded module `init'

[Vincent de Phily]

Hi list,

here's an error I can't quite figure out and started getting on some of my 
servers, as far as I can tell without code change or environement 
modifications :

> $ erlexec -name foo@REDACTED -config foo.config +W w
>
> Crash dump was written to: erl_crash.dump
> The code server called the unloaded module `init'

When I look at the crash dump, I do have 'init' in my modules list, along with 
lots of standard modules (but none of my own modules) :

> =loaded_modules
> Current code: 1064029
> Old code: 0
> =mod:otp_ring0
> Current size: 620
> =mod:init
> Current size: 31160
> =mod:prim_inet
> Current size: 50792
> ...

and an 'init' process :
> =proc:<0.0.0>
> State: Waiting
> Name: init
> Spawned as: otp_ring0:start/2
> Spawned by: []
> Started: Tue Dec 30 23:25:05 2008
> Message queue length: 0
> Number of heap fragments: 0
> Heap fragment data: 0
> Link list: [<0.1.0>, <0.5.0>, <0.4.0>, <0.2.0>]
> Reductions: 4938
> Stack+heap: 377
> OldHeap: 0
> Heap unused: 229
> OldHeap unused: 0
> Program counter: 0xb4b7a250 (init:boot_loop/2 + 32)
> CP: 0x081f4340 (<terminate process normally>)
> arity = 0

(I can provide more of the dump if desired)


I don't know where to begin with this one; google only picked up a 
seemingly-irrelevant thread on this mailinglist. This is a recent erlang 
version. Any ideas ?

-- 
Vincent de Phily