Difference between revisions of "Obsolete Service/jabber"

From Sugar Labs
Jump to navigation Jump to search
Line 1: Line 1:
<noinclude>{{TOCright}}</noinclude>
+
== Hostnames ==
  
== Jabber (jabber.sugarlabs.org) ==
+
* http://jabber.sugarlabs.org/
  
=== Hardware ===
+
== Hosted on ==
* Vmware ESX Virtual Machine
 
  
=== Location ===
+
[[Machine/jita]]
Hosted by [http://www.solutiongrove.com/|Solutiongrove]
 
  
=== Admins ===
+
== Administrative contact ==
* [[User:daveb| Dave Bauer]], daveb on #sugar Freenode
 
  
=== Software ===
+
jabber AT sugarlabs DOT org
* Modified XS 0.6 (based on Fedora Core 9)
 
  
=== Admin Notes ===
+
== Sysadmins ==
 +
 
 +
For non-emergency calls, preferably send email to the administrative contact.
 +
 
 +
* [[User:alsroot|Aleksey Lim]]
 +
 
 +
== Notes ==
 +
 
 +
ejabberd instance default for upstream sugar shell.
 +
 
 +
{| class="wikitable"
 +
|-
 +
!scope="row" | Home
 +
|{{Code|/srv/ejabberd}}
 +
|-
 +
!scope="row" | Main service
 +
|{{Code|ejabberd}}
 +
|-
 +
|}
 +
 
 +
'''TODO''' Initial install configuration, needs to be added to puppet recipes:
 +
 
 +
* create ''admin'' user
 +
* 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. To purge those users and get things working again:
Line 29: Line 48:
  
 
  # ejabberdctl stats registeredusers
 
  # ejabberdctl stats registeredusers
 +
 +
== Upgrade notes ==
 +
 +
Upgrade will be triggered on every puppet session, vcs repository will be rebased to the HEAD commit.

Revision as of 20:27, 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

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.