15 Dec
2006
15 Dec
'06
8:38 a.m.
Jiri Kuthan wrote:
At 16:03 14/12/2006, samuel wrote:
It might be due to a DNS query....whenver a
request has to be
forwarded to a domain, openSER makes a DNS query to resolv the IP.
During this operation, the child processing the request will not
answer to further incoming messages.
Hard to say without more input what the cause may be. Indeed common
suspects are DNS (or any other blocking operation, such as dataabse)
or timers, but again it is hard to say without more input. If it is DNS or TCP-based blocking, it may be
worthwhile trying genuine
SER/ottendorf which is having IP blacklisting and DNS cachine in there --
this is indeed something which has been pressing us for a while.
How about the TTL in ser's cache? Does it obey the TTL in the DNS
responses? If yes, then there is no beneift over using a "near"
resolving bind.
regards
klaus
If it is timer system, then SER should address it it (it must be
the latest ottendorf version though).
If it is database that blocks itself and SER consequently too, you
have to look at the database. (Even if SER would do something about
it, it could do hardly better then sending a negative reply
"DB unavailable").
-jiri
--
Klaus Darilion
nic.at
it also can be happening due to a spiral loop
that stays on the server.
Without further information (confg,logs) it's hard to tell which is
the reason...
hope it helps,
Samuel.
without more information
2006/12/14, Max Gregorian <gregorian442(a)googlemail.com>om>:
--
Jiri Kuthan http://iptel.org/~jiri/
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users Hi all,
Just wondering if anyone else has had this problem. I have noticed while
tracing on my OpenSER server, that every now and then the server receives a
packet which it does to respond to immediately, resulting in a string of
packets being sent to the server and then the server responding a few
seconds later. This does not happen all the time, just say maybe once or
twice every hour. The rest of the time the signaling is correct and
responses follow request packets in the correct order.
What I am trying to figure out is whether this is a load traffic issue (i.e.
can the server not handle too much load), and if so is it OpenSER or the
network or the server in general? I have run diagnostics on the servers and
there is nothing wrong with the hardware.
On the other hand Could this be related to any timer issues? I remember
there was mention of timers in SER but are there any default timer settings
that can be tweaked?
Thanks in advance for any response.
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users