Date: Mon, 9 Jan 2006 14:55:48 GMT From: Lars Eggert <lars.eggert@gmx.net> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/91555: ejabberd-1.0.0 hangs at boot Message-ID: <200601091455.k09EtmKo057729@www.freebsd.org> Resent-Message-ID: <200601091500.k09F0Ffs085534@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 91555
>Category: ports
>Synopsis: ejabberd-1.0.0 hangs at boot
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jan 09 15:00:14 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Lars Eggert
>Release: 6.0-STABLE
>Organization:
NEC Network Laboratories
>Environment:
FreeBSD kobe.netlab.nec.de 6.0-STABLE FreeBSD 6.0-STABLE #3: Mon Jan 9 12:00:30 CET 2006 root@kobe.netlab.nec.de:/usr/obj/usr/src/sys/KOBE i386
>Description:
I just portupgraded to ejabberd-1.0.0 and have a problem: when ejabberd.sh executes at boot time, it just sits there and hangs the boot process.
Hitting Ctrl-C twice in the console kills the script and the boot process continues.
One more data point: When running ejabberd from the console, I see these three processes:
ejabberd 915 /usr/local/lib/erlang/erts-5.4.12/bin/epmd -daemon
ejabberd 916 [beam]
ejabberd 926 /usr/local/lib/erlang/lib/ssl-3.0.10/priv/bin/ssl_esock
After aborting the startup script, only the first two exists, which makes me think that the problem is with starting the third process...
>How-To-Repeat:
>Fix:
Manually starting ejabberd from the console after boot works, but is obviously not a good solution.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601091455.k09EtmKo057729>