[Serusers] Problem using Serctl Monitor SER is static
Martin Coggin
martin at mc2-consulting.co.uk
Sun Apr 18 12:47:17 CEST 2004
When I run serctl monitor I get the following output:
[cycle #: 1; if constant make sure server lives and fifo is on]
and nothing else. When I use top to see what processes are running I
can see that the ser processes are there but they are sleeping, ie stat
S, a sample of the output is as follows:
7306 ser 9 0 2884 2884 2860 S 0.0 4.5 0:00 ser
7307 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
7308 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
7309 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
7310 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
7311 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
7312 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
7313 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
7314 ser 9 0 2852 2852 2820 S 0.0 4.5 0:00 ser
When I use serctl fifo commands of fifo uptime and fifo ps I get the
following output.
hattie:/home/martinc# serctl fifo version
Server: Sip EXpress router (0.8.12 (i386/linux))
hattie:/home/martinc# serctl fifo uptime
Now: Sun Apr 18 11:29:31 2004
Up Since: Sun Apr 4 13:01:29 2004
Up time: 1204082 [sec]
hattie:/home/martinc# serctl fifo ps
0 7306 attendant
1 7307 receiver child=0 sock=0 @ 127.0.0.1:5060
2 7308 receiver child=1 sock=0 @ 127.0.0.1:5060
3 7309 receiver child=2 sock=0 @ 127.0.0.1:5060
4 7310 receiver child=3 sock=0 @ 127.0.0.1:5060
5 7311 receiver child=4 sock=0 @ 127.0.0.1:5060
6 7312 receiver child=5 sock=0 @ 127.0.0.1:5060
7 7313 receiver child=6 sock=0 @ 127.0.0.1:5060
8 7314 receiver child=7 sock=0 @ 127.0.0.1:5060
9 7315 receiver child=0 sock=1 @ 192.168.0.100:5060
10 7316 receiver child=1 sock=1 @ 192.168.0.100:5060
11 7317 receiver child=2 sock=1 @ 192.168.0.100:5060
12 7318 receiver child=3 sock=1 @ 192.168.0.100:5060
13 7319 receiver child=4 sock=1 @ 192.168.0.100:5060
14 7320 receiver child=5 sock=1 @ 192.168.0.100:5060
15 7321 receiver child=6 sock=1 @ 192.168.0.100:5060
16 7322 receiver child=7 sock=1 @ 192.168.0.100:5060
17 7323 fifo server
18 7324 timer
19 7325 tcp receiver
20 7326 tcp receiver
21 7327 tcp receiver
22 7328 tcp receiver
23 7329 tcp receiver
24 7330 tcp receiver
25 7331 tcp receiver
26 7332 tcp receiver
27 7333 tcp main process
I assume Im missing something here and that despite all the info to the
contrary ser is not running as the output of serctl monitor cycle 1 is
static. What configuration changes are needed to this thing?
Best regards Martin Coggin
Information in this message is confidential and may be legally
privileged. It is intended solely for the person to whom it is
addressed. If you have received this email in error please delete it
immediately and also reply to me to let me know. Thank you for your
help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20040418/a68bcb2f/attachment.htm>
More information about the sr-users
mailing list