Wednesday, June 20. 2007
Migrated to ejabberd
Last week the Berkeley DB used by the Jabber server of our local linux user group crashed again. It was the second database crash in six months. But this time even db_recover was unable to repair the database, so I did what I had on my TODO list since the first crash: Migrate to ejabberd, which I was already using on two other Jabber servers.
Meanwhile the service and all transports are back up again. There's only one visible change compared with the old setup, for security reasons connecting through port 5222 now requires starttls.
Meanwhile the service and all transports are back up again. There's only one visible change compared with the old setup, for security reasons connecting through port 5222 now requires starttls.
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
hi there,
im having same problems here: 2 db crashes in 6 month now and fixing it by using backups - db_recover was unsuccessfull. just one question: did you migrate the users/rosters to ejabberd? if yes, how? my googlesearches for converting a bdb jabberd2 database to ejabberd format gave no results. thx in advance.
bye paula
im having same problems here: 2 db crashes in 6 month now and fixing it by using backups - db_recover was unsuccessfull. just one question: did you migrate the users/rosters to ejabberd? if yes, how? my googlesearches for converting a bdb jabberd2 database to ejabberd format gave no results. thx in advance.
bye paula
It's possible to convert a jabberd14 database (it's just an XML file) to ejabberd, but unfortunately I found no way to convert a jabberd2 database to ejabberd, so the users had to recreate their accounts.
Quicksearch
Calendar
|
September '10 |
|
||||
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | |||
Categories
Syndication
Personal
Blogroll
