[ejabberd] Strange problem with HTTP stuff on NetBSD

Jonathan Schleifer js at h3c.de
Mon Jun 18 15:24:58 MSD 2007


Magnus Henoch <mange at freemail.hu> wrote:

> NetBSD/macppc CURRENT, ejabberd 1.1.2 and SVN head, OTP R11B-1.

The current machine will be replaced with a new one soon which will be
running NetBSD/ofppc, so I could also try it on PPC then.

> None changed.

I'm using the following sysctls:
net.inet.tcp.mss_ifmtu=1
net.inet.ip.forwarding=1
net.inet6.ip6.v6only=0

I guess only the last will be of interest. But this shouldn't be a
problem since it's only listening on a pure IPv4 socket:

tcp        0      0  127.0.0.1.5280         *.*                    LISTEN

What's also interesting is that I get this after trying to connect to
port 5280:

tcp        0      0  127.0.0.1.5280         127.0.0.1.63012        TIME_WAIT

> erl -sname ejabberd -s ejabberd

I start it this way (quoting my ejabberd startup script):

#!/bin/sh
export HOME=/var/lib/ejabberd
export LD_LIBRARY_PATH=/usr/pkg/lib
ulimit -n 512
cd /var/lib/ejabberd
/usr/local/bin/erl -pa /var/lib/ejabberd/ebin \
        -sname ejabberd \
        -s ejabberd \
        -ejabberd config \"/etc/ejabberd/ejabberd.cfg\" \
                log_path \"/var/log/ejabberd/ejabberd.log\" \
        -sasl sasl_error_logger \{file,\"/var/log/ejabberd/sasl.log\"\} \
        -mnesia dir \"/var/lib/ejabberd/spool\" \
        -kernel inetrc \"/etc/ejabberd/inetrc\" \
        -noshell -detached

I also removed the -noshell -detached to see debug info, but there's
none regarding port 5280.

> > Do you have a inetrc file?
> 
> No.

Mine looks like this to fix some DNS issues:
{file, resolv, "/etc/resolv.conf"}.

> If you hadn't explicitly written 127.0.0.1 on the telnet command line,
> I might have suspected IPv6.  As it is enabled by default in NetBSD,
> some applications take "localhost" to mean only ::1, never 127.0.0.1,
> while ejabberd by default listens only on IPv4.  But that shouldn't be
> the problem here…

That was something I already thought about it. I even tried forcing it
to IPv6 and connecting via v6 then, but that does exactly the same.

Forgot to ask: Do you use the PgSQL native module? Maybe this could be
he reason?

To the others: Any idea how to debug this?

-- 
Jonathan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 618 bytes
Desc: not available
Url : http://lists.jabber.ru/pipermail/ejabberd/attachments/20070618/107770b7/attachment.pgp 


More information about the ejabberd mailing list