Ciernik Tomas
06-02-2008, 12:55 PM
Hi all,
after upgrade from jabberd 2.1.23 to 2.2.0
jabberd is not able to start due to resolver error.
# /usr/local/bin/jabberd -D
JBRD: debug on
JBRD: version(2.2.0)
JBRD: config_dir(/usr/local/etc/jabberd)
JBRD: config(/usr/local/etc/jabberd/jabberd.cfg)
JBRD: LaunchJob: router -> /usr/local/bin/router -c
/usr/local/etc/jabberd/router.xml -D
JBRD: LaunchJob: resolver -> -c /usr/local/etc/jabberd/resolver.xml -D
JBRD: LaunchJob: sm -> /usr/local/bin/sm -c
/usr/local/etc/jabberd/sm-ciernik.sk.xml -D
JBRD: LaunchJob: sm -> /usr/local/bin/sm -c
/usr/local/etc/jabberd/sm-ciernikova.sk.xml -D
JBRD: LaunchJob: s2s -> /usr/local/bin/s2s -c
/usr/local/etc/jabberd/s2s.xml -D
JBRD: LaunchJob: c2s -> /usr/local/bin/c2s -c
/usr/local/etc/jabberd/c2s.xml -D
resolver: Can't exec "-c": No such file or directory at
/usr/local/lib/perl5/5.8.8/IPC/Open3.pm line 246.
ROUT: Mon Jun 2 12:16:34 2008 [notice] starting up
ERROR: resolver died. Shutting down server.
JBRD: Got a signal... pass it on.
JBRD: It was a TERM. Shut it all down!
Upgrade was made through portupgrade on freebsd 6.3 amd64.
Unfortunately resolver, c2s and s2s logs are empty, router and sm logs
just tell that both processes are started and after few seconds shutted
down.
Have you any idea what can cause this behavior?
Thank you in advance,
Tomas Ciernik.
_______________________________________________
JAdmin mailing list
FAQ: http://www.jabber.org/discussion-lists/jadmin-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=19
Info: http://mail.jabber.org/mailman/listinfo/jadmin
Unsubscribe: JAdmin-unsubscribe (AT) jabber (DOT) org
_______________________________________________
after upgrade from jabberd 2.1.23 to 2.2.0
jabberd is not able to start due to resolver error.
# /usr/local/bin/jabberd -D
JBRD: debug on
JBRD: version(2.2.0)
JBRD: config_dir(/usr/local/etc/jabberd)
JBRD: config(/usr/local/etc/jabberd/jabberd.cfg)
JBRD: LaunchJob: router -> /usr/local/bin/router -c
/usr/local/etc/jabberd/router.xml -D
JBRD: LaunchJob: resolver -> -c /usr/local/etc/jabberd/resolver.xml -D
JBRD: LaunchJob: sm -> /usr/local/bin/sm -c
/usr/local/etc/jabberd/sm-ciernik.sk.xml -D
JBRD: LaunchJob: sm -> /usr/local/bin/sm -c
/usr/local/etc/jabberd/sm-ciernikova.sk.xml -D
JBRD: LaunchJob: s2s -> /usr/local/bin/s2s -c
/usr/local/etc/jabberd/s2s.xml -D
JBRD: LaunchJob: c2s -> /usr/local/bin/c2s -c
/usr/local/etc/jabberd/c2s.xml -D
resolver: Can't exec "-c": No such file or directory at
/usr/local/lib/perl5/5.8.8/IPC/Open3.pm line 246.
ROUT: Mon Jun 2 12:16:34 2008 [notice] starting up
ERROR: resolver died. Shutting down server.
JBRD: Got a signal... pass it on.
JBRD: It was a TERM. Shut it all down!
Upgrade was made through portupgrade on freebsd 6.3 amd64.
Unfortunately resolver, c2s and s2s logs are empty, router and sm logs
just tell that both processes are started and after few seconds shutted
down.
Have you any idea what can cause this behavior?
Thank you in advance,
Tomas Ciernik.
_______________________________________________
JAdmin mailing list
FAQ: http://www.jabber.org/discussion-lists/jadmin-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=19
Info: http://mail.jabber.org/mailman/listinfo/jadmin
Unsubscribe: JAdmin-unsubscribe (AT) jabber (DOT) org
_______________________________________________