Problem with jabberd2 on ebox 0.11.101

[Piero Proietti]

Hello eBoxers! 

I'm trying to putting work Jabber on a eBox server in my lan. The server is configurated as follow:

hostname: atlante
domain: eng-arch (just an internal name, configurated in the ebox dns module)
eth0: 192.168.0.1 internal
eth1: 192.168.1.1 external card


I follow the advise on this post regarding the problem on the SSH protocol  http://forum.eboxplatform.com/index.php?topic=483.msg1795#msg1795

At this point I tried to connect with psi, but the result was who psi don't want to connect to the server becouse the certificate is auto-signed!

Well, I removed the mandatory ssl and tried again, with psi and spark, but I saw who the problem was who the module jabberd2-sm dont work!

I tried a little with this command and after I relaized who the problem was who it was trying to find the configuration file in /etc/jabberd when the configuration file is in /etc/jabberd2.

After that, I created a new directory /etc/jabberd and inside that, I put this 5 links:

# ln -s /etc/jabberd2/c2s.xml /etc/jabberd/c2s.xml
# ln -s /etc/jabberd2/resolver.xml /etc/jabberd/resolver.xml
# ln -s /etc/jabberd2/router.xml /etc/jabberd/router.xml
# ln -s /etc/jabberd2/s2s.xml /etc/jabberd/s2s.xml
# ln -s /etc/jabberd2/sm.xml /etc/jabberd/sm.xml

becouse, almost in my installation (ebox 0.11.101), the jabberd-c2s, jabberd-resolver, jabberd-router, jabberd-s2s and jabberd-sm all them try to open the configuration file in /etc/jabberd and not in /etc/jabberd2 where they are.

At the moment, all them are starting...

root@atlante:~# pstree|grep jabber
     |-jabberd2-c2s
     |-jabberd2-resolv
     |-jabberd2-router
     |-jabberd2-s2s


...with the notable exception of jabberd-sm, who die with this log:

root@atlante:/var/log/jabberd2# jabberd2-sm -D
Sat Aug 16 14:06:43 2008 [notice] starting up
Sat Aug 16 14:06:43 2008 [notice] id: atlante.eng-arch
Sat Aug 16 14:06:43 2008 [info] process id is 16159, written to /var/run/jabberd2/sm.pid
Sat Aug 16 14:06:43 2008 storage.c:163 adding arbitrary types to driver 'db'
Sat Aug 16 14:06:43 2008 storage.c:183 driver not loaded, trying to init
Sat Aug 16 14:06:43 2008 storage.c:206 calling driver initializer
Sat Aug 16 14:06:43 2008 [error] db: couldn't open environment: Invalid argument
Sat Aug 16 14:06:43 2008 [notice] initialisation of storage driver 'db' failed
Sat Aug 16 14:06:43 2008 [error] failed to initialise one or more storage drivers, aborting

That can be the problem?

Thanx in advance

Piero Proietti

[Piero Proietti]

Hi Eboxers!

After a while, was simple to find the solution... The problem was the corruption of the database, and the solution was:

root@atlante# cd /var/lib/jabberd2/db
root@atlante# db4.6_recover

and everything go finally well!

I hope this can help someone else...

Ciao

[sixstone]

Sorry not to answer about this issue. There is FAQ in trac [1], which talks about this issue, that I update with your last information in Ubuntu hardy.

Thanks very much for your feedback!

[1] http://trac.ebox-platform.com/wiki/Document/FAQ/RecoverJabberSessionManager