[OPEN-ILS-DEV] Ejabberd error

[BUNTON, GLENN]

No luck. So we have begun the installation process again.
1. We installed Ubuntu 12.04 (Precise) in our server room.
2. We provide a static IP address rather than using DHCP. This is the only difference from our previous install which worked fine until Evergreen crashed.
3. We ran all updates before beginning Evergreen related installation processes.
4. We began Opensrf 2.3 installation
5. We get all the way to step 10 - Creat the OpenSRF Jabber users with no errors of any kind. We input the first command - ejabberdctl register router private.localhost <password> (with our chosen password) and we receive the following error: "Can't register user router at private.localhost at node ejabber at sandbox: not_allowed"
(sandbox is the name of the machine)

How can doing everything exactly the same except giving the machine a static IP address rather than using DHCP cause this problem? 

Any more ideas on solutions because I'm now at a loss.

Thanks in advance.

 
________________________________________
From: open-ils-dev-bounces at list.georgialibraries.org [open-ils-dev-bounces at list.georgialibraries.org] on behalf of Sharp, Chris [csharp at georgialibraries.org]
Sent: Friday, April 11, 2014 7:44 AM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] Ejabberd error

Hi Glenn,

----- Original Message -----
> From: "GLENN BUNTON" <BUNTONGA at mailbox.sc.edu>
> To: "Evergreen Development Discussion List" <open-ils-dev at list.georgialibraries.org>
> Sent: Friday, April 11, 2014 7:08:24 AM
> Subject: Re: [OPEN-ILS-DEV] Ejabberd error
>
> Ben, this is, in fact, our case. We installed and configured
> initially and got it up and running using DHCP so we did everything
> localhost. Then we had to move the box to our server room where we
> gave it an official IP. The strange thing is that Evergreen still
> ran correctly after that.

If you had happened to restart ejabberd or rebooted the server after changing the hostname, you would have seen this problem happen then.  ejabberd was still running with the "old" hostname's configuration in memory.

> We had people working on it from the
> desktop clients. Then one of our staff ran into a problem checking
> on some records that locked the system up completely. We had to
> reboot and that is when the problem occurred. I'll check through the
> archive of the list to look at the email thread you mention. Thanks.

These links may help:

http://www.process-one.net/docs/ejabberd/guide_en.html#htoc77
http://lists.jabber.ru/pipermail/ejabberd/2011-May/006777.html

I did this myself recently (on a test server), so I know your pain!

Hope that's helpful!

Chris

--
Chris Sharp
PINES System Administrator
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, Georgia 30345
(404) 235-7147
csharp at georgialibraries.org
http://pines.georgialibraries.org/