[OPEN-ILS-GENERAL] Building on Amazon EC2; Hostname Issues

[Stephen Wills]

I just spent the weekend playing with EG 2.0.1 on Ubuntu 10.10 on a  
couple of EC2 AMI's

This is a note for others still learning about Evergreen.   Erlang,  
the E in ejabberd, uses a default configuration file while ejabberd is  
starting up, which, among other things sets up the default node for  
the ejabber server.  On an Amazon EC2 slice, the first time this runs,  
it computes the default jabber node and stores it in a mnesia database.

When you stop and then restart your EC2 instance, this default  
behavior computes a new node name for your jabber which then crashes  
with a mismatch error against the previous name in the mnesia database.

To correct this annoyance, one can explicitly name the ERLANG_NODE in / 
etc/default/ejabberd as Raymond noted last June in the included post.

A helpful post on this is:
http://blog.kenweiner.com/2008/05/ejabberd-on-amazon-ec2-ubuntu-ami.html

I hope this helps someone,
Stev3

On Jan 11, 2011, at 11:23 AM, Dan Scott wrote:

> Hi Christinger:
>
> On Tue, Jan 11, 2011 at 06:22:36AM -0500, Christinger Tomer wrote:
>> I'm trying to get Evergreen 1.6.1.6 running under Ubuntu 10.04 on  
>> Amazon
>> EC2. After wrestling with ejabberd, I have Evergreen running, but  
>> when I try
>
> Can you describe the nature of your "wrestling" with ejabberd? This
> might be pertinent to debugging the problem you're running into.
>
> To confirm that you have Evergreen running successfully: can you use  
> the
> "login" command from srfsh?

On Jun 8, 2010, at 2:58 PM, Raymond Norton wrote:

> Can you post your ejabberd.cfg file? Syntax errors there can cause
>> significant and perplexing pain with ejabberd.
>>
>>
>
> I backtracked,  and for good measure added "echo  
> 'ERLANG_NODE=ejabberd at localhost' >> /etc/default/ejabberd"
>
> That is what fixed it. I had skipped it earlier because I was not  
> getting errors.
>
> Thanks for the reply.
>
>