[Serusers] Debian unstable: ser starts but socket not open
Luna Kid
listreader at neuropolis.org
Sat Feb 28 17:39:37 CET 2004
Thanks, but I just forgot to tell that I already tried that. :-/
My new cfg:
--------------------------------------------
debug=7
fork=yes
log_stderror=no
dns=no # (cmd. line: -r)
rev_dns=no # (cmd. line: -R)
listen=sip.neuropolis.org
port=5060
children=2
fifo="/tmp/ser_fifo"
...
--------------------------------------------
But still the same:
# fuser -n tcp 5060
here: 5060
# fuser -n udp 5060
here: 5060
(Dunno what this "here" means here, but it is written for closed ports...)
Oops, now I guess, ser actually terminates prematurely. After
# /etc/init.d/ser start
/var/run/ser/ser.pid contains a PID which is not running any more. And
#ps aux | grep ser
gives nothing "ser-like"...
Also
# strace /usr/sbin/ser
gives:
...
write(1, "Listening on \n", 14Listening on
) = 14
write(1, " sip.neuropolis.org"..., 54 sip.neuropolis.org [212.52.166.10]:5060
) = 54
write(1, "Aliases: \n", 10Aliases:
) = 10
chdir("/") = 0
fork() = 23843
--- SIGCHLD (Child exited) @ 0 (0) ---
munmap(0x4001c000, 4096) = 0
exit_group(0) = ?
sniper:/var/run/ser#
Is this normal, possibly? What may I do wrong, please?
Thanks very much,
Sz.
----- Original Message -----
From: "Jiri Kuthan" <jiri at iptel.org>
To: "Luna Kid" <listreader at neuropolis.org>; <serusers at lists.iptel.org>
Sent: Saturday, February 28, 2004 5:21 PM
Subject: Re: [Serusers] Debian unstable: ser starts but socket not open
> Luna,
>
> turn on fork=yes -- fork=on is debugging mode which does not support TCP.
>
> -jiri
>
> At 05:13 PM 2/28/2004, Luna Kid wrote:
> >Just downloaded and installed the latest Debian unstable packages.
> >
> >When starting ser:
> >
> >-----------------
> >Listening on
> > sip.neuropolis.org [212.52.166.10]:5060
> >Aliases:
> >WARNING: no fork mode
> >stateless - initializing
> >Maxfwd module- initializing
> >------------------
> >
> >Still I cannot connect (e.g. telnet) to 5060. The socket is NOT actually
> >open. I guess my local Linux (Debian) config prevents ser from properly
> >opening that socket (just dunno, how).
> >
> ># fuser -n tcp 5060
> >here: 5060
> >
> ># uname -r
> >2.4.22
> >
> >Tried low port numbers, too. Nothing. Strange that ser does not seem to
> >complain.. Or does it? Here's a debug=7 log: http://sip.neuropolis.org/serlog.txt
> >
> >Some ser.cfg settings that may differ from the (latest) default stuff:
> >---------------------
> >debug=7
> >fork=no
> >log_stderror=no
> >check_via=no # (cmd. line: -v)
> >dns=no # (cmd. line: -r)
> >rev_dns=no # (cmd. line: -R)
> >listen=sip.neuropolis.org
> >port=5060
> >children=2
> >fifo="/tmp/ser_fifo"
> >
> >Thanks,
> >Luna Kid
> >
> >_______________________________________________
> >Serusers mailing list
> >serusers at lists.iptel.org
> >http://lists.iptel.org/mailman/listinfo/serusers
>
> --
> Jiri Kuthan http://iptel.org/~jiri/
>
>
More information about the sr-users
mailing list