<div dir="ltr">Me and Wiger managed to mess up the upgrades for a while, see mnesia rel notes between 4.4.18-4.5.1 otherwise it should work.<div><br></div><div>But bad_object_header might to be something else though..looks like the dets file is corrupt or?</div>
<div><br></div><div>/Dan</div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 19, 2014 at 6:05 AM, Chandru <span dir="ltr"><<a href="mailto:chandrashekhar.mullaparthi@gmail.com" target="_blank">chandrashekhar.mullaparthi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="">On 18 March 2014 21:38, Daniel Dormont <span dir="ltr"><<a href="mailto:dan@greywallsoftware.com" target="_blank">dan@greywallsoftware.com</a>></span> wrote:<br>
</div><div class="gmail_extra"><div class="gmail_quote"><div class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
Can a Mnesia cluster exist across two OTP releases, specifically R15B<br>
and R16B? I'm testing some upgrades here and seeing this error about<br>
two minutes after trying to join a node running R16B to an existing<br>
cluster running R15B:<br></blockquote></div><div><br>The simplest way to test this is to try this on two standalone nodes, one running R15B and the other R16B. I've tried this, and had no problem joining an R15B-1 node into an R16B-2 node.<br>
<br>You say "trying to join", how exactly are you doing this? When a node joins an existing mnesia installation, it should not have a schema of its own.<span class="HOEnZb"><font color="#888888"><br><br></font></span></div>
<span class="HOEnZb"><font color="#888888"><div>Chandru<br></div></font></span><div><div class="h5"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
=ERROR REPORT==== 2014-03-18 17:13:29 ===<br>
Mnesia('<a href="mailto:ejabberd@chat-stg-01.ec2-int.veoci.com" target="_blank">ejabberd@chat-stg-01.ec2-int.veoci.com</a>'): ** ERROR ** (core<br>
dumped to file:<br>
"/var/lib/ejabberd/MnesiaCore.ejabberd@my-node-name_1395_177209_319048")<br>
** FATAL ** Schema update error {{badmatch,<br>
{error,<br>
{bad_object_header,<br>
"/var/lib/ejabberd/schema.DAT"}}},<br>
[{mnesia_dumper,dets_insert,4,<br>
[{file,"mnesia_dumper.erl"},{line,342}]},<br>
{mnesia_dumper,insert_cstruct,5,<br>
[{file,"mnesia_dumper.erl"},{line,1117}]},<br>
{mnesia_dumper,insert_ops,6,<br>
[{file,"mnesia_dumper.erl"},{line,309}]},<br>
{mnesia_dumper,perform_update,4,<br>
[{file,"mnesia_dumper.erl"},{line,292}]},<br>
{mnesia_dumper,update,3,<br>
[{file,"mnesia_dumper.erl"},{line,273}]},<br>
{mnesia_tm,do_commit,3,<br>
[{file,"mnesia_tm.erl"},{line,1780}]},<br>
{mnesia_tm,commit_participant,6,<br>
<br>
[{file,"mnesia_tm.erl"},{line,1699}]}]} [{op,<br>
<br>
merge_schema,<br>
<br>
[{name,<br>
<br>
... etc.<br>
<br>
If not, are there strategies for dealing with such an upgrade? Or is<br>
this caused by something else entirely?<br>
<br>
Thanks,<br>
Dan<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br></blockquote></div><br></div></div></div>