thilly
20.11.03, 12:33
hallo,
nachdem ich das mit dem mu-conference (bei jabber 1.4) nicht hin bekommen habe,
versuche ichs jetzt mit jabber2.0
aber auch nicht besser...
ich habe alles so konfiguriert wie im Manual
( configure --prefix=/jabber --enable-ssl )
make
make install
usw...)
nun bin ich am Punkt wo er gestartet werden soll - Punkt 5(http://www.jabberdoc.org/section05.html)
das geht leider nicht: ich bekomme die FM:
mylinux:/jabber/etc/jabberd # /jabber/bin/jabberd -D
JBRD: debug on
JBRD: version(2.0rc1)
JBRD: config_dir(/jabber/etc/jabberd)
JBRD: LaunchJob: router -> /jabber/bin/router -c /jabber/etc/jabberd/router.xml -D
JBRD: LaunchJob: resolver -> /jabber/bin/resolver -c /jabber/etc/jabberd/resolver.xml -D
JBRD: LaunchJob: sm -> /jabber/bin/sm -c /jabber/etc/jabberd/sm.xml -D
JBRD: LaunchJob: s2s -> /jabber/bin/s2s -c /jabber/etc/jabberd/s2s.xml -D
JBRD: LaunchJob: c2s -> /jabber/bin/c2s -c /jabber/etc/jabberd/c2s.xml -D
RSLV: Thu Nov 20 13:29:15 2003 [notice] starting up
RSLV: Thu Nov 20 13:29:15 2003 [info] process id is 22269, written to /jabber/var/jabberd/pid/resolver.pid
RSLV: sx (sasl.c:533) initialising sasl plugin
ROUT: Thu Nov 20 13:29:15 2003 [notice] starting up
RSLV: Thu Nov 20 13:29:15 2003 [notice] attempting connection to router at 127.0.0.1, port=5347
ROUT: Thu Nov 20 13:29:15 2003 user.c:34 loading user table
ROUT: Thu Nov 20 13:29:15 2003 [info] process id is 22268, written to /jabber/var/jabberd/pid/router.pid
ROUT: Thu Nov 20 13:29:15 2003 user.c:89 remembering user 'jabberd'
S2S : Thu Nov 20 13:29:15 2003 [notice] starting up
ROUT: Thu Nov 20 13:29:15 2003 [notice] loaded user table (1 users)
ROUT: Thu Nov 20 13:29:15 2003 aci.c:37 loading aci
ERROR: sm died. Shutting down server.
JBRD: Got a signal... pass it on.
JBRD: It was a TERM. Shut it all down!
***
Und nu?
das komische ist ich finde keine logs.
obwohl z.B. im sm.xml folgendes steht:
<!-- Log configuration - type is "syslog", "file" or "stdout" -->
<log type='file'>
<!--
<!-- If logging to syslog, this is the log ident -->
<ident>jabberd/sm</ident>
<!-- If logging to syslog, this is the log facility
(local0 - local7) [default: local3] -->
<facility>local3</facility>
-->
<!-- If logging to file, this is the filename of the logfile -->
<file>/cust/php/jabber/var/jabberd/log/sm.log</file>
</log>
***
Hat jemand eine Idee? Hilfe
nachdem ich das mit dem mu-conference (bei jabber 1.4) nicht hin bekommen habe,
versuche ichs jetzt mit jabber2.0
aber auch nicht besser...
ich habe alles so konfiguriert wie im Manual
( configure --prefix=/jabber --enable-ssl )
make
make install
usw...)
nun bin ich am Punkt wo er gestartet werden soll - Punkt 5(http://www.jabberdoc.org/section05.html)
das geht leider nicht: ich bekomme die FM:
mylinux:/jabber/etc/jabberd # /jabber/bin/jabberd -D
JBRD: debug on
JBRD: version(2.0rc1)
JBRD: config_dir(/jabber/etc/jabberd)
JBRD: LaunchJob: router -> /jabber/bin/router -c /jabber/etc/jabberd/router.xml -D
JBRD: LaunchJob: resolver -> /jabber/bin/resolver -c /jabber/etc/jabberd/resolver.xml -D
JBRD: LaunchJob: sm -> /jabber/bin/sm -c /jabber/etc/jabberd/sm.xml -D
JBRD: LaunchJob: s2s -> /jabber/bin/s2s -c /jabber/etc/jabberd/s2s.xml -D
JBRD: LaunchJob: c2s -> /jabber/bin/c2s -c /jabber/etc/jabberd/c2s.xml -D
RSLV: Thu Nov 20 13:29:15 2003 [notice] starting up
RSLV: Thu Nov 20 13:29:15 2003 [info] process id is 22269, written to /jabber/var/jabberd/pid/resolver.pid
RSLV: sx (sasl.c:533) initialising sasl plugin
ROUT: Thu Nov 20 13:29:15 2003 [notice] starting up
RSLV: Thu Nov 20 13:29:15 2003 [notice] attempting connection to router at 127.0.0.1, port=5347
ROUT: Thu Nov 20 13:29:15 2003 user.c:34 loading user table
ROUT: Thu Nov 20 13:29:15 2003 [info] process id is 22268, written to /jabber/var/jabberd/pid/router.pid
ROUT: Thu Nov 20 13:29:15 2003 user.c:89 remembering user 'jabberd'
S2S : Thu Nov 20 13:29:15 2003 [notice] starting up
ROUT: Thu Nov 20 13:29:15 2003 [notice] loaded user table (1 users)
ROUT: Thu Nov 20 13:29:15 2003 aci.c:37 loading aci
ERROR: sm died. Shutting down server.
JBRD: Got a signal... pass it on.
JBRD: It was a TERM. Shut it all down!
***
Und nu?
das komische ist ich finde keine logs.
obwohl z.B. im sm.xml folgendes steht:
<!-- Log configuration - type is "syslog", "file" or "stdout" -->
<log type='file'>
<!--
<!-- If logging to syslog, this is the log ident -->
<ident>jabberd/sm</ident>
<!-- If logging to syslog, this is the log facility
(local0 - local7) [default: local3] -->
<facility>local3</facility>
-->
<!-- If logging to file, this is the filename of the logfile -->
<file>/cust/php/jabber/var/jabberd/log/sm.log</file>
</log>
***
Hat jemand eine Idee? Hilfe