7 Oct
2003
7 Oct
'03
11:57 a.m.
Hello,
On 10/7/2003 8:29 AM, 郝育鹏 wrote:
[...]
4, SER logs :
When I apply the following configuration options: debug=8,
log_stderror=yes,
fork=no. show this information:
.....
0(0) DEBUG: udp_init: trying SO_RCVBUF: 262140
0(0) DEBUG: setting SO_RCVBUF; set=262140,verify=131070
0(0) DEBUG: setting SO_RCVBUF has no effect
0(0) DEBUG: udp_init: trying SO_RCVBUF: 133118
0(0) DEBUG: setting SO_RCVBUF; set=133118,verify=131070
0(0) DEBUG: setting SO_RCVBUF has no effect
0(0) INFO: udp_init: SO_RCVBUF is finally 131070
0(0) WARNING: using only the first listen address (no fork)
as I told you, only the first network interface is used and that is
127.0.0.1
1(4499) DBG: open_uac_fifo: opening fifo...
1(4499) DEBUG: fifo /tmp/ser_fifo opened, mode=438
0(4497) DEBUG: init_mod_child (1): tm
0(4497) DEBUG: callid: '763e7fde-4497(a)127.0.0.1'
<mailto:%27763e7fde-4497@127.0.0.1%27>
0(4497) DEBUG: init_mod_child (1): usrloc
1(4499) DEBUG: init_mod_child (-1): tm
1(4499) DEBUG: callid: '763e7fde-4499(a)127.0.0.1'
<mailto:%27763e7fde-4499@127.0.0.1%27>
1(4499) DEBUG: init_mod_child (-1): usrloc
2(4500) INFO: fifo process starting: 4500
2(4500) DEBUG: init_mod_child (-2): tm
2(4500) DEBUG: callid: '763e7fde-4500(a)127.0.0.1'
<mailto:%27763e7fde-4500@127.0.0.1%27>
2(4500) DEBUG: init_mod_child (-2): usrloc
1(4499) DEBUG: init_mod_child (-1): auth_db
0(4497) DEBUG: init_mod_child (1): auth_db
2(4500) DEBUG: init_mod_child (-2): auth_db
2(4500) SER: open_uac_fifo: fifo server up at /tmp/ser_fifo...
It's no longer running,always stop! why? My SER log is :
Are you sure is not running? It stops here until a SIP request is
received and then displays other debug messages.
....
Oct 7 13:30:05 Lserver ser: WARNING: could not rev. resolve 210.72.128.44
Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: Listening on
Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: 127.0.0.1 [127.0.0.1
]:5060
Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: 192.168.0.179 [192.1
68.0.179]:5060
Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: 210.72.128.44 [210.7
2.128.44]:5060
Oct 7 13:30:05 Lserver 10月 7 13:30:05 ser: Aliases:
Lserver.sict.net:5060 loc
alhost:5060 localhost.localdomain:5060 Lserver:5060 Lserver.net:*
Oct 7 13:30:06 Lserver 10月 7 13:30:05 ser: ser startup succeeded
Oct 7 13:49:07 Lserver 10月 7 13:49:07 ser: ser shutdown failed
Oct 7 13:50:42 Lserver ser: parse error (14,1-2): parse error
Here you had some errors in your config file (line 14), ser didn't start
at that moment.
Regards,
}Daniel
Oct 7 13:50:42 Lserver ser: parse error (14,1-2):
Oct 7 13:51:24 Lserver ser: WARNING: could not rev. resolve 210.72.128.44
[root@Lserver /]#
----- Original Message -----
From: "Daniel-Constantin Mierla"
<Daniel-Constantin.Mierla(a)fokus.fraunhofer.de
<mailto:Daniel-Constantin.Mierla@fokus.fraunhofer.de>>
To: "郝育鹏" <haoypeng(a)sict.ac.cn <mailto:haoypeng@sict.ac.cn>>
Cc: <serusers(a)lists.iptel.org <mailto:serusers@lists.iptel.org>>
Sent: Monday, October 06, 2003 7:26 PM
Subject: Re: [Serusers] Can you help me!
Hello,
did you add some users into database?
Please follow the guidelines from http://www.iptel.org/ser/bugs/ and
send us the result. We can't guess everything what happen into your
system only from config file.
You have commented some global parameters and that changed the behavior
SER should have with default config file -- you even commented the
number of children that means ser listens only on first network
interface (I have to double check it, but it should be like that), and
that is usually 127.0.0.1. We need the log messages, network dumps and
so on ...
Regards,
"Daniel
------------------------------------------------------------------------
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers