[erlang-questions] noproc file_server_2 when trying to load boot file

[Tristan Sloughter]

I fixed it... My release file was wrong. I had each app listed like:

{kernel,"2.14.5",load},

But once for each app I removed the ', load' and so just had:

{kernel,"2.14.5",load},

It works fine. Odd that systools:make_script creates a boot file fine though
if it can't run it.

Thanks.

2011/10/22 Tristan Sloughter <tristan.sloughter@REDACTED>

> And I do see it loaded if I just run 'erl':
>
> 1> regs().
>
> ** Registered procs on node nonode@REDACTED **
> Name                  Pid          Initial Call                      Reds
> Msgs
> application_controlle <0.6.0>      erlang:apply/2                     437
>  0
> code_server           <0.19.0>     erlang:apply/2                  270601
>  0
> erl_prim_loader       <0.3.0>      erlang:apply/2                  324250
>  0
> error_logger          <0.5.0>      gen_event:init_it/6                220
>  0
> file_server_2         <0.18.0>     file_server:init/1                  85
>  0
> global_group          <0.17.0>     global_group:init/1                 59
>  0
> global_name_server    <0.12.0>     global:init/1                       50
>  0
> inet_db               <0.15.0>     inet_db:init/1                     251
>  0
> init                  <0.0.0>      otp_ring0:start/2                 2614
>  0
> kernel_safe_sup       <0.28.0>     supervisor:kernel/1                 58
>  0
> kernel_sup            <0.10.0>     supervisor:kernel/1               1562
>  0
> rex                   <0.11.0>     rpc:init/1                          35
>  0
> standard_error        <0.21.0>     erlang:apply/2                       9
>  0
> standard_error_sup    <0.20.0>     supervisor_bridge:standar           41
>  0
> user                  <0.24.0>     group:server/3                      36
>  0
> user_drv              <0.23.0>     user_drv:server/2                  450
>  0
>
> 2011/10/22 Tristan Sloughter <tristan.sloughter@REDACTED>
>
>> Nevermind, file_server module registeres as file_server_2:
>>
>> -define(FILE_SERVER, file_server_2).      % Registered name
>>
>>
>> 2011/10/22 Tristan Sloughter <tristan.sloughter@REDACTED>
>>
>>> Though I can point out I actually have no file_server_2...
>>>
>>> find ~/otp/ -name *file_server*
>>> /home/dotcloud/otp/lib/kernel-2.14.4/src/file_server.erl
>>> /home/dotcloud/otp/lib/kernel-2.14.4/ebin/file_server.beam
>>> /home/dotcloud/otp/lib/kernel-2.14.5/src/file_server.erl
>>> /home/dotcloud/otp/lib/kernel-2.14.5/ebin/file_server.beam
>>>
>>> Hmm..
>>>
>>> 2011/10/22 Tristan Sloughter <tristan.sloughter@REDACTED>
>>>
>>>> Right, there isn't much I can do in that respect though since I can't
>>>> get into a shell when loading the boot file.
>>>>
>>>> Thanks,
>>>> Tristan
>>>>
>>>>
>>>> 2011/10/22 Motiejus Jakštys <desired.mta@REDACTED>
>>>>
>>>>> On Sat, Oct 22, 2011 at 10:11:39AM -0500, Tristan Sloughter wrote:
>>>>> > I have a .rel file and successfully create the boot/script files with
>>>>> > systools:make_script but when I try to load the boot file it crashes
>>>>> with an
>>>>> > error I can't find reference too anywhere online. Does anyone have an
>>>>> idea
>>>>> > on what might be wrong?
>>>>> >
>>>>> > $ erl
>>>>> > Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:4:4] [rq:4]
>>>>> > [async-threads:0] [kernel-poll:false]
>>>>> >
>>>>> > Eshell V5.8.5  (abort with ^G)
>>>>> > 1> systools:make_script("ctdemo", [local]).
>>>>> > ok
>>>>> > 2> q().
>>>>> > ok
>>>>> >
>>>>> > $ erl -boot ctdemo
>>>>> > {"init terminating in
>>>>> >
>>>>> do_boot",{noproc,{gen_server,call,[file_server_2,{open,"./.erlang",[read]},infinity]}}}
>>>>>
>>>>> In a nutshell, gen_server is complaining that process file_server_2 is
>>>>> not running.
>>>>>
>>>>> Check application:loaded_applications(), global_registered_names(),
>>>>> appmon:start() for troubleshooting.
>>>>>
>>>>> Hope this helps
>>>>>
>>>>> Motiejus
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111022/c344b7f3/attachment.htm>