I've got ejabberd-0.9.8-1 installed and running, but I'm having trouble making database backups. Following the server migration page (http://www.ejabberd.im/migrate-host), I get:
jabber1:~/temp# ejabberdctl ejabberd@jabber1 backup ./backup.txt
Usage: ejabberdctl [--node node] command [options]
Available commands:
status get ejabberd status
stop stop ejabberd
restart restart ejabberd
reopen-log reopen log file
register user server password register a user
unregister user server unregister a user
backup file store a database backup to file
restore file restore a database backup from file
install-fallback file install a database fallback from file
dump file dump a database to a text file
load file restore a database from a text file
import-file file import user data from jabberd 1.4 spool file
import-dir dir import user data from jabberd 1.4 spool directory
registered-users list all registered users
delete-expired-messages delete expired offline messages from database
Examples:
ejabberdctl restart
ejabberdctl --node ejabberd@host restart
jabber1:~/temp#
Using just 'ejabberdctl backup ./file.txt', it pauses for a second as though something is happening, but no files are actually created.
Can someone give me a pointer?
Re: Unable to create a backup
I've got ejabberd-0.9.8-1 installed and running, but I'm having trouble making database backups. Following the server migration page (http://www.ejabberd.im/migrate-host), I get:
jabber1:~/temp# ejabberdctl ejabberd@jabber1 backup ./backup.txt
Usage: ejabberdctl [--node node] command [options]
Available commands:
status get ejabberd status
...
He shows you the help since the command you entered is invalid. Maybe the node name is not required.
Using just 'ejabberdctl backup ./file.txt', it pauses for a second as though something is happening, but no files are actually created.
Maybe the file was created where you don't expect it. Note that you specified a relative path; you should better try /tmp/ejadump.txt for example.
badlop wrote:Maybe the file
Maybe the file was created where you don't expect it. Note that you specified a relative path; you should better try /tmp/ejadump.txt for example.
No, I'm certain I've gone through /tmp and have searched through the file system. I've also tried using hard paths.
The fact that ejabberd_ctl
The fact that ejabberd_ctl stops for a second leads me think it really tries to do the dump. If you used absolute paths and the file is not created, then you should check ejabberd log files, maybe they include some indicative error report.
If the problem is on ejabberd_ctl, you can still use the web interface to dump the database.