I faced some problem with reload command and/or reloading configuration via "kill -HUP". When I send this command to gnugk, it is "stopped" for some time (~ 10 min) and then continues normal operations. I think it is because size of my config file ~90K (and number of rules in section RasSrv::RewriteE164 - more than 4000).
Here is the log (trace level 4):
2004/03/04 10:57:02.642 2 GkStatus.cxx(343) GK GkStatus got com
mand reload
2004/03/04 10:57:35.764 3 RasSrv.cxx(2111) GK Send to x.x.x.x:54259
disengageRequest {
requestSeqNum = 12211
endpointIdentifier = 9 characters {
0034 0036 0033 0038 005f 0065 006e 0064 4638_end
0070 p
}
conferenceID = 16 octets {
02 3b 4f f9 6c e8 11 d8 8a 71 b7 55 8f fd e0 0b .;O.l....q.U....
}
callReferenceValue = 28832
disengageReason = forcedDrop <<null>>
callIdentifier = {
guid = 16 octets {
02 3b 4f f9 6c e8 11 d8 8a 73 b7 55 8f fd e0 0b .;O.l....s.U....
}
}
gatekeeperIdentifier = 7 characters {
0072 0061 006d 0073 002d 0067 006b rams-gk
}
answeredCall = FALSE
}
2004/03/04 10:57:35.764 2 RasTbl.cxx(1170) Gk Disconnect Call
No. 2759598
2004/03/04 10:57:36.724 1 RasTbl.cxx(1573) CDR|2759598|02 3b 4f f9
6c e8 11 d8 8a 73 b7 55 8f fd e0 0b|0|unconnected|Thu, 04 Mar 2004 10:57:35 +030
0| | |x.x.x.x:1720|4638_endp|8032#70112580545:dialedDigits|70957483333:dial
edDigits=gw_mks_msk1:h323_ID|rams-gk;
2004/03/04 11:06:08.297 2 GkStatus.cxx(529) GK GkStatus client
26715 (y.y.y.y) has disconnected
2004/03/04 11:06:08.616 2 GkStatus.cxx(529) GK GkStatus client
26913 (z.z.z.z) has disconnected
2004/03/04 11:07:04.458 4 Toolkit.cxx(120) InterfaceTable:
a.a.a.a (em0)
127.0.0.1 (lo0)
2004/03/04 11:07:04.459 2 Toolkit.cxx(90) Network=b.b.b.b/255
.255.255.255, IP=80.93.96.230
2004/03/04 11:07:04.459 2 Toolkit.cxx(90) Network=c.c.c.c/255
.255.255.248, IP=80.93.96.230
2004/03/04 11:07:04.459 2 Toolkit.cxx(90) Network=127.0.0.1/255.25
5.255.255, IP=127.0.0.1
2004/03/04 11:07:04.459 2 Toolkit.cxx(90) Network=0.0.0.0/255.255.
255.255, IP=127.0.0.1
2004/03/04 11:07:04.459 2 Toolkit.cxx(90) Network=0.0.0.0/255.255.
255.255, IP=80.93.96.230
2004/03/04 11:07:04.459 2 Toolkit.cxx(90) Network=0.0.0.0/255.255.
255.255, IP=127.0.0.1
2004/03/04 11:07:04.459 2 Toolkit.cxx(90) Network=0.0.0.0/255.255.
255.255, IP=127.0.0.1
2004/03/04 11:07:04.460 2 Toolkit.cxx(90) Network=0.0.0.0/255.255.
255.255, IP=80.93.96.230
2004/03/04 11:07:04.460 2 Toolkit.cxx(90) Network=0.0.0.0/255.255.
255.255, IP=127.0.0.1
2004/03/04 11:07:04.460 2 Toolkit.cxx(91) Default IP=a.a.a.a
2004/03/04 11:07:04.460 2 Toolkit.cxx(158) GK H.323 Proxy enab
led
2004/03/04 11:07:06.134 1 gkacct.cxx(133) GKACCT Destroyed module
FileAcct
2004/03/04 11:07:06.134 1 gkacct.cxx(128) GKACCT Created module F
ileAcct with event mask FFFFFFFF
2004/03/04 11:07:06.134 3 gk.cxx(175) GK Config reloaded.
So you can see that:
1) gatekeeper get command reload
2) after 33 sec it somehow process disengageRequest (!!!)
3) after ~10 min it eventually ends reload command (saying "Config reloaded.")
During reloading computer doesn't answer PING requests.
GnuGk 2.0.6 on FreeBSD 4.8 in full proxy mode. Version 2.0.7 - the same behaviour.
Does anybody have similar problem? Is there some limit on config file or number of rewrite rules?
Regards.
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
