[erlang-questions] Upgrade from R13B02 to R14B03

[Siri Hansen]

Hi Allen!

I have to be honest and say I don't really know how this is supposed to
work. I know that the appup files in kernel and stdlib are intentionally
left empty, since it is never an option to hot-swap code from these
applications - i.e. the emulator must always be restarted. However, it is of
course not ok that systools:make_relup fails due to this! I will investigate
further, but I can not promise a quick answer since most of my colleagues
are on vacation and I definitely need to discuss this...

It would be interesting though, if it is possible, to see your fixed
.appup-files and the resulting relup that caused the second problem with
code loading.

Regards
/siri@REDACTED




2011/7/19 Allen Kim <allen.kim@REDACTED>

> Did make all .appup files for all system applications. I don't see the
> previous errors any more.
> Then, installed erlang otp r14b03 to target machine
> and when I run release_handler:install_release/1 I see the following error.
>
> =ERROR REPORT==== 19-Jul-2011::14:15:36 ===
> Loading of
> /home/tracking/projects/tracking/erlang/lib/inets-5.6/ebin/httpd_manager.beam
> failed: badfile
>
> =ERROR REPORT==== 19-Jul-2011::14:15:36 ===
> beam/beam_load.c(1300): Error loading module httpd_manager:
>   use of opcode 151; this emulator supports only up to 148
>
>
> =ERROR REPORT==== 19-Jul-2011::14:15:36 ===
> beam/beam_load.c(1300): Error loading module tftp_engine:
>   use of opcode 151; this emulator supports only up to 148
>
>
> =ERROR REPORT==== 19-Jul-2011::14:15:36 ===
> Loading of
> /home/tracking/projects/tracking/erlang/lib/inets-5.6/ebin/tftp_engine.beam
> failed: badfile
>
> anyone?
>
> From: Allen Kim <bighostkim@REDACTED>
> Date: Thu, 14 Jul 2011 15:31:22 -0500
> To: "erlang-questions@REDACTED" <erlang-questions@REDACTED>
> Cc: Allen Kim <allen.kim@REDACTED>
> Subject: Upgrade from R13B02 to R14B03
>
> Hi,
>
> I have installed elrang otp R14B03 on my machine.
> Then, I wanted to upgrade erlang otp from R13B02 to R14B03.
>
> I have myapp-1.9.0.rel  like this:
>
> {release,{"tracking","1.9.0"},*{erts,"5.7.3"},*
> [
>    {kernel,"2.13.3"},    {sasl,"2.1.7"},    {stdlib,"1.16.3"},
>  {compiler, "4.6.3", load},    {crypto, "1.6.1", permanent},
>  {edoc,"0.7.6.4", load},    {et,"1.3.2"},
>    {syntax_tools,"1.6.3", load},    {gs,"1.5.10"},    {inets,"5.1.3"},
>  {mnesia,"4.4.11", permanent},    {observer,"0.9.8.1"},    {os_mon,"2.2.3",
> permanent},
>    {otp_mibs,"1.0.5", load},    {snmp,"4.13.5", load},
>  {public_key,"0.3", load},    {ssl,"3.10.4", load},    {tools,"2.6.4",
> load},    {webtool,"0.8.4", load},
>    {xmerl,"1.2.1", load},    {myapp,"1.0.0", load}
> ]}.
>
> and, I have myapp-2.0.0.rel like this:
>
> {release,{"tracking","2.0.0"},*{erts,"5.8.4"},*
> [
>    {kernel,"2.14.4"},    {sasl,"2.1.9.4"},    {stdlib,"1.17.4"},
>  {compiler, "4.7.4", load},    {crypto, "2.0.3", permanent},
>  {edoc,"0.7.8", load},    {et,"1.4.3"},
>    {syntax_tools,"1.6.7.1", load},    {gs,"1.5.13"},    {inets,"5.6"},
>  {mnesia,"4.4.19", permanent},    {observer,"0.9.9"},    {os_mon,"2.2.6",
> permanent},
>    {otp_mibs,"1.0.6", load},    {snmp,"4.20", load},    {public_key,"0.12",
> load},    {ssl,"4.1.5", load},    {tools,"2.6.6.4", load},
>  {webtool,"0.8.8", load},
>    {xmerl,"1.2.9", load},    {myapp,"1.0.0", load}
> ]}.
>
> when I run make_relup command, I see the following error.
>
> error = systools:make_relup("myapp-2.0.0", ["myapp-1.9.0"],
> ["myapp-1.9.0"], [restart_emulator, {path,
> ["/home/allen/releases/1.9.0/lib/*/ebin",
> "/home/allen/applications/*/ebin"]}])
> No release upgrade script entry for kernel-2.14.4 to kernel-2.13.3 in file
> "/home/azoogle/projects/releases/1.9.0/lib/kernel-2.14.4/ebin/kernel.appup"
>
> that appup file looks like this.
> $ cat
> /home/azoogle/projects/releases/1.9.0/lib/kernel-2.14.4/ebin/kernel.appup
> {"2.14.4",[],[]}.
>
> Does it mean do I have to write all .appup files for all application that I
> want to upgrade with erlang version upgrade?
>
> Is there any one who upgraded erlang version with systools:make_relup?
>
> Thanks for your reply in advance
>
> Allen.
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110720/1934bdc7/attachment.htm>