Obsolete Service/jabber: Difference between revisions

← Older edit Newer edit →

Revision as of 10:19, 12 March 2011

Hostnames

http://jabber.sugarlabs.org/

Hosted on

Machine/housetree/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	installed from native packages
Logs	`/var/log/ejabberd`
Main service	`ejabberd`
Admin Web UI	http://jabber.sugarlabs.org:5280/admin

Initial install configuration that was done:

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. Thus, ejabberd database is being resetting from daily cron task using /backup/ejabberd-spool.tar.gz initial db.

Upgrade notes

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

@@ Line 24: / Line 24: @@
 |-
 !scope="row" | Home
-|{{Code|/srv/ejabberd}}
+|''installed from native packages''
 |-
 !scope="row" | Logs
-|{{Code|/srv/ejabberd/site/var/log/ejabberd}}
+|{{Code|/var/log/ejabberd}}
 |-
 !scope="row" | Main service
@@ Line 37: / Line 37: @@
 |}
-'''TODO''' Initial install configuration, needs to be added to puppet recipes:
+Initial install configuration that was done:
 * create ''admin'' user
 * add [http://wiki.laptop.org/go/Installing_ejabberd#Installing_ejabberd_from_source_with_OLPC_patches 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.
+There's a problem with scaling up after more than a few dozens of users have been registered. Thus, ejabberd database is being resetting from daily cron task using {{Code|/backup/ejabberd-spool.tar.gz}} initial db.
-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.