1 Feb
2009
1 Feb
'09
9:12 p.m.
Greetings,
Trying to compile openser 1.3.3 without PKG_MALLOC, just using OS malloc
Here's me Makefile.defs
DEFS+= $(extra_defs) \
-DNAME='"$(MAIN_NAME)"' -DVERSION='"$(RELEASE)"'
-DARCH='"$(ARCH)"' \
-DOS='"$(OS)"' -DCOMPILER='"$(CC_VER)"'
-D__CPU_$(ARCH) -D__OS_$(OS) \
-D__SMP_$(ISSMP) -DCFG_DIR='"$(cfg-target)"'\
-DSHM_MEM -DSHM_MMAP \
#-DPKG_MALLOC \
-DUSE_IPV6 \
-DUSE_MCAST \
-DUSE_TCP \
-DDISABLE_NAGLE \
-DHAVE_RESOLV_RES \
-DSTATISTICS \
-DCHANGEABLE_DEBUG_LEVEL \
#-DF_MALLOC \
-DQM_JOIN_FREE \
#-DDBG_QM_MALLOC \
#-DDBG_F_MALLOC \
#-DNO_DEBUG \
#-DNO_LOG \
#-DVQ_MALLOC \
#-DDBG_LOCK \
#-DNOSMP \
#-DEXTRA_DEBUG \
#-DUSE_SHM_MEM
It's bailing out compiling blacklists.c
blacklists.c: In function `rm_dups':
blacklists.c:435: error: syntax error before "else"
blacklists.c:440: error: syntax error before "else"
blacklists.c: At top level:
blacklists.c:443: error: syntax error before "else"
blacklists.c:445: warning: type defaults to `int' in declaration of `q'
blacklists.c:445: error: invalid type argument of `->'
blacklists.c:445: warning: data definition has no type or storage class
blacklists.c:446: error: syntax error before '}' token
make: *** [blacklists.o] Error 1
Did anybody had a problem compiling openser without pkg_malloc support?
I would appreciate any help.
TIA
Toly.
--
View this message in context:
http://www.nabble.com/Trying-to-compile-openser-1.3.3-without-PKG_MALLOC-su…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
2 Feb
2 Feb
3:50 a.m.
I got it. Thanks anyway.
toly wrote:
Greetings,
Trying to compile openser 1.3.3 without PKG_MALLOC, just using OS malloc
Here's me Makefile.defs
DEFS+= $(extra_defs) \
-DNAME='"$(MAIN_NAME)"' -DVERSION='"$(RELEASE)"'
-DARCH='"$(ARCH)"' \
-DOS='"$(OS)"' -DCOMPILER='"$(CC_VER)"'
-D__CPU_$(ARCH) -D__OS_$(OS) \
-D__SMP_$(ISSMP) -DCFG_DIR='"$(cfg-target)"'\
-DSHM_MEM -DSHM_MMAP \
#-DPKG_MALLOC \
-DUSE_IPV6 \
-DUSE_MCAST \
-DUSE_TCP \
-DDISABLE_NAGLE \
-DHAVE_RESOLV_RES \
-DSTATISTICS \
-DCHANGEABLE_DEBUG_LEVEL \
#-DF_MALLOC \
-DQM_JOIN_FREE \
#-DDBG_QM_MALLOC \
#-DDBG_F_MALLOC \
#-DNO_DEBUG \
#-DNO_LOG \
#-DVQ_MALLOC \
#-DDBG_LOCK \
#-DNOSMP \
#-DEXTRA_DEBUG \
#-DUSE_SHM_MEM
It's bailing out compiling blacklists.c
blacklists.c: In function `rm_dups':
blacklists.c:435: error: syntax error before "else"
blacklists.c:440: error: syntax error before "else"
blacklists.c: At top level:
blacklists.c:443: error: syntax error before "else"
blacklists.c:445: warning: type defaults to `int' in declaration of `q'
blacklists.c:445: error: invalid type argument of `->'
blacklists.c:445: warning: data definition has no type or storage class
blacklists.c:446: error: syntax error before '}' token
make: *** [blacklists.o] Error 1
Did anybody had a problem compiling openser without pkg_malloc support?
I would appreciate any help.
TIA
Toly.
--
View this message in context:
http://www.nabble.com/Trying-to-compile-openser-1.3.3-without-PKG_MALLOC-su…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
7:16 p.m.
Hello,
On 02/02/2009 03:50 AM, toly wrote:
I got it. Thanks anyway.
what was the problem? Others might learn from your experience ...
Cheers,
Daniel
toly wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com
Greetings,
Trying to compile openser 1.3.3 without PKG_MALLOC, just using OS malloc
Here's me Makefile.defs
DEFS+= $(extra_defs) \
-DNAME='"$(MAIN_NAME)"' -DVERSION='"$(RELEASE)"'
-DARCH='"$(ARCH)"' \
-DOS='"$(OS)"' -DCOMPILER='"$(CC_VER)"'
-D__CPU_$(ARCH) -D__OS_$(OS) \
-D__SMP_$(ISSMP) -DCFG_DIR='"$(cfg-target)"'\
-DSHM_MEM -DSHM_MMAP \
#-DPKG_MALLOC \
-DUSE_IPV6 \
-DUSE_MCAST \
-DUSE_TCP \
-DDISABLE_NAGLE \
-DHAVE_RESOLV_RES \
-DSTATISTICS \
-DCHANGEABLE_DEBUG_LEVEL \
#-DF_MALLOC \
-DQM_JOIN_FREE \
#-DDBG_QM_MALLOC \
#-DDBG_F_MALLOC \
#-DNO_DEBUG \
#-DNO_LOG \
#-DVQ_MALLOC \
#-DDBG_LOCK \
#-DNOSMP \
#-DEXTRA_DEBUG \
#-DUSE_SHM_MEM
It's bailing out compiling blacklists.c
blacklists.c: In function `rm_dups':
blacklists.c:435: error: syntax error before "else"
blacklists.c:440: error: syntax error before "else"
blacklists.c: At top level:
blacklists.c:443: error: syntax error before "else"
blacklists.c:445: warning: type defaults to `int' in declaration of `q'
blacklists.c:445: error: invalid type argument of `->'
blacklists.c:445: warning: data definition has no type or storage class
blacklists.c:446: error: syntax error before '}' token
make: *** [blacklists.o] Error 1
Did anybody had a problem compiling openser without pkg_malloc support?
I would appreciate any help.
TIA
Toly.
4 Feb
4 Feb
6:29 p.m.
the problem was:
file mem/mem.h
8th line from the bottom
original:
define pkg_free(p) do{ LM_DBG("free %p\n", (p)); free((p)); }while(0);
the semicolon at the end of the line must be removed.
Toly
miconda wrote:
Hello,
On 02/02/2009 03:50 AM, toly wrote:
--
View this message in context:
http://www.nabble.com/Trying-to-compile-openser-1.3.3-without-PKG_MALLOC-su…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
I got it. Thanks anyway.
what was the problem? Others might learn from your experience ...
Cheers,
Daniel
toly wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Greetings,
Trying to compile openser 1.3.3 without PKG_MALLOC, just using OS malloc
Here's me Makefile.defs
DEFS+= $(extra_defs) \
-DNAME='"$(MAIN_NAME)"' -DVERSION='"$(RELEASE)"'
-DARCH='"$(ARCH)"' \
-DOS='"$(OS)"' -DCOMPILER='"$(CC_VER)"'
-D__CPU_$(ARCH) -D__OS_$(OS) \
-D__SMP_$(ISSMP) -DCFG_DIR='"$(cfg-target)"'\
-DSHM_MEM -DSHM_MMAP \
#-DPKG_MALLOC \
-DUSE_IPV6 \
-DUSE_MCAST \
-DUSE_TCP \
-DDISABLE_NAGLE \
-DHAVE_RESOLV_RES \
-DSTATISTICS \
-DCHANGEABLE_DEBUG_LEVEL \
#-DF_MALLOC \
-DQM_JOIN_FREE \
#-DDBG_QM_MALLOC \
#-DDBG_F_MALLOC \
#-DNO_DEBUG \
#-DNO_LOG \
#-DVQ_MALLOC \
#-DDBG_LOCK \
#-DNOSMP \
#-DEXTRA_DEBUG \
#-DUSE_SHM_MEM
It's bailing out compiling blacklists.c
blacklists.c: In function `rm_dups':
blacklists.c:435: error: syntax error before "else"
blacklists.c:440: error: syntax error before "else"
blacklists.c: At top level:
blacklists.c:443: error: syntax error before "else"
blacklists.c:445: warning: type defaults to `int' in declaration of `q'
blacklists.c:445: error: invalid type argument of `->'
blacklists.c:445: warning: data definition has no type or storage class
blacklists.c:446: error: syntax error before '}' token
make: *** [blacklists.o] Error 1
Did anybody had a problem compiling openser without pkg_malloc support?
I would appreciate any help.
TIA
Toly.
6:44 p.m.
New subject: [Kamailio-Users] Trying to compile openser 1.3.3 without PKG_MALLOC support
On Wednesday 04 February 2009, toly wrote:
the problem was:
file mem/mem.h
8th line from the bottom
original:
define pkg_free(p) do{ LM_DBG("free %p\n", (p)); free((p)); }while(0);
the semicolon at the end of the line must be removed.
Hi toly,
i fixed this some time ago for the 1.4.x branch, but aparently this was not
backported to 1.3.x. I'll do this now.
Cheers,
Henning
6:47 p.m.
New subject: [Kamailio-Users] Trying to compile openser 1.3.3 without PKG_MALLOC support
On Wednesday 04 February 2009, Henning Westerholt wrote:
I was wrong, this was already committed, its fixed in OpenSER 1.3.4.
Cheers,
Henning
file
mem/mem.h
8th line from the bottom
original:
define pkg_free(p) do{ LM_DBG("free %p\n", (p)); free((p)); }while(0);
the semicolon at the end of the line must be removed.
i fixed this some time ago for the 1.4.x branch, but aparently this was not
backported to 1.3.x. I'll do this now.
12 Feb
12 Feb
4:57 p.m.
New subject: [Kamailio-Users] Trying to compile openser 1.3.3 without PKG_MALLOC support
On Wednesday 04 February 2009, toly wrote:
the problem was:
file mem/mem.h
Hi Toly,
may i ask how were your experiences so far without the PKG_MALLOC memory
manager? Any performance problems, or perhaps instabilities that you would
credit to this?
Cheers,
Henning
13 Feb
13 Feb
5:41 a.m.
Hi Henning,
We are running the test:
hammer->sbc(asterisk 1.4)->openser1.3.3->mediaserver(heavily modified
asterisk)
It is production environment.
call rate is steady 4 cps.
Proxy is 2 dual cores 2.5Ghz with 4G of ram
Initially openser was compiled with private memory size of 4M.
After few days privated memory was heavily fragmented and proxy was running
out of memory.
Then I've compiled with 8M of ram.
It prolonged more but with the same result, which made me very nervous and
PKG_MALLOC was out of the question.
Without PKG_MALLOC:
There were few runs for few days, the last one since last friday still
running.
No instabilities on proxy, no problems at all. Performance wise I have not
notice any difference. It may be subjective, I'd say cpu may be higher (%0.1
sometimes) but again it's subjective and I'm running ngrep logging via
syslog_ng and the proxy logging done via syslog_ng, configured (syslog_ng)
to send the output to the syslog_ng server and pumping all huge output via
syslog_ng may contribute to the CPU.
BTW, in main.c when opens syslog, there is the thing which may be qualified
as bug. I you use standard syslog then there is no problem. With syslog_ng,
there is the problem: it creates 2 log files and I've fixed main.c, by the
code it writes in syslog, and then when daemonized opens syslog.
In turn, I'd like to ask the question about ngrep. I'm using ngrep-1-45.
When running on proxy I see duplicate message. When running not on proxy -
no dups.
My hunch is that it's recording all stuff from on_reply_route and
loose_route?
Can anybody enlighten this subject.
Regards,
Toly
Henning Westerholt-2 wrote:
On Wednesday 04 February 2009, toly wrote:
--
View this message in context:
http://www.nabble.com/Trying-to-compile-openser-1.3.3-without-PKG_MALLOC-su…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
the problem was:
file mem/mem.h
Hi Toly,
may i ask how were your experiences so far without the PKG_MALLOC memory
manager? Any performance problems, or perhaps instabilities that you would
credit to this?
Cheers,
Henning
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
5:37 a.m.
How is Asterisk an SBC?
toly wrote:
Hi Henning,
We are running the test:
hammer->sbc(asterisk 1.4)->openser1.3.3->mediaserver(heavily modified
asterisk)
It is production environment.
call rate is steady 4 cps.
Proxy is 2 dual cores 2.5Ghz with 4G of ram
Initially openser was compiled with private memory size of 4M.
After few days privated memory was heavily fragmented and proxy was running
out of memory.
Then I've compiled with 8M of ram.
It prolonged more but with the same result, which made me very nervous and
PKG_MALLOC was out of the question.
Without PKG_MALLOC:
There were few runs for few days, the last one since last friday still
running.
No instabilities on proxy, no problems at all. Performance wise I have not
notice any difference. It may be subjective, I'd say cpu may be higher (%0.1
sometimes) but again it's subjective and I'm running ngrep logging via
syslog_ng and the proxy logging done via syslog_ng, configured (syslog_ng)
to send the output to the syslog_ng server and pumping all huge output via
syslog_ng may contribute to the CPU.
BTW, in main.c when opens syslog, there is the thing which may be qualified
as bug. I you use standard syslog then there is no problem. With syslog_ng,
there is the problem: it creates 2 log files and I've fixed main.c, by the
code it writes in syslog, and then when daemonized opens syslog.
In turn, I'd like to ask the question about ngrep. I'm using ngrep-1-45.
When running on proxy I see duplicate message. When running not on proxy -
no dups.
My hunch is that it's recording all stuff from on_reply_route and
loose_route?
Can anybody enlighten this subject.
Regards,
Toly
Henning Westerholt-2 wrote:
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
On Wednesday 04 February 2009, toly wrote:
the problem was:
file mem/mem.h
Hi Toly,
may i ask how were your experiences so far without the PKG_MALLOC memory
manager? Any performance problems, or perhaps instabilities that you would
credit to this?
Cheers,
Henning
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
4:22 p.m.
On 02/13/2009 05:37 AM, Alex Balashov wrote:
How is Asterisk an SBC?
By using it as b2bua you can get an SBC - it cleans the headers, relays
media...
However, definitions of scb and b2bua are vague, so if ti does what you
need for a sbc, you can call it so. Some time I am labeling kamailio as
sbc, when I place it at entrance/exit of internal network - it just does
source IP checking, flood detection and some time load balancing... at
least I know the sip message is fairly well formatted after goes through.
Cheers,
Daniel
toly wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com
Hi Henning,
We are running the test:
hammer->sbc(asterisk 1.4)->openser1.3.3->mediaserver(heavily modified
asterisk)
It is production environment.
call rate is steady 4 cps.
Proxy is 2 dual cores 2.5Ghz with 4G of ram
Initially openser was compiled with private memory size of 4M.
After few days privated memory was heavily fragmented and proxy was running
out of memory.
Then I've compiled with 8M of ram.
It prolonged more but with the same result, which made me very nervous and
PKG_MALLOC was out of the question.
Without PKG_MALLOC:
There were few runs for few days, the last one since last friday still
running.
No instabilities on proxy, no problems at all. Performance wise I have not
notice any difference. It may be subjective, I'd say cpu may be higher (%0.1
sometimes) but again it's subjective and I'm running ngrep logging via
syslog_ng and the proxy logging done via syslog_ng, configured (syslog_ng)
to send the output to the syslog_ng server and pumping all huge output via
syslog_ng may contribute to the CPU.
BTW, in main.c when opens syslog, there is the thing which may be qualified
as bug. I you use standard syslog then there is no problem. With syslog_ng,
there is the problem: it creates 2 log files and I've fixed main.c, by the
code it writes in syslog, and then when daemonized opens syslog.
In turn, I'd like to ask the question about ngrep. I'm using ngrep-1-45.
When running on proxy I see duplicate message. When running not on proxy -
no dups.
My hunch is that it's recording all stuff from on_reply_route and
loose_route?
Can anybody enlighten this subject.
Regards,
Toly
Henning Westerholt-2 wrote:
> On Wednesday 04 February 2009, toly wrote:
>
>> the problem was:
>>
>> file mem/mem.h
>>
> Hi Toly,
>
> may i ask how were your experiences so far without the PKG_MALLOC memory
> manager? Any performance problems, or perhaps instabilities that you would
> credit to this?
>
> Cheers,
>
> Henning
>
> _______________________________________________
> Kamailio (OpenSER) - Users mailing list
> Users(a)lists.kamailio.org
> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>
>
>
9:23 p.m.
We observe the crashes after about 300000 calls, in the asterisk code.
Alex Balashov wrote:
How is Asterisk an SBC?
toly wrote:
--
View this message in context:
http://www.nabble.com/Trying-to-compile-openser-1.3.3-without-PKG_MALLOC-su…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
Hi Henning,
We are running the test:
hammer->sbc(asterisk 1.4)->openser1.3.3->mediaserver(heavily modified
asterisk)
It is production environment.
call rate is steady 4 cps.
Proxy is 2 dual cores 2.5Ghz with 4G of ram
Initially openser was compiled with private memory size of 4M.
After few days privated memory was heavily fragmented and proxy was
running
out of memory.
Then I've compiled with 8M of ram.
It prolonged more but with the same result, which made me very nervous
and
PKG_MALLOC was out of the question.
Without PKG_MALLOC:
There were few runs for few days, the last one since last friday still
running.
No instabilities on proxy, no problems at all. Performance wise I have
not
notice any difference. It may be subjective, I'd say cpu may be higher
(%0.1
sometimes) but again it's subjective and I'm running ngrep logging via
syslog_ng and the proxy logging done via syslog_ng, configured
(syslog_ng)
to send the output to the syslog_ng server and pumping all huge output
via
syslog_ng may contribute to the CPU.
BTW, in main.c when opens syslog, there is the thing which may be
qualified
as bug. I you use standard syslog then there is no problem. With
syslog_ng,
there is the problem: it creates 2 log files and I've fixed main.c, by
the
code it writes in syslog, and then when daemonized opens syslog.
In turn, I'd like to ask the question about ngrep. I'm using ngrep-1-45.
When running on proxy I see duplicate message. When running not on proxy
-
no dups.
My hunch is that it's recording all stuff from on_reply_route and
loose_route?
Can anybody enlighten this subject.
Regards,
Toly
Henning Westerholt-2 wrote:
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
On Wednesday 04 February 2009, toly wrote:
the problem was:
file mem/mem.h
Hi Toly,
may i ask how were your experiences so far without the PKG_MALLOC memory
manager? Any performance problems, or perhaps instabilities that you
would
credit to this?
Cheers,
Henning
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
12:37 p.m.
New subject: [Kamailio-Users] Trying to compile openser 1.3.3 without PKG_MALLOC support
On Friday 13 February 2009, toly wrote:
We are running the test:
hammer->sbc(asterisk 1.4)->openser1.3.3->mediaserver(heavily modified
asterisk)
It is production environment.
Hi Toly,
thanks for the feedback.
call rate is steady 4 cps.
Proxy is 2 dual cores 2.5Ghz with 4G of ram
Initially openser was compiled with private memory size of 4M.
After few days privated memory was heavily fragmented and proxy was running
out of memory.
Then I've compiled with 8M of ram.
It prolonged more but with the same result, which made me very nervous and
PKG_MALLOC was out of the question.
Hm, this is strange. We using 1.3 PKG_MALLOC in a production environment with
heavy traffic, and don't any fragmentation instabilities. You're not the
first that reports this, thought.
Without PKG_MALLOC:
There were few runs for few days, the last one since last friday still
running.
No instabilities on proxy, no problems at all. Performance wise I have not
notice any difference. It may be subjective, I'd say cpu may be higher
(%0.1 sometimes) but again it's subjective and I'm running ngrep logging
via syslog_ng and the proxy logging done via syslog_ng, configured
(syslog_ng) to send the output to the syslog_ng server and pumping all huge
output via syslog_ng may contribute to the CPU.
Good to know that its aparently don't cause any problems.
BTW, in main.c when opens syslog, there is the thing
which may be qualified
as bug. I you use standard syslog then there is no problem. With syslog_ng,
there is the problem: it creates 2 log files and I've fixed main.c, by the
code it writes in syslog, and then when daemonized opens syslog.
It creates two log files? We've also use syslog-ng in some instances, never
noticed a problem. What exactly you need to change?
In turn, I'd like to ask the question about ngrep.
I'm using ngrep-1-45.
When running on proxy I see duplicate message. When running not on proxy -
no dups. My hunch is that it's recording all stuff from on_reply_route and
loose_route?
I don't think its related to the OpenSER, perhaps this is something in the
network configuration of this machine? This could e.g. happens when you use
bonded interfaces, and traces on the "any" interface.
Cheers,
Henning
8:02 p.m.
Hi Henning,
That was not exactly 2 files, did not formulate it correctly.
Prior to daemonizing it was writing into /var/log/messages, and after
daemonizing into it's own file.
Here's what I did:
Original code:
/* init_daemon? */
if (!dont_fork){
if ( daemonize((log_name==0)?argv[0]:log_name) <0 )
goto error;
}
Modified code:
/* init_daemon? */
if (!dont_fork){
char *p = rindex(argv[0], '/');
log_name = ( p == NULL ) ? argv[0] : ++p;
if ( daemonize((log_name==0)?argv[0]:log_name) <0 )
goto error;
}
Regards,
Toly.
Henning Westerholt-2 wrote:
On Friday 13 February 2009, toly wrote:
--
View this message in context:
http://www.nabble.com/Trying-to-compile-openser-1.3.3-without-PKG_MALLOC-su…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
We are running the test:
hammer->sbc(asterisk 1.4)->openser1.3.3->mediaserver(heavily modified
asterisk)
It is production environment.
Hi Toly,
thanks for the feedback.
call rate is steady 4 cps.
Proxy is 2 dual cores 2.5Ghz with 4G of ram
Initially openser was compiled with private memory size of 4M.
After few days privated memory was heavily fragmented and proxy was
running
out of memory.
Then I've compiled with 8M of ram.
It prolonged more but with the same result, which made me very nervous
and
PKG_MALLOC was out of the question.
Hm, this is strange. We using 1.3 PKG_MALLOC in a production environment
with
heavy traffic, and don't any fragmentation instabilities. You're not the
first that reports this, thought.
Without PKG_MALLOC:
There were few runs for few days, the last one since last friday still
running.
No instabilities on proxy, no problems at all. Performance wise I have
not
notice any difference. It may be subjective, I'd say cpu may be higher
(%0.1 sometimes) but again it's subjective and I'm running ngrep logging
via syslog_ng and the proxy logging done via syslog_ng, configured
(syslog_ng) to send the output to the syslog_ng server and pumping all
huge
output via syslog_ng may contribute to the CPU.
Good to know that its aparently don't cause any problems.
BTW, in main.c when opens syslog, there is the
thing which may be
qualified
as bug. I you use standard syslog then there is no problem. With
syslog_ng,
there is the problem: it creates 2 log files and I've fixed main.c, by
the
code it writes in syslog, and then when daemonized opens syslog.
It creates two log files? We've also use syslog-ng in some instances,
never
noticed a problem. What exactly you need to change?
In turn, I'd like to ask the question about
ngrep. I'm using ngrep-1-45.
When running on proxy I see duplicate message. When running not on proxy
-
no dups. My hunch is that it's recording all stuff from on_reply_route
and
loose_route?
I don't think its related to the OpenSER, perhaps this is something in the
network configuration of this machine? This could e.g. happens when you
use
bonded interfaces, and traces on the "any" interface.
Cheers,
Henning
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
5763
days inactive
5775
days old
12 comments
4 participants
participants (4)
-
Alex Balashov -
Daniel-Constantin Mierla -
Henning Westerholt -
toly