I downloaded the .gz file and unpacked to the .bin file.
Then changed permissions to make it executable.
When ejabberd-2.0.2-linux-x86-installer.bin is double-
clicked, a window opens and asks which program should
be used?
I have not been able to get any further.
What should I do?
The O/S is Ubuntu Desktop 8.4 updated.
Any help is appreciated.
Thanks, Earl
having the same problem.....
having the same problem.....
no problems on Debian
no problems on Debian 4.0
works fine...
Ubuntu sources
Hey,
I've tried doing the installation using the packages and have managed to get it working. I have found that installing from the Ubuntu repository is much easier.
If your using Ubuntu desktop goto System >> Administration >> Synaptic Package Manager and then search for ejabberd. Currently the stable release on Ubuntu (&debian) is 1.1.4-4 so if you do want 2+ you'll need to update your sources list or install from source.
I believe 2.0.1-2~hardy1 is available in hardy-backports, I don't feel confident enough to leave further instructions here on how to go about installing backports you will need to read up on what this means (ie. I don't want to be responsible for you accidentally upgrading the wrong packages :P )
Obviously you can use apt-get and aptitude from the command line (you will still need to update your sources if you need newer versions)
Regards,
Kurt
installed via Synaptic, but CPU=100%
Hi,
I added some sources to the Synaptic package manager and installed ejabberd 2.0.1-2~etch1.
Then
# ps -AF |grep ejabberd
ejabberd 4718 1 0 498 396 0 Oct02 ? 00:00:04 /usr/lib/erlang/erts-5.5.5/bin/epmd -daemon
ejabberd 4737 1 0 6219 20184 0 Oct02 ? 00:00:28 /usr/lib/erlang/erts-5.5.5/bin/beam -K false -P 250000 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/ejabberd -sname ejabberd -pa /usr/lib/ejabberd/ebin -s ejabberd -kernel inetrc "/etc/ejabberd/inetrc" -ejabberd config "/etc/ejabberd/ejabberd.cfg" log_path "/var/log/ejabberd/ejabberd.log" -sasl sasl_error_logger {file,"/var/log/ejabberd/sasl.log"} -mnesia dir "/var/lib/ejabberd" -smp disable -noshell -noshell -noinput
root 23414 23393 0 751 752 0 20:53 pts/1 00:00:00 grep ejabberd
#
I noticed that the CPU was at 100%, so I rebooted.
After reboot, ps gave same results, so ejabberd is starting at boot-up. However CPU still at 100%.
So I commanded
# kill 4733
# kill 4714
# ps -AF | grep ejabberd
root 5650 5500 0 751 752 0 21:16 pts/0 00:00:00 grep ejabberd
#
and guess what: CPU dropped to low %
This is really frustrating.
Sources
Could you provide a little more information eg. which sources were added?
Isn't etch a Debian release I hope you aren't installing this on an Ubuntu system. What are you running?
toubles installing ejabberd 2.0.1-2 on Ubuntu 8.0.4.1
Hi Kurt,
yes, I did try to install 2.0.1-2~etch1 on Ubuntu 8.0.4.1.
I asked Synaptic to completely remove this, which it did.
I then removed from 3rd source repositories:
http://sgolovan.jabber.ru/debian/ etch main
http://www.kamailio.net/debian sarge main
now unchecked:
and addedhttp://fr.archive.ubuntu.com/ubuntu hardy-backports main universe
deb
I have seen some comments about the hardy backport and assume that it is working correctly now:
https://bugs.launchpad.net/hardy-backports/+bug/237187/comments/4
https://lists.ubuntu.com/archives/ubuntu-backports/2008-September/009079...
Under Synaptic, I now see ejabberd 2.0.1.-2 and could install it.
Please confirm that it is OK to install
ejabberd 2.0.1.-2 hardy backport by using Synaptic.
Thanks for your help, Earl
ejabberd 2.0.1-2
There shouldn't be a problem installing that, you will be pulling in dependencies from back ports though so you should just double check that any upgrades won't effect anything else on the system.
I decided to stay with the stable release so wouldn't be able to tell you if the newer releases will definetly work on your system. I don't see any problems with what you've done though and I've have completed the installation of ejabberd2 in this way before without any problems.
Let me know how you get on.
Regards,
Kurt
toubles installing ejabberd 2.0.1-2 on Ubuntu 8.0.4.1
Kurt,
I uninstalled erlang-base and erlang-nox and used Synaptic to reinstall ejabberd 2.0.1-2 hardy backport. It automatically added erlang-base and erlang-nox and installed these also. The installation went very fast.
Unlike the (false) etch installation, ejabberd does not appear to be running. I only see one process instead of the two using the etch install, which hogged 100% CPU. That second process also had a very long command line (see below at bottom).
For hardy backport installation:
# ps -AF |grep erlan*
ejabberd 6053 1 0 498 392 0 21:18 ? 00:00:00 /usr/lib/erlang/erts-5.5.5/bin/epmd -daemon
root 6119 6102 0 751 764 0 21:20 pts/2 00:00:00 grep erlan*
# ps -AF |grep ejabber*
ejabberd 6053 1 0 498 392 0 21:18 ? 00:00:00 /usr/lib/erlang/erts-5.5.5/bin/epmd -daemon
root 6121 6102 0 751 768 0 21:21 pts/2 00:00:00 grep ejabber*
# ejabberdctl status
RPC failed on the node ejabberd@Persistent: nodedown
# ejabberdctl start
RPC failed on the node ejabberd@Persistent: nodedown
# sudo ejabberdctl register name password
RPC failed on the node ejabberd@Persistent: nodedown
I saw a comment
"you need to edit the /etc/ejabberd/ejabberd.cfg and put your hostname in where it tells you in the comments",
but don't understand exactly what to do.
Do you have any comments how I can get ejabberd running
completely?
Earl
--------------------
under /etc/init.d/ejabberd is the following:
#! /bin/sh
#
# ejabberd Start/stop ejabberd server
#
### BEGIN INIT INFO
# Provides: ejabberd
# Required-Start: $remote_fs $network
# Required-Stop: $remote_fs $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Starts ejabberd jabber server
# Description: Starts ejabberd jabber server, an XMPP
# compliant server written in Erlang.
### END INIT INFO
PATH=/sbin:/bin:/usr/sbin:/usr/bin
EJABBERD=/usr/sbin/ejabberd
EJABBERDCTL=/usr/sbin/ejabberdctl
EJABBERDUSER=ejabberd
NAME=ejabberd
test -f $EJABBERD || exit 0
test -f $EJABBERDCTL || exit 0
# Include ejabberd defaults if available
if [ -f /etc/default/ejabberd ] ; then
. /etc/default/ejabberd
fi
ctl()
{
action="$1"
su $EJABBERDUSER -c "$EJABBERDCTL $action" >/dev/null
}
start()
{
cd /var/lib/ejabberd
su $EJABBERDUSER -c "$EJABBERD -noshell -detached"
}
stop()
{
if ctl stop ; then
cnt=0
sleep 1
while ctl status ; do
echo -n .
cnt=`expr $cnt + 1`
if [ $cnt -gt 60 ] ; then
echo -n " failed"
break
fi
sleep 1
done
else
echo -n " failed"
fi
}
case "$1" in
start)
echo -n "Starting jabber server: $NAME"
if ctl status ; then
echo -n " already running"
else
start
fi
;;
stop)
echo -n "Stopping jabber server: $NAME"
if ctl status ; then
stop
else
echo -n " already stopped"
fi
;;
restart|force-reload)
echo -n "Restarting jabber server: $NAME"
if ctl status ; then
stop
start
else
echo -n " is not running. Starting $NAME"
start
fi
;;
*)
echo "Usage: $0 {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
if [ $? -eq 0 ]; then
echo .
else
echo " failed."
fi
exit 0
==========================
here are the two processes when I falsely installed from etch:
# ps -AF |grep ejabberd
ejabberd 4718 1 0 498 396 0 Oct02 ? 00:00:04 /usr/lib/erlang/erts-5.5.5/bin/epmd -daemon
ejabberd 4737 1 0 6219 20184 0 Oct02 ? 00:00:28 /usr/lib/erlang/erts-5.5.5/bin/beam -K false -P 250000 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/ejabberd -sname ejabberd -pa /usr/lib/ejabberd/ebin -s ejabberd -kernel inetrc "/etc/ejabberd/inetrc" -ejabberd config "/etc/ejabberd/ejabberd.cfg" log_path "/var/log/ejabberd/ejabberd.log" -sasl sasl_error_logger {file,"/var/log/ejabberd/sasl.log"} -mnesia dir "/var/lib/ejabberd" -smp disable -noshell -noshell -noinput
found easy to understand tutorial_install + configure
I just found a very good tutorial that is easy to understand.
Will be following this tutorial and hope to get things working.
Earl
Looks good
Hi Earl,
That seems to cover most of the configuration.
This might be a matter of preference but there is a web interface that allows the updating of users and various other things. If your on the machine running ejabberd open a browser and go tohttp://localhost:5280/
Use the admin users login credentials to get in. I seem to remember something about ejabberdctl overwriting changes made by the web interface though, although I can't remember where I read that.
You may need to uncomment this line and restart ejabberd to get this working:
{5280, ejabberd_http, [http_poll, web_admin]}
]}.
Another thing that I've found quite useful is shared rosters and vhosts:
http://www.ejabberd.im/shared-roster-all
Multiple hosts/domains (vhosts):
%% Hostname
{hosts, ["example1.com", "example2.com", "example3.com"]}.