relup restart_new_emulator does not work for me

[Allen Kim-2]

Hi, 

I want to upgrade erlang otp from R13B04 to R43B03

I used this start_erl.data and relup(recommended from 

[tracking@openads releases]$ cat new_start_erl.data 

5.8.4 2.0.0

[tracking@openads releases]$ cat current/relup 

{"2.0.0",

 [{"1.9.0",

   [],

   [restart_new_emulator]}],

 [{"1.9.0",

   [],

   [restart_new_emulator]}]

}.

when I run command release_handler:install_release("2.0.0")

I see the node shutting down messages, but I don't see a new node start up.(looks like heart is not starting up a new node).

My HEART_COMMAND is coreect, since I was able to kill the node and I see it starting up again.

The reason why I said restart_new_emulator not working is I could reboot the node with command init:reboot().

Any help would be appreciated.

Allen Kim

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions

[Siri Hansen]

Hi Allen!

Can you see an erl_crash.dump file after this?

Can you start the 5.8.4 emulator manually?

Regards

/siri

2011/8/3 Allen Kim <[hidden email]>

Hi, 

I want to upgrade erlang otp from R13B04 to R43B03

I used this start_erl.data and relup(recommended from 

[tracking@openads releases]$ cat new_start_erl.data 

5.8.4 2.0.0

[tracking@openads releases]$ cat current/relup 

{"2.0.0",

 [{"1.9.0",

   [],

   [restart_new_emulator]}],

 [{"1.9.0",

   [],

   [restart_new_emulator]}]

}.

when I run command release_handler:install_release("2.0.0")

I see the node shutting down messages, but I don't see a new node start up.(looks like heart is not starting up a new node).

My HEART_COMMAND is coreect, since I was able to kill the node and I see it starting up again.

The reason why I said restart_new_emulator not working is I could reboot the node with command init:reboot().

Any help would be appreciated.

Allen Kim

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions

[Allen Kim]

Siri,

No, I don't see erl_crash.dump, or I could not find it.

Yes, I could start 5.8.4 emulator manually.

The weird thing is after I start manually, then I run command, release_handler:install_release("2.0.0")

It gives me an error, which I don't remember.

Now, I decided to upgrade erlang version manually, that means

  previous plan: 

    1. run command release_handler:install_release("2.0.0")

  new plan:       

    1. update RELEASE file manually by changing 1.9.0 old and 2.0.0 permanent

    2. run command init:reboot()

The new plan seems working, but I was curious why the previous plan did not work.

Hope this helps

    

From: Siri Hansen <[hidden email]>
Date: Tue, 9 Aug 2011 08:05:07 -0500
To: Allen Kim <[hidden email]>
Cc: erlang-questions <[hidden email]>
Subject: Re: [erlang-questions] relup restart_new_emulator does not work for me

Hi Allen!

Can you see an erl_crash.dump file after this?

Can you start the 5.8.4 emulator manually?

Regards

/siri

2011/8/3 Allen Kim <[hidden email]>

Hi, 

I want to upgrade erlang otp from R13B04 to R43B03

I used this start_erl.data and relup(recommended from 

[tracking@openads releases]$ cat new_start_erl.data 

5.8.4 2.0.0

[tracking@openads releases]$ cat current/relup 

{"2.0.0",

 [{"1.9.0",

   [],

   [restart_new_emulator]}],

 [{"1.9.0",

   [],

   [restart_new_emulator]}]

}.

when I run command release_handler:install_release("2.0.0")

I see the node shutting down messages, but I don't see a new node start up.(looks like heart is not starting up a new node).

My HEART_COMMAND is coreect, since I was able to kill the node and I see it starting up again.

The reason why I said restart_new_emulator not working is I could reboot the node with command init:reboot().

Any help would be appreciated.

Allen Kim

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions

[Siri Hansen]

Hi again Allen!

When executing a restart_new_emulator instruction, the release_handler changes the heart command to "<start program> $ROOTDIR/releases/new_start_erl.data". The start program defaults to $ROOTDIR/bin/start, unless you have specifically set the 'start_prg' environment variable for the sasl application. 

If you haven't modified this start script (found in you erlang installation), it will do

$ROOTDIR/bin/run_erl -daemon /tmp/ $ROOTDIR/log "exec $ROOTDIR/bin/start_erl $ROOTDIR $RELDIR $START_ERL_DATA" 

i.e. it will start erlang node using run_erl, and log to $ROOTDIR/log - but only if this directory exists. In the log directory you should find erlang.log.*, and run_erl.log - they might give you an indication of what the problem is.

I hope this can be to some help in the investigation.

Regards

/siri

2011/8/9 Allen Kim <[hidden email]>

Siri,

No, I don't see erl_crash.dump, or I could not find it.

Yes, I could start 5.8.4 emulator manually.

The weird thing is after I start manually, then I run command, release_handler:install_release("2.0.0")

It gives me an error, which I don't remember.

Now, I decided to upgrade erlang version manually, that means

  previous plan: 

    1. run command release_handler:install_release("2.0.0")

  new plan:       

    1. update RELEASE file manually by changing 1.9.0 old and 2.0.0 permanent

    2. run command init:reboot()

The new plan seems working, but I was curious why the previous plan did not work.

Hope this helps

    

From: Siri Hansen <[hidden email]>
Date: Tue, 9 Aug 2011 08:05:07 -0500
To: Allen Kim <[hidden email]>
Cc: erlang-questions <[hidden email]>
Subject: Re: [erlang-questions] relup restart_new_emulator does not work for me

Hi Allen!

Can you see an erl_crash.dump file after this?

Can you start the 5.8.4 emulator manually?

Regards

/siri

2011/8/3 Allen Kim <[hidden email]>

Hi, 

I want to upgrade erlang otp from R13B04 to R43B03

I used this start_erl.data and relup(recommended from 

[tracking@openads releases]$ cat new_start_erl.data 

5.8.4 2.0.0

[tracking@openads releases]$ cat current/relup 

{"2.0.0",

 [{"1.9.0",

   [],

   [restart_new_emulator]}],

 [{"1.9.0",

   [],

   [restart_new_emulator]}]

}.

when I run command release_handler:install_release("2.0.0")

I see the node shutting down messages, but I don't see a new node start up.(looks like heart is not starting up a new node).

My HEART_COMMAND is coreect, since I was able to kill the node and I see it starting up again.

The reason why I said restart_new_emulator not working is I could reboot the node with command init:reboot().

Any help would be appreciated.

Allen Kim

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions