Difference between revisions of "Obsolete Service/jabber"

From Sugar Labs
Jump to navigation Jump to search
Line 28: Line 28:
 
!scope="row" | Main service
 
!scope="row" | Main service
 
|{{Code|ejabberd}}
 
|{{Code|ejabberd}}
 +
|-
 +
!scope="row" | Admin Web UI
 +
|http://jabber.sugarlabs.org:5280/admin
 
|-
 
|-
 
|}
 
|}

Revision as of 20:31, 20 November 2010

Hostnames

Hosted on

Machine/jita

Administrative contact

jabber AT sugarlabs DOT org

Sysadmins

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

Notes

ejabberd instance default for upstream sugar shell.

Home /srv/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. To purge those users and get things working again:

# /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:

# ejabberdctl stats registeredusers

Upgrade notes

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