Linux xen3.kzts.ru 2.6.18-8.el5xen #1 SMP Thu Mar 15 19:56:43 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
jabberd-2.1.17
собирал из исходников --enable-mysql --enable-ssl --enable-sasl=cyrus
--with-extra-library-path=/...:... --with-extra-include-path=/...:...
перечитав руководство по установке и администрированию изменил конфигурацию по умолчанию, создал пользователя в mysql, дал ему права insert, delete ...., прописал в конфиге пароль для доступа к бд...сервер стартует..
[jabber@xen3 etc]$ jabberd -D
JBRD: debug on
JBRD: version(2.1.17)
JBRD: config_dir(/usr/local/etc)
JBRD: LaunchJob: router -> /usr/local/bin/router -c /usr/local/etc/router.xml -D
JBRD: LaunchJob: resolver -> /usr/local/bin/resolver -c /usr/local/etc/resolver.xml -D
JBRD: LaunchJob: sm -> /usr/local/bin/sm -c /usr/local/etc/sm.xml -D
JBRD: LaunchJob: s2s -> /usr/local/bin/s2s -c /usr/local/etc/s2s.xml -D
JBRD: LaunchJob: c2s -> /usr/local/bin/c2s -c /usr/local/etc/c2s.xml -D
в логах:
Oct 19 10:06:36 xen3 jabberd/router[31455]: starting up
Oct 19 10:06:36 xen3 jabberd/router[31455]: process id is 31455, written to /var/jabberd/pid/router.pid
Oct 19 10:06:36 xen3 jabberd/router[31455]: loaded user table (1 users)
Oct 19 10:06:36 xen3 jabberd/router[31455]: loaded filters (0 rules)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: starting up
Oct 19 10:06:36 xen3 jabberd/sm[31457]: id: xen3.kzts.ru
Oct 19 10:06:36 xen3 jabberd/router[31455]: [0.0.0.0, port=5347] listening for incoming connections
Oct 19 10:06:36 xen3 jabberd/sm[31457]: process id is 31457, written to /var/jabberd/pid/sm.pid
Oct 19 10:06:36 xen3 jabberd/sm[31457]: loading 'mysql' storage module
Oct 19 10:06:36 xen3 jabberd/sm[31457]: initialised storage driver 'mysql'
Oct 19 10:06:36 xen3 jabberd/sm[31457]: modules search path: /usr/local/lib/jabberd
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'status' added to chain 'sess-start' (order 0 index 0 seq 0)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'status' added to chain 'sess-end' (order 0 index 0 seq 1)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'iq-last' added to chain 'sess-end' (order 1 index 1 seq 0)
Oct 19 10:06:36 xen3 jabberd/s2s[31458]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
Oct 19 10:06:36 xen3 jabberd/c2s[31459]: starting up
Oct 19 10:06:36 xen3 jabberd/resolver[31456]: starting up
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'validate' added to chain 'in-sess' (order 0 index 2 seq 0)
Oct 19 10:06:36 xen3 jabberd/s2s[31458]: process id is 31458, written to /var/jabberd/pid/s2s.pid
Oct 19 10:06:36 xen3 jabberd/resolver[31456]: process id is 31456, written to /var/jabberd/pid/resolver.pid
Oct 19 10:06:36 xen3 jabberd/resolver[31456]: attempting connection to router at 127.0.0.1, port=5347
Oct 19 10:06:36 xen3 jabberd/router[31455]: [127.0.0.1, port=60000] connect
Oct 19 10:06:36 xen3 jabberd/resolver[31456]: No worthy mechs found
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'status' added to chain 'in-sess' (order 1 index 0 seq 2)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'privacy' added to chain 'in-sess' (order 2 index 3 seq 0)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'roster' added to chain 'in-sess' (order 3 index 4 seq 0)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'vacation' added to chain 'in-sess' (order 4 index 5 seq 0)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'iq-vcard' added to chain 'in-sess' (order 5 index 6 seq 0)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'iq-ping' added to chain 'in-sess' (order 6 index 7 seq 0)
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'iq-private' added to chain 'in-sess' (order 7 index 8 seq 0)
Oct 19 10:06:36 xen3 jabberd/s2s[31458]: attempting connection to router at 127.0.0.1, port=5347
Oct 19 10:06:36 xen3 jabberd/c2s[31459]: process id is 31459, written to /var/jabberd/pid/c2s.pid
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'disco' added to chain 'in-sess' (order 8 index 9 seq 0)
Oct 19 10:06:36 xen3 jabberd/router[31455]: [127.0.0.1, port=60001] connect
Oct 19 10:06:36 xen3 jabberd/s2s[31458]: No worthy mechs found
Oct 19 10:06:36 xen3 jabberd/sm[31457]: module 'amp' added to chain 'in-sess' (order 9 index 10 seq 0)
Oct 19 10:06:36 xen3 jabberd/c2s[31459]: modules search path: /usr/local/lib/jabberd
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'offline' added to chain 'in-sess' (order 10 index 11 seq 0)
Oct 19 10:06:37 xen3 jabberd/c2s[31459]: loading 'mysql' authreg module
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'announce' added to chain 'in-sess' (order 11 index 12 seq 0)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'presence' added to chain 'in-sess' (order 12 index 13 seq 0)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'deliver' added to chain 'in-sess' (order 13 index 14 seq 0)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'session' added to chain 'in-router' (order 0 index 15 seq 0)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'validate' added to chain 'in-router' (order 1 index 2 seq 1)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'presence' added to chain 'in-router' (order 2 index 13 seq 1)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'privacy' added to chain 'in-router' (order 3 index 3 seq 1)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'privacy' added to chain 'out-router' (order 0 index 3 seq 2)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 1 seq 1)
Oct 19 10:06:37 xen3 jabberd/c2s[31459]: initialized auth module 'mysql'
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 7 seq 1)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 16 seq 0)
Oct 19 10:06:37 xen3 jabberd/c2s[31459]: [xen3.kzts.ru] configured; realm=kzts.ru, registration enabled
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 17 seq 0)
Oct 19 10:06:37 xen3 jabberd/c2s[31459]: attempting connection to router at 127.0.0.1, port=5347
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'amp' added to chain 'pkt-sm' (order 4 index 10 seq 1)
Oct 19 10:06:37 xen3 jabberd/router[31455]: [127.0.0.1, port=60002] connect
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'disco' added to chain 'pkt-sm' (order 5 index 9 seq 1)
Oct 19 10:06:37 xen3 jabberd/sm[31457]: module 'announce' added to chain 'pkt-sm' (order 6 index 12 seq 1)
Oct 19 10:06:37 xen3 jabberd/c2s[31459]: No worthy mechs found
.....
Oct 19 10:06:37 xen3 jabberd/sm[31457]: attempting connection to router at 127.0.0.1, port=5347
Oct 19 10:06:37 xen3 jabberd/router[31455]: [127.0.0.1, port=60003] connect
Oct 19 10:06:37 xen3 jabberd/sm[31457]: No worthy mechs found
погуглил, нашел: http://www.jabber.org/muc-logs/jdev@conference.jabber.org/2007-05-21.html
[14:08:22] <ccaporal> i got a lot of 'no worthy mechs found' at /var/log/messages
[14:08:33] <ccaporal> from all components: c2s, s2s, sm, router
[14:19:51] <ccaporal> hello?
[14:20:19] <legoscia> i know almost nothing about jabberd2 ☺
[14:20:37] <legoscia> but the mechanisms error message sounds funny
[14:20:52] <legoscia> have you accidentally disabled some authentication mechanism in the configuration?
[14:23:10] <ccaporal> no
[14:23:36] <ccaporal> im using <traditional> <plain/> </traditional>
[14:23:59] <ccaporal> after <sasl> <plain/> </sasl>
[14:24:45] <legoscia> hm… isn't digest-md5 supposed to be there?
[14:24:51] legoscia is guessing wildly
[14:25:19] <ccaporal> i think that its not the problem
исправил:
фрагмент c2s.xml
<!-- Available authentication mechanisms -->
<mechanisms>
<!-- These are the traditional Jabber authentication mechanisms.
Comment out any that you don't want to be offered to clients.
Note that if the auth/reg module does not support one of
these mechanisms, then it will not be offered regardless of
whether or not it is enabled here. -->
<traditional>
<plain/>
<!-- <digest/> -->
</traditional>
<!-- SASL authentication mechanisms. Comment out any that you
don't want to be offered to clients. Again, if the auth/reg
module does not support one of these mechanisms, then it will
not be offered. -->
<!-- <sasl>
<plain/>
<digest-md5/>
<anonymous/>
</sasl> -->
</mechanisms>
<!-- Additional mechanisms that are also available when the
connection is encrypted. Ie. when START-TLS had been
negotiated, or user connected on SSL-wrapped port. -->
<ssl-mechanisms>
<!-- it's advisable that you disable plain in the above
<mechanisms/> section -->
<traditional>
<plain/>
</traditional>
<!-- <sasl>
<plain/>
</sasl> -->
</ssl-mechanisms>
netstat -na после запуска jabberd
e
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 192.168.2.143:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:665 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN
tcp 1 0 192.168.2.143:34766 192.168.1.15:389 CLOSE_WAIT
tcp 0 0 192.168.2.143:54534 192.168.1.15:389 CLOSE_WAIT
tcp 0 0 192.168.2.143:49706 192.168.1.15:389 ESTABLISHED
tcp 0 0 192.168.2.143:36873 192.168.1.15:389 CLOSE_WAIT
tcp 0 0 192.168.2.143:55984 192.168.1.15:389 CLOSE_WAIT
tcp 0 0 192.168.2.143:57578 192.168.1.15:445 ESTABLISHED
tcp 0 0 192.168.2.143:59798 192.168.1.15:389 CLOSE_WAIT
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 :::443 :::* LISTEN
udp 0 0 192.168.2.143:137 0.0.0.0:*
udp 0 0 0.0.0.0:137 0.0.0.0:*
udp 0 0 192.168.2.143:138 0.0.0.0:*
udp 0 0 0.0.0.0:138 0.0.0.0:*
udp 0 0 0.0.0.0:659 0.0.0.0:*
udp 0 0 0.0.0.0:662 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:111 0.0.0.0:*
порты 5222 и 5223 не открываются.
Помогите, пожалуйста.