>These errors from JCR occur when JCR cannot properly connect to or
>authenticate to the jabberd 2 router. Check the router logs for
>additional information.

>However, I suspect that the passwords and/or port numbers between
>mu-conference and the router are not the same.

>Paul
Thanx. I checked router.log:
Thu Aug 24 00:39:49 2006 [notice] starting up
Thu Aug 24 00:39:49 2006 [info] process id is 21451, written
to /var/run/jabber/router.pid
Thu Aug 24 00:39:49 2006 [notice] loaded user table (1 users)
Thu Aug 24 00:39:49 2006 [error] [0.0.0.0, port=5347] unable to listen
(Address already in use)
Last error does not occures only when I change port number in
muc-conf.xml and router.xml to another one. I tried 5348 and
muc-conference starts up without errors, but I cannot join or create
conference. Pandion says that "server does not support conferencing". I
think that port number must be 5347, but what can I do to start router
module without problems with such configuration?
My ip and port settings:
In c2s.xml:
<ip>127.0.0.1</ip<!-- default: 127.0.0.1
<port>5347</port<!-- default: 5347
In router.xml:
<ip>0.0.0.0</ip>
<port>5347</port>
P.S.: i tried to change ip addresses to 192.168.2.240, 127.0.0.1,
0.0.0.0 in various combinations, but i failed :(
JAdmin mailing list
JAdmin (AT) jabber (DOT) org
FAQ:

Alexander Semyonov wrote:
My ip and port settings:

In c2s.xml:
<ip>127.0.0.1</ip<!-- default: 127.0.0.1
<port>5347</port<!-- default: 5347

In router.xml:
<ip>0.0.0.0</ip>
<port>5347</port>

The c2s and router components cannot both listen on the same port.

c2s is only to allow Jabber clients to connect directly, and usually
should be listening on port 5222.

For a component connection as with mu-c, c2s is not used; the component
should connect to the router (presumably on port 5347)
-Alex Mauer "hawke"

JAdmin mailing list
JAdmin (AT) jabber (DOT) org

FAQ:

PGP SIGNATURE
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

4AxCgKlJVMCN9LVXWCNJrJg=
=+MPY
PGP SIGNATURE