Jiri Kuthan,
Thanks for your help, I found the problem reason according your analysis.
First I modified the debug level in ser.cfg
# Debug level on logging
debug=4
# Fork and create children (no=run single process for debugging purposes)
fork=no
# Log to stderr (only use this of fork=no)
log_stderror=yes
And running SER again, and get the follow messages:
0(10768) qm_malloc(0x5e0b20, 9) called from xl_lib.c: xl_mod_init(1649)
0(10768) qm_malloc(0x5e0b20, 16) returns address 0x61dcd0 frag. 0x61dca0
(size=56) on 1 -th hit
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10768) qm_free(0x5e0b20, 0x61db30), called from xl_lib.c:
xl_mod_init(1667)
0(10768) qm_free: freeing frag. 0x61db00 alloc'ed from xl_lib.c:
xl_mod_init(1628)
0(10768) Hostname: sipmcu
0(10768) Domainname: leadtek.com.cn
0(10768) Fullname: sipmcu.leadtek.com.cn
0(10768) IPaddr: 10.0.0.21
0(10768) DEBUG: init_mod: ctl
0(10768) listening on:
0(10768) [binrpc:tcp] 127.0.0.1:2049
0(10768) [fifo:fifo] /tmp/ser_fifo
0(10768) [binrpc:unix stream] /tmp/ser_ctl
0(10768) ERROR: init_tcpudp_sock: bind: Address already in use [98]
0(10768) ERROR: ctl: mod_init: init ctrl. sockets failed
0(10768) init_mod(): Error while initializing module ctl
ERROR: error while initializing modules
0(10768) qm_free(0x5e0b20, 0x617d98), called from sr_module.c:
destroy_modules(393)
the 2049 port that Ser want to use is used by NFS. As described In
/etc/services:
nfs 2049/tcp nfsd
nfs 2049/udp nfsd
And the NFS service is running on my machine too.
After stopped NFS and running SER again, It seemed OK.
[frank@sipmcu ser]$ ../../sbin/ser -f ser.cfg
Listening on
udp: 10.0.0.21 [10.0.0.21]:5060
tcp: 10.0.0.21 [10.0.0.21]:5060
Aliases:
tcp: sipmcu.mydomain.com.cn:5060
udp: sipmcu.mydomain.com.cn:5060
*: mytestser.org:*
WARNING: no fork mode
0(10945) init_tcp: using epoll_lt as the io watch method (auto detected)
0(10945) Maxfwd module- initializing
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) WARNING: xl_mod_init: more IP 10.0.0.21 not used
0(10945) INFO: udp_init: SO_RCVBUF is initially 135168
0(10945) INFO: udp_init: SO_RCVBUF is finally 262142
So if can SER change binrpc:tcp port to another value to avoid conflict with
NFS port?
Best Regards,
Frank
2007/9/12, Jiri Kuthan <jiri(a)iptel.org>rg>:
At 11:55 12/09/2007, Frank Wang wrote:
I downloaded ser 2.0.0-rc1 source code from <
http://www.iptel.org/ser_2_0_0_release_candidate_1>
http://www.iptel.org/ser_2_0_0_release_candidate_1 and install on my Linux
step by step according the tutorial on the WEB.
When I running SER, I got follow messages:
[root@sipmcu ser]# ../../sbin/ser -f ser.cfg
Listening on
udp: <http://10.0.0.21>10.0.0.21 [<http://10.0.0.21>
10.0.0.21]:5060
tcp:
<http://10.0.0.21>10.0.0.21 [<http://10.0.0.21>
10.0.0.21]:5060
Aliases:
tcp: <http://sipmcu.leadtek.com.cn:5060>
sipmcu.leadtek.com.cn:5060
udp:
<http://sipmcu.leadtek.com.cn:5060>
sipmcu.leadtek.com.cn:5060
*: mytestser.org:*
WARNING: no fork mode
0(3078) init_tcp: using epoll_lt as the io watch method (auto detected)
0(3078) Maxfwd module- initializing
0(3078) WARNING: xl_mod_init: more IP <http://10.0.0.21>10.0.0.21 not
used
unimportant. (I checked the code and I was a bit puzzled by it, but it
really
shold not matter much.)
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) WARNING: xl_mod_init: more IP
<http://10.0.0.21>10.0.0.21 not
used
0(3078) ERROR: init_tcpudp_sock: bind: Address
already in use [98]
This is the problem. Maybe you have a SER instance running from the last
time and you are starting
the script again, for which reason SER can't be restarted -- it can't
claim the same port number
twice.
0(3078) ERROR: ctl: mod_init: init ctrl. sockets
failed
0(3078) init_mod(): Error while initializing module ctl
ERROR: error while initializing modules
This could have same reason.
could anybody tell me how about it? Thanks a lot.
Regards,
Frank
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan
http://iptel.org/~jiri/