TR: [OPEN-ILS-DEV] Re:RE: Ejabberd and Ubuntu
John Fink
john.fink at gmail.com
Fri Oct 19 14:23:21 EDT 2007
Pierre,
I have successfully installed 1.2RC2 (and, provided everything is ship
shape, 1.2 stable this afternoon) on Ubuntu Server 7.04. I hit some snags
that were things I did wrong, but the two Ubuntu instruction sheets work
okay.
jf
On 10/19/07, Roberge, Pierre <roberge.pierre at uqam.ca> wrote:
>
>
>
> Hi Dan,
>
>
>
> Sorry to interfere in this discussion but after reading your last post, a
> question arises:
>
>
>
> Has anybody been able to install successfully Evergreen on Ubuntu 7.04following the instructions available on the Wiki? You indicated that you
> face these problems with Ubuntu 6.10. Now, if instructions have been
> written for 7.04, I suppose this implies that the installation is feasible
> on that distribution. Am I wrong? Should we abandon this path and try a new
> install on Gentoo instead?
>
>
>
> Thanks,
>
> _________________________________________________________
>
>
>
>
>
> *Pierre Roberge***
>
> Directeur des technologies de l'information
>
> Service des bibliothèques
>
> *Université du Québec à Montréal***
>
> Case postale 8889, succ. Centre-Ville
>
> Montréal, Qc
>
> H3C 3P3
>
> Téléphone: 514-987-3000 #3163
>
> Télécopieur: 514-987-0285
>
> Courriel: roberge.pierre at uqam.ca
>
>
> ------------------------------
>
> *De :* open-ils-dev-bounces at list.georgialibraries.org [mailto:
> open-ils-dev-bounces at list.georgialibraries.org] *De la part de* Dan Scott
> *Envoyé :* 19 octobre 2007 12:52
> *À :* open-ils-dev at list.georgialibraries.org
> *Objet :* Re: [OPEN-ILS-DEV] Re:RE: Ejabberd and Ubuntu
>
>
>
> Hi Pierre:
>
> I don't think your configuration file is at fault; I replaced the
> ejabberd.cfg configuration file on my Gentoo machine with a copy of your
> file, changed one setting (cobaye-ti to my own hostname), and started up
> ejabberd successfully (going on to run Evergreen, etc, without any
> noticeable differences).
>
> Maybe it would be worthwhile uninstalling ejabberd and erlang, and
> installing them again, then copying your configuration file into place and
> registering the users? It seems that the problem you're experiencing is
> entirely at the ejabberd / erlang level (which is sadly the obstacle that
> ultimately caused me to give up on Ubuntu 6.10 back when I was writing the
> install instructions for Ubuntu!).
>
> Dan
>
> On 19/10/2007, *Pierre Nault* <pierrenault at gmail.com > wrote:
>
> Good morning Dan,
>
> On my peregrination in the web to solve this problem, I never heard
> about these strange behaviours: you have to reveal this somewhere !
> Thankfully, Google will harvest this mailing list...
> Apart from that, these little tricks didn't help much : the ejabberd
> server is still dead calm...
> I verified the ejabberd.cfg file for syntax errors (no problem), restart
> and stop ejabberctl and then ejabberd start : still, ejabberd won't work.
> Finally I reboot the machine, did a netstat -l -n : nothing on the ports
> that ejabberd is suppose to listen. Did again the little sequence of
> commands : again nothing from ejabberd.
> This is so strange : before the capital letters problem, ejabberd was
> running nicely...
>
> So I upload the ejabberd.cfg here (http://www.bibliotheques.uqam.ca/flash_bugs/ejabberd_cfg.txt
> ).
>
> Thanks a lot,
>
> Pierre Nault
>
> 2007/10/18, Dan Wells < dbw2 at calvin.edu>:
>
> Pierre,
>
> I am glad (yet also amazed) that the case change fixed your registration
> problem. I do not think you really needed to go through and change all your
> other files and settings, but it shouldn't hurt if it was done
> accurately. As for your recent issues, you almost certainly have some
> syntax error in your ejabberd.cfg file (though I am not sure how it worked
> before). You are also running into some more ejabberd (on Ubuntu at least)
> weirdness, which I will now explain. To start ejabberd, you use the
> command:
>
> sudo /etc/init.d/ejabberd start
>
> which is fine and dandy, but it doesn't complain about syntax errors! It
> loads an erlang process which attempts to start ejabberd, but that part
> silently fails. You are left with a "Started" node but no running server,
> and attempts to register an account give the long nasty erlang error message
> you got. To make matters worse, when you are in this state, the following
> commands:
>
> sudo /etc/init.d/ejabberd stop
> and
> sudo /etc/init.d/ejabberd restart
> and
> sudo /etc/init.d/ejabberd force-reload
>
> NO LONGER WORK. The running node will both refuse to go down and will
> refuse to reload the (presumably) now corrected config file.
>
> Thankfully, there is a solution not involving finding and killing the
> rogue erlang process (which would work as well). For reasons I have never
> bothered to fully look into, the following commands DO WORK:
>
> sudo ejabberdctl restart
> and
> sudo ejabberdctl stop
>
> !!!! So, why not just use ejabberdctl and forget about the 'ejabberd'
> init script altogether? Well, turns out that there is no 'ejabberdctl
> start' command. Hey, don't look at me, I didn't write it :)
>
>
> That leaves us with the problem of finding your syntax error. If you want
> to upload the ejabberd.cfg file we can all take a look, but I would bet
> the line of the hour is the culprit:
>
> {hosts, ["localhost"," cobaye-ti.bib.uqam.ca"]}.
>
> Double check for matching " ",[ ], and { }, and also be aware that the
> period '.' at the end is a requirement.
>
> Once you get ejabberd back together, I would suggest rebooting to clear
> out any half-running parts of the system and try again. Since this is
> obviously just a test machine, sometimes a restart is the easiest way to
> clean the slate.
>
> Good luck,
> DW
>
>
>
> >>> "Pierre Nault" <pierrenault at gmail.com> 10/18/2007 3:27 PM >>>
> Hello Dan,
>
> Yes, it worked : I registered the two accounts, the upper case
> letters
> seems to be the problem. After registering the accounts, I tried to start
> Open SRF but it give me the same error message. Then I remembered that the
> capital letters were everywhere (opensrf.xml, opensrf_core.xml,
> .srfsh.xml).
> I modified these files, restart Opens SRF: same error message. I change
> the
> /etc/hosts and /etc/hostname files, reboot the machine. After that,
> ejabberd
> was dead : the command sudo ejabberdctl status returned:
> Node 'ejabberd at cobaye-ti' is started. Status: started
> ejabberd is not running
> Nothing on any ports (5222, 5223, 5269). Strange, as I just change the
> capital letters. Euh.. this is an entirely new problem.
>
> I tried to register an account, it give me that message:
> RPC failed on the node 'ejabberd at cobaye-ti': {'EXIT',
> {badarg,
> [{erlang,
> port_control,
>
> [stringprep_port,
> 1,
> "
> cobaye-ti.bib.uqam.ca"]},
>
> {stringprep,control,2},
> {jlib,nameprep,1},
> {ejabberd_auth,
> auth_modules,
> 1},
> {ejabberd_auth,
> is_user_exists,
> 2},
> {ejabberd_auth,
> try_register,
> 3},
>
> {ejabberd_ctl,process,1},
> {rpc,
>
> '-handle_call/3-fun-0-',
> 5}]}}
>
> I put the ejabberd sasl log file (
> http://www.bibliotheques.uqam.ca/flash_bugs/sasl2.txt ). Do I have to
> reinstall Evergreen (step 20) to change the capital letters in the
> bootstrapping database host (cobaye-TI.bib.uqam.ca) ?
>
> Thanks,
>
> Pierre Nault
>
>
>
>
> --
> What do you call a cyclist who doesn't wear a helmet? An organ
> donor. ~David Perry
>
>
>
>
> --
> Dan Scott
> Laurentian University
>
--
http://libgrunt.blogspot.com -- library culture and technology.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.georgialibraries.org/pipermail/open-ils-dev/attachments/20071019/a76e6564/attachment-0001.html
More information about the Open-ils-dev
mailing list