9 Sep
2005
9 Sep
'05
8:09 p.m.
Hello everybody,
the cvs head is frozen in preparation for the new release. Please commit
only fixes to the C code. Documentation updates are very welcome as well
as adjacent tools upgrades.
In about two weeks (more or less), a new branch will be created the the
cvs head will be unfrozen and open for new features.
Cheers,
Daniel
12 Sep
12 Sep
10:45 a.m.
Hi Daniel!
I still have 2 problems which are hard to track down.
1. Sometime the UDP threads get screwed up. Fifo and TCP threads are
still working (also TCP in and UDP out) but UDP packets sent to openser
are not processed.
2. Sometimes the tm module rans out of memory. The tm module keeps old
transactions in memory but apparently it does not delete them when they
get expired.
But bugs haven't appeared yet in normal usage, but when testing against
the protos test suite.
Thus, it would be very cool, if one of the core developers can test
openser against protos to find the bugs.
regards
klaus
Daniel-Constantin Mierla wrote:
Hello everybody,
the cvs head is frozen in preparation for the new release. Please commit
only fixes to the C code. Documentation updates are very welcome as well
as adjacent tools upgrades.
In about two weeks (more or less), a new branch will be created the the
cvs head will be unfrozen and open for new features.
Cheers,
Daniel
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
11:30 a.m.
New subject: [Devel] Re: [Users] cvs is frozen
Klaus Darilion wrote:
1. Sometime the UDP threads get screwed up. Fifo and
TCP threads are
still working (also TCP in and UDP out) but UDP packets sent to openser
are not processed.
Could this be related to the problem I reported here?
http://mail.iptel.org/pipermail/serusers/2005-September/023638.html
What exactly does happen in your case? Does the load also go up? What's
the SIP message which screws up SER?
2. Sometimes the tm module rans out of memory. The tm
module keeps old
transactions in memory but apparently it does not delete them when they
get expired.
Hmm... I've 2GB of RAM for the SER hosts, but I've to restart SER every
other week or so because it eats up quite a lot of memory.
But bugs haven't appeared yet in normal usage, but
when testing against
the protos test suite.
We've some Cisco ATA 186 running with a 3.1.1 firmware, and they quite
often send broken SIP messages ("%d" instead of ports and so on). Maybe
these sometimes cause the errors, but I'm not sure.
Andy
12:30 p.m.
New subject: [Devel] Re: [Users] cvs is frozen
Hello,
On 09/12/05 12:30, Andreas Granig wrote:
Klaus Darilion wrote:
could you send the memory log when it runs out of memory? ( /kill
-SIGUSR1/ ) It would help to see if it is same issue as reported by Klaus.
Cheers,
Daniel
1. Sometime the UDP threads get screwed up. Fifo
and TCP threads are
still working (also TCP in and UDP out) but UDP packets sent to
openser are not processed.
Could this be related to the problem I reported here?
http://mail.iptel.org/pipermail/serusers/2005-September/023638.html
What exactly does happen in your case? Does the load also go up?
What's the SIP message which screws up SER?
2. Sometimes the tm module rans out of memory.
The tm module keeps
old transactions in memory but apparently it does not delete them
when they get expired.
Hmm... I've 2GB of RAM for the SER hosts, but I've to restart SER
every other week or so because it eats up quite a lot of memory. But bugs haven't appeared yet in normal
usage, but when testing
against the protos test suite.
We've some Cisco ATA 186 running with a 3.1.1 firmware, and they quite
often send broken SIP messages ("%d" instead of ports and so on).
Maybe these sometimes cause the errors, but I'm not sure.
Andy
2:02 p.m.
New subject: [Devel] Re: [Users] cvs is frozen
Andreas Granig wrote:
Klaus Darilion wrote:
I couldn't find the SIP message yet. It happens when testing against
protos. Sometimes after 50 requests, sometimes after 4000 requests.
regards
klaus
1. Sometime the UDP threads get screwed up. Fifo
and TCP threads are
still working (also TCP in and UDP out) but UDP packets sent to
openser are not processed.
Could this be related to the problem I reported here?
http://mail.iptel.org/pipermail/serusers/2005-September/023638.html
What exactly does happen in your case? Does the load also go up? What's
the SIP message which screws up SER? 2. Sometimes
the tm module rans out of memory. The tm module keeps old
transactions in memory but apparently it does not delete them when
they get expired.
Hmm... I've 2GB of RAM for the SER hosts, but I've to restart SER every
other week or so because it eats up quite a lot of memory.
But bugs haven't appeared yet in normal
usage, but when testing
against the protos test suite.
We've some Cisco ATA 186 running with a 3.1.1 firmware, and they quite
often send broken SIP messages ("%d" instead of ports and so on). Maybe
these sometimes cause the errors, but I'm not sure.
Andy
15 Sep
15 Sep
8:41 p.m.
New subject: [Devel] Re: [Users] cvs is frozen
Hello,
On 09/12/05 12:30, Andreas Granig wrote:
Klaus Darilion wrote:
this issue should be solved in the latest cvs (committed just a few time
ago). Please try it and let us know if it works.
The deadlock occurred when handling CANCELs within a failure_route. The
failure_route is executed under a lock which protects the replies for
that transaction. As RFC states, a stateful proxy processes the CANCEL
hop by hop and sends back 200OK immediately => this needed to acquire
same lock -- all this processing happens in t_relay*() functions.
Now, no reply is sent for a CANCEL from failure_route (it is already
sent when the CANCEL arrived) or if a reply was already sent (due to
misconfiguration or whatever reason).
Thanks again to Klaus for testing and providing access to affected system.
Cheers,
Daniel
1. Sometime the UDP threads get screwed up. Fifo
and TCP threads are
still working (also TCP in and UDP out) but UDP packets sent to
openser are not processed.
Could this be related to the problem I reported here?
http://mail.iptel.org/pipermail/serusers/2005-September/023638.html
What exactly does happen in your case? Does the load also go up?
What's the SIP message which screws up SER?
12 Sep
12 Sep
12:14 p.m.
Hello Klaus,
On 09/12/05 11:45, Klaus Darilion wrote:
Hi Daniel!
I still have 2 problems which are hard to track down.
1. Sometime the UDP threads get screwed up. Fifo and TCP threads are
still working (also TCP in and UDP out) but UDP packets sent to
openser are not processed.
2. Sometimes the tm module rans out of memory. The tm module keeps old
transactions in memory but apparently it does not delete them when
they get expired.
But bugs haven't appeared yet in normal usage, but when testing
against the protos test suite.
Thus, it would be very cool, if one of the core developers can test
openser against protos to find the bugs.
yes, we know about them. We will try to track them down, these weeks we
will focus on testing.
Cheers,
Daniel
regards
klaus
Daniel-Constantin Mierla wrote:
Hello everybody,
the cvs head is frozen in preparation for the new release. Please
commit only fixes to the C code. Documentation updates are very
welcome as well as adjacent tools upgrades.
In about two weeks (more or less), a new branch will be created the
the cvs head will be unfrozen and open for new features.
Cheers,
Daniel
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
7015
days inactive
7021
days old
6 comments
3 participants
participants (3)
-
Andreas Granig -
Daniel-Constantin Mierla -
Klaus Darilion