Difference between revisions of "Obsolete Service/jabber"

Revision as of 04:30, 10 January 2011

Hostnames

http://jabber.sugarlabs.org/

Hosted on

Machine/jita

Administrative contact

jabber AT sugarlabs DOT org

Sysadmins

For non-emergency calls, preferably send email to the administrative contact.

Aleksey Lim

Notes

ejabberd instance default for upstream sugar shell.

Home	`/srv/ejabberd`
Logs	`/srv/ejabberd/site/var/log/ejabberd`
Main service	`ejabberd`
Admin Web UI	http://jabber.sugarlabs.org:5280/admin

TODO Initial install configuration, needs to be added to puppet recipes:

create admin user
add Online shared roster group from web ui.

There's a problem with scaling up after more than a few dozens of users have been registered. All users who weren't logged in for 2 weeks will be deleted from cron job.

You can check how many users are registered with:

# ejabberdctl stats registeredusers

Upgrade notes

Upgrade will be triggered on every puppet session, vcs repository will be rebased to the HEAD commit.

@@ Line 42: / Line 42: @@
 * add [http://wiki.laptop.org/go/Ejabberd_Configuration Online] shared roster group from web ui.
-There's a problem with scaling up after more than a few dozens of users have been registered. To purge those users and get things working again:
+There's a problem with scaling up after more than a few dozens of users have been registered. All users who weren't logged in for 2 weeks will be deleted from cron job.
- # /etc/init.d/ejabberd stop
- # ps ax | grep jabber        # Make sure there are no erlang processes
- # rm -rf /var/lib/ejabberd
- # mkdir /var/lib/ejabberd
- # chown ejabberd.ejabberd /var/lib/ejabberd
- # /etc/init.d/ejabberd start
 You can check how many users are registered with: