-
Notifications
You must be signed in to change notification settings - Fork 127
Developer: Reset ejabberd database
nicolasochem edited this page Jun 20, 2012
·
2 revisions
Something goes mad? You have very weird error about entity connection, subscription or whatever? You have tried everything but you can't fix your problem? The badass solution is to drop the ejabberd database. It is relatively safe operation as all your Archipel configuration will be kept. It will fix most of problems related to ejabberd.
It is mandatory to do this when you change the host part of ejabberd.cfg
You will loose:
- All users rosters: you need to remove and add again your hypervisors and virtual machines as contacts.
- All shared roster groups if any.
- All human users account
- All user's Archipel GUI specific configuration
Note that this only works when using mnesia backend for ejabberd (the default)
/etc/init.d/archipel stop
ejabberdctl stop
rm -rf /var/lib/ejabberd/*
rm -rf /opt/ejabberd-X.X.X/var/lib/ejabberd/*
rm -rf /opt/ejabberd-X.X.X/database/ejabberd@localhost/*
ejabberdctl start
ejabberdctl register admin FQDN password
ejabberdctl register userA FQDN password
...
ejabberdctl register userN FQDN password
/etc/init.d/archipel start
DO NOT RECREATE ANY XMPP ACCOUNTS FOR HYPERVISORS OR VIRTUAL MACHINES