<precise descRiption of the problem (multiple lines)>
jabberd processes refuses to start with this messages in jabberd.log:

Apr  7 11:24:37 ugai-test jabberd/resolver[70934]: starting up
Apr  7 11:24:37 ugai-test jabberd/sm[70935]: starting up
Apr  7 11:24:37 ugai-test jabberd/resolver[70934]: process id is 70934, written
to /var/jabberd/pid/resolver.pid
Apr  7 11:24:37 ugai-test jabberd/resolver[70934]: attempting connection to rout
er at 127.0.0.1, port=5347
Apr  7 11:24:37 ugai-test jabberd/resolver[70934]: connection attempt to router
failed: Connection refused (61)
Apr  7 11:24:37 ugai-test jabberd/router[70933]: starting up
Apr  7 11:24:37 ugai-test jabberd/router[70933]: process id is 70933, written to
 /var/jabberd/pid/router.pid
Apr  7 11:24:37 ugai-test jabberd/s2s[70936]: starting up (interval=0, queue=0,
keepalive=0, idle=86400)
Apr  7 11:24:37 ugai-test jabberd/s2s[70936]: process id is 70936, written to /v
ar/jabberd/pid/s2s.pid
Apr  7 11:24:37 ugai-test jabberd/router[70933]: loaded user table (2 users)
Apr  7 11:24:37 ugai-test jabberd/c2s[70937]: starting up
Apr  7 11:24:37 ugai-test jabberd/c2s[70937]: process id is 70937, written to /v
ar/jabberd/pid/c2s.pid
Apr  7 11:24:37 ugai-test jabberd/router[70933]: [0.0.0.0, port=5347] listening
for incoming connections
Apr  7 11:24:38 ugai-test jabberd/sm[70935]: id: jabber.road.omskelecom.ru
Apr  7 11:24:38 ugai-test jabberd/sm[70935]: process id is 70935, written to /va
r/jabberd/pid/sm.pid
Apr  7 11:24:38 ugai-test jabberd/s2s[70936]: attempting connection to router at
 127.0.0.1, port=5347
Apr  7 11:24:38 ugai-test jabberd/router[70933]: [127.0.0.1, port=3804] connect
Apr  7 11:24:38 ugai-test jabberd/s2s[70936]: connection to router established
Apr  7 11:24:38 ugai-test jabberd/router[70933]: [127.0.0.1, port=3804] authenti
cated as jabberd
Apr  7 11:24:38 ugai-test jabberd/router[70933]: [s2s] set as default route
Apr  7 11:24:38 ugai-test jabberd/router[70933]: [s2s] online (bound to 127.0.0.
1, port 3804)
Apr  7 11:24:38 ugai-test jabberd/s2s[70936]: [0.0.0.0, port=5269] listening for connections
Apr  7 11:24:38 ugai-test jabberd/s2s[70936]: ready for connections
Apr  7 11:24:38 ugai-test jabberd/c2s[70937]: db: couldn't set panic call: No su
ch file or directory
Apr  7 11:24:38 ugai-test jabberd/sm[70935]: db: couldn't set panic call: No suc
h file or directory
Apr  7 11:24:38 ugai-test jabberd/c2s[70937]: failed to initialise auth module '
db'
Apr  7 11:24:38 ugai-test jabberd/sm[70935]: initialisation of storage driver 'd
b' failed
Apr  7 11:24:38 ugai-test jabberd/sm[70935]: failed to initialise one or more st
orage drivers, aborting
Apr  7 11:24:38 ugai-test jabberd/s2s[70936]: shutting down
Apr  7 11:24:38 ugai-test jabberd/router[70933]: shutting down
Apr  7 11:24:38 ugai-test jabberd/resolver[70934]: shutting down
Apr  7 11:24:38 ugai-test jabberd/router[70933]: [127.0.0.1, port=3804] disconne
ct
Apr  7 11:24:38 ugai-test jabberd/router[70933]: [s2s] default route offline
Apr  7 11:24:38 ugai-test jabberd/router[70933]: [s2s] offline

possible reason is that port using headers from db41 port, but jabberd binaries are linked against db43 libs.
btw, net-im/jabberd used to work in this configuration before upgrade to 2.0.10 (or something around that)

How-To-Repeat: 	
just install net-im/jabberd port with multiple versions of Berkeley DB installed.