[OPEN-ILS-DEV] troubleshooting new install: grep ejabberd doesn't match example
Anoop Atre
anoop.atre at mnsu.edu
Wed Aug 25 15:16:19 EDT 2010
Steve
You might want to drop by the IRC channel via the web gateway for a
more immediate feedback well unless folks are sleeping or on a deadline.
The IRC gets used quite a bit by admins/devs for troubleshooting.
http://evergreen-ils.org/irc.php
Cheers
Thomas Berezansky wrote:
> I don't think that is a problem, our working install (of trunk, but
> shouldn't matter for this) doesn't have that in the output either. I
> think that was part of how SSL used to be handled by ejabberd.
>
> Thomas Berezansky
> Merrimack Valley Library Consortium
>
>
> Quoting "Metcalf, Steve" <MetcalfS at evergreen.edu>:
>
>> Lucid 10.04, OpenSRF 1.2.2, Evergreen 1.6.0.7
>>
>> On
>> http://www.open-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_fo
>> r_errors there is an example of output from ps -aef | grep ejabberd that
>> includes a process with the command
>>
>> /usr/lib/erlang/lib/ssl-3.1.1.1/priv/bin/ssl_esock
>>
>> There is a file with that name on the system, the version is 3.10.7, but
>> I never see a process with that command in the ps output. I only get
>> the other two processes in the example.
>>
>> Is this a sign of something broken in the install? I've not been able
>> to get the smoke test to work and the default login and password are not
>> recognized when logging in from the client.
More information about the Open-ils-dev
mailing list