Jabberd 2 Documentation Project
Jabberd 2 Documentation Project
|
You can also try searching the Jabberd 2 Mailing List Archives for questions about jabber administration, or subscribe to the Jabberd 2 Mailing List or one of the Jabber Mailing Lists to post your own question. You may also want to check out Troubleshooting Tips for Jabberd 2.
"Internal" or "library load" components that load at runtime into a jabberd 1.4 instance can be used by placing the 1.4 instance into "uplink" mode. An appropriate "linker" alias needs to be added to router.xml to support this.
Jabberd 2 does not provide XDB and logging facilities. For "internal" components, these can be provided by the enclosing jabberd 1.4 instance. For "external" components, they will need to connect to a 1.4 instance that provides these services, which in turn uplinks to the Jabberd 2 router.
authreg table
because this only introduces users to the c2s component, but not to the
sm component. Correct entries are required in the active
table as well. It is best to use a Jabber client to register users. If
this is not acceptable, corresponding entries can be manually created in
the active table, or the session manager can be configured
to create new users automatically the first time they log in. Uncomment
the auto-create tag in the User options section
of sm.xml to enable auto-creation of new users. (Note that
enabling auto-create does not enable inband registration, as
only users that pass the c2s component are created.)
--with-package=path has been replaced with
--with-extra-include-path path and
--with-extra-library-path path. The paths searched also
changed with stable 3; therefore, it may be necessary to specify a
path(s) to a package that was automatically found by a previous release.
See Section 3.3.
--enable-authreg=package and
--enable-storage=package have been replaced with a simpler
--enable-package option. Thus to enable MySQL for authreg
and/or storage, one would use the option --enable-mysql. See
Section 3.3. Because the configure
script does not report invalid options, using an option such as
--enable-authreg=mysql would cause neither the configure nor
the build to crash; however, the MySQL driver would not be compiled in.
If you then set the XML configuration files to use MySQL, Jabberd 2 would
crash.
netstat -l |grep postgres). If not,
modify postgresql.conf, setting tcpip_socket =
true and restart. If problems still exist, check the
pg_hba.conf file and check if TCP/IP connections are
authorized (i.e. an appropriate host record exists).
./configure script searches several locations;
however, if the script cannot find your Berkeley DB installation, you
should specify the location as a parameter when running
./configure. For example, if you are running Berkeley DB
version 4.2, you may need to run ./configure as below:
./configure --with-berkeley-db=/usr/local/BerkeleyDB.4.2/
select `collection-owner`, `object-sequence`, `jid`, `group` from `roster-groups`;
/tmp/mysql.sock. The default socket when installing MySQL
from source is /var/lib/mysql/mysql.sock. You will need to
create a symlink to /tmp/mysql.sock if it does not exist:
ln -s /var/lib/mysql/mysql.sock /tmp/mysql.sock
./configure to fail on Redhat
is that Redhat ships with a MySQL installation that does not include the
development libraries required by Jabberd 2. See the MySQL question under
Building and Installation above. The second reason that
./configure might fail is that Redhat stores the MySQL
libraries and include files separately. Run ./configure with
both paths (as below) to identify both locations:
./configure --with-mysql=/usr/include/mysql:/usr/lib/mysql
./configure is run. However, Kerberos references cause
the Jabberd 2 build to crash.
There is an easy work around for this problem. Execute the command
below before running ./configure :
export CFLAGS="-I/usr/kerberos/include"
./configure cannot find Berkeley DB, it may be because
libpthreads is not linked. Run ./configure as below to fix
this:
./configure [options] LDFLAGS=-lpthread
./configure. To fix this, run ./configure with
the paths to both as below (replacing "mysql" with "pgsql" for PostgreSQL
installations):
./configure --with-mysql=/usr/include/mysql:/usr/lib/mysql
|
|
|
|
||||
|
|
||||
|
© 2003 Will Kamishlian and Robert Norris
|
||||
|
|
||||
| This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. | ||||
|
|
||||
|
|
 |
||