Hi Bogdan,
I followed Henning's advice and I increased the shared memory to 128MB
(-m 128). I haven't seen this ERROR since then.
However this is an error that I have only seen once. Maybe during those
three minutes something very unusual happened.
Regards,
George
-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro]
Sent: Thursday, June 21, 2007 4:51 PM
To: Papadopoulos Georgios
Cc: users(a)openser.org; Henning Westerholt
Subject: Re: [Users] ERROR: sip_msg_cloner: cannot allocate memory
HI George,
any feedback on this? Henning was asking you to see if there
is a memory outage or leak...any result?
regards,
bogdan
Papadopoulos Georgios wrote:
Hello all,
I am running Openser 1.2 for several days and whithin a period of
three minutes I got a lot of these messages:
Jun 8 10:27:41 ser1 openser[23287]: ERROR: new_t: out of mem:
Jun 8 10:27:41 ser1 openser[23287]: ERROR: t_newtran: new_t failed
Jun 8 10:27:41 ser1 openser[23287]: ERROR: new_t: out of mem:
Jun 8 10:27:41 ser1 openser[23287]: ERROR: t_newtran: new_t failed
Jun 8 10:27:42 ser1 openser[23279]: ERROR: sip_msg_cloner: cannot
allocate memory Jun 8 10:27:42 ser1 openser[23279]: ERROR:
new_t: out
of mem:
Jun 8 10:27:42 ser1 openser[23279]: ERROR: t_newtran: new_t failed
Jun 8 10:27:42 ser1 openser[23279]: ERROR: sip_msg_cloner: cannot
allocate memory Jun 8 10:27:42 ser1 openser[23279]: ERROR:
new_t: out
of mem:
Jun 8 10:27:42 ser1 openser[23279]: ERROR: t_newtran: new_t failed
Jun 8 10:27:42 ser1 openser[23279]: ERROR:tm:relay_reply: cannot
alloc reply shmem Jun 8 10:27:42 ser1 openser[23287]:
ERROR:tm:relay_reply: cannot alloc reply shmem Jun 8 10:27:42 ser1
openser[23287]: ERROR:tm:_reply_light: cannot allocate shmem buffer
Jun 8 10:27:42 ser1 openser[23279]: ERROR:tm:_reply_light: cannot
allocate shmem buffer They only appeared in the log for a
few minutes
and then they stopped.
After this happened I got the following statistics and ps info.
[root@ser1 sbin]# ./openserctl fifo get_statistics all
core:rcv_requests = 34449564 core:rcv_replies = 14967742
core:fwd_requests = 78714 core:fwd_replies = 15461
core:drop_requests
= 49337 core:drop_replies = 0 core:err_requests =
0
core:err_replies =
250 core:bad_URIs_rcvd = 457
core:unsupported_methods = 471
core:bad_msg_hdr = 389075 shmem:total_size = 33554432
shmem:used_size
= 4467768 shmem:real_used_size = 4731144
shmem:max_used_size =
33052304 shmem:free_size = 28823288 shmem:fragments = 9383
sl:1xx_replies = 0 sl:2xx_replies = 16962574 sl:3xx_replies = 2306
sl:4xx_replies = 4501596 sl:5xx_replies = 12366570
sl:6xx_replies = 0
sl:sent_replies = 33833046 sl:sent_err_replies =
275
sl:received_ACKs
= 49337 tm:received_replies = 14952031
tm:relayed_replies =
14702762
tm:local_replies = 69373 tm:UAS_transactions =
14671506
tm:UAC_transactions = 0 tm:2xx_transactions = 14551357
tm:3xx_transactions = 0 tm:4xx_transactions = 113514
tm:5xx_transactions = 9327 tm:6xx_transactions = 1
tm:inuse_transactions = 248 usrloc:registered_users = 2668
usrloc:location-users = 2668 usrloc:location-contacts = 2844
usrloc:location-expires = 53356 registrar:max_expires = 600
registrar:max_contacts = 10 registrar:default_expire = 600
registrar:accepted_regs = 14722245 registrar:rejected_regs = 43947
[root@ser1 sbin]# ./openserctl ps
Process:: ID=0 PID=23265 Type=attendant
Process:: ID=1 PID=23279 Type=receiver child=0 sock=
xxx.xxx.xxx.xxx:5060
Process:: ID=2 PID=23284 Type=receiver child=1 sock=
xxx.xxx.xxx.xxx:5060
Process:: ID=3 PID=23287 Type=receiver child=2 sock=
xxx.xxx.xxx.xxx:5060
Process:: ID=4 PID=23290 Type=receiver child=0 sock=
yyy.yyy.yyy.yyy:5060
Process:: ID=5 PID=23292 Type=receiver child=1 sock=
yyy.yyy.yyy.yyy:5060
Process:: ID=6 PID=23293 Type=receiver child=2 sock=
yyy.yyy.yyy.yyy:5060
Process:: ID=7 PID=23297 Type=receiver child=0 sock=
zzz.zzz.zzz.zzz:5060
Process:: ID=8 PID=23300 Type=receiver child=1 sock=
zzz.zzz.zzz.zzz:5060
Process:: ID=9 PID=23303 Type=receiver child=2 sock=
zzz.zzz.zzz.zzz:5060
Process:: ID=10 PID=23306 Type=receiver child=0 sock=
qqq.qqq.qqq.qqq:5060
Process:: ID=11 PID=23309 Type=receiver child=1 sock=
qqq.qqq.qqq.qqq:5060
Process:: ID=12 PID=23310 Type=receiver child=2 sock=
qqq.qqq.qqq.qqq:5060
Process:: ID=13 PID=23311 Type=receiver child=0 sock=
vvv.vvv.vvv.vvv:5060
Process:: ID=14 PID=23318 Type=receiver child=1 sock=
vvv.vvv.vvv.vvv:5060
Process:: ID=15 PID=23321 Type=receiver child=2 sock=
vvv.vvv.vvv.vvv:5060
Process:: ID=16 PID=23324 Type=timer
Does anyone know what might be causing these errors?
Thank you
George
Disclaimer
The information in this e-mail and any attachments is
confidential. It
is intended solely for the attention and use of
the named
addressee(s). If you are not the intended recipient, or person
responsible for delivering this information to the intended
recipient,
please notify the sender immediately. Unless you
are the intended
recipient or his/her representative you are not authorized to, and
must not, read, copy, distribute, use or retain this message or any
part of it. E-mail transmission cannot be guaranteed to be
secure or
error-free as information could be intercepted,
corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses.
----------------------------------------------------------------------
--
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users