Hi Pascal, a number of bugs have been fixed since the release of 2.2.6. If you are a heavy user of the status port, I would suggest you download the latest version of the v2_2_7_STABLE branch from the CVS. There is one important fix made in July thats not in the 2.2.7 download archives, yet. Regards, Jan Pascal GRELICHE wrote: > Hi, > > I experienced a segfault few days ago in gnugk. I use Ubuntu 8.04.1 and > gnugk included (2:2.2.6-7build1). > > I didn't have core dumps activated but here are the logs I have: > > In syslog > Sep 4 19:30:03 gatekeeper-dinan1 kernel: [88441.385399] gnugk[5272]: > segfault at d6104574 eip b75eb6fe esp b66790b0 error 7 > > In gnugk.log (few lines before the crash and all the reboot done after) > 2008/09/04 19:29:03.457 2 RasSrv.cxx(413) > DCF|172.26.5.2|2261_endp|14952|normalDrop; > 2008/09/04 19:29:03.457 2 RasSrv.cxx(252) RAS Send DCF to > 172.26.5.2:3719 > 2008/09/04 19:29:19.857 2 RasSrv.cxx(189) RAS Read from > 172.26.4.2:3719 > 2008/09/04 19:29:19.858 2 RasSrv.cxx(240) RAS Received RRQ > 2008/09/04 19:29:19.858 1 RasSrv.cxx(368) RAS RRQ Received > 2008/09/04 19:29:19.858 2 RasSrv.cxx(252) RAS Send RCF to > 172.26.4.2:3719 > 2008/09/04 19:29:40.610 2 RasSrv.cxx(189) RAS Read from > 172.26.5.2:3719 > 2008/09/04 19:29:40.610 2 RasSrv.cxx(240) RAS Received RRQ > 2008/09/04 19:29:40.610 1 RasSrv.cxx(368) RAS RRQ Received > 2008/09/04 19:29:40.610 2 RasSrv.cxx(252) RAS Send RCF to > 172.26.5.2:3719 > 2008/09/04 19:29:41.089 2 RasSrv.cxx(189) RAS Read from > 172.26.6.2:3719 > 2008/09/04 19:29:41.089 2 RasSrv.cxx(240) RAS Received RRQ > 2008/09/04 19:29:41.089 1 RasSrv.cxx(368) RAS RRQ Received > 2008/09/04 19:29:41.089 2 RasSrv.cxx(252) RAS Send RCF to > 172.26.6.2:3719 > 2008/09/04 19:30:02.291 1 GkStatus.cxx(503) STATUS New client > authenticated succesfully: 216 193.252.20.34:53690=>193.252.20.34:7000 , > login: > 2008/09/04 19:30:02.625 1 GkStatus.cxx(503) STATUS New client > authenticated succesfully: 217 193.252.20.34:53691=>193.252.20.34:7000 , > login: > > > 2008/09/05 10:28:36.187 2 singleton.cxx(29) Create instance: > Toolkit(1) > 2008/09/05 10:28:36.228 2 Toolkit.cxx(313) Internal Network Detected > 172.26.0.0/16 > 2008/09/05 10:28:36.228 2 Toolkit.cxx(261) > Network=193.252.20.0/255.255.255.0, IP=193.252.20.34 > 2008/09/05 10:28:36.228 2 Toolkit.cxx(261) > Network=193.253.66.0/255.255.255.0, IP=193.253.66.117 > 2008/09/05 10:28:36.228 2 Toolkit.cxx(261) > Network=172.26.0.0/255.255.0.0, IP=193.252.20.34 > 2008/09/05 10:28:36.228 2 Toolkit.cxx(261) > Network=135.9.0.0/255.255.0.0, IP=135.9.48.60 > 2008/09/05 10:28:36.228 2 Toolkit.cxx(262) Default IP=135.9.48.60 > 2008/09/05 10:28:36.228 2 transports.cxx(886) H323 Use of non IP > transport address: "" > 2008/09/05 10:28:36.228 2 Toolkit.cxx(399) GK H.323 Proxy enabled > 2008/09/05 10:28:36.228 2 Toolkit.cxx(409) GK Internal Network 0 = > 172.26.0.0/16 > 2008/09/05 10:28:36.228 2 Toolkit.cxx(639) GK Loaded per GW rewrite > data: > 2008/09/05 10:28:36.228 2 Toolkit.cxx(642) GK No per GW data loaded > 2008/09/05 10:28:36.229 2 singleton.cxx(29) Create instance: > CapacityControl(2) > 2008/09/05 10:28:36.229 1 gk.cxx(503) OpenH323 Gatekeeper - The > GNU Gatekeeper with ID 'OpenH323GK' started > Gatekeeper(GNU) Version(2.2.6) > Ext(pthreads=1,radius=1,mysql=1,pgsql=1,firebird=1,large_fdset=0,crypto/ssl=1) > Build(Mar 26 2008, 18:30:59) Sys(Linux i686 2.6.24-19-server)^M > > 2008/09/05 10:28:36.229 2 singleton.cxx(29) Create instance: > CallTable(3) > 2008/09/05 10:28:36.229 2 gk.cxx(547) GK TimeToLive for > Registrations: -1 > 2008/09/05 10:28:36.229 2 singleton.cxx(29) Create instance: RasSrv(4) > 2008/09/05 10:28:36.229 2 ProxyChannel.cxx(181) RTPPortRange: 1024-65535 > 2008/09/05 10:28:36.230 2 singleton.cxx(29) Create instance: Agent(5) > 2008/09/05 10:28:36.230 2 RasSrv.cxx(746) GK Using Routed > Signalling > 2008/09/05 10:28:36.230 2 RasSrv.cxx(747) GK H.245 Routed Enabled > 2008/09/05 10:28:36.230 2 singleton.cxx(29) Create instance: > GkStatus(6) > 2008/09/05 10:28:36.230 2 singleton.cxx(29) Create instance: > RegistrationTable(7) > 2008/09/05 10:28:36.231 1 RasTbl.cxx(80) New > EP|127.0.0.1:1720|ASTERISK:h323_ID|gateway|8916_endp^M > > 2008/09/05 10:28:36.231 2 RasTbl.cxx(1321) Add permanent endpoint > 127.0.0.1:1720 > 2008/09/05 10:28:36.232 2 RasSrv.cxx(783) GK Home = 193.252.20.34 > 2008/09/05 10:28:36.232 1 RasSrv.cxx(529) Listening to > 193.252.20.34:1719(U) > 2008/09/05 10:28:36.233 1 RasSrv.cxx(529) Listening to > 193.252.20.34:1718(Mcast) > 2008/09/05 10:28:36.233 1 RasSrv.cxx(529) Listening to > 193.252.20.34:1721 > 2008/09/05 10:28:36.233 1 RasSrv.cxx(529) Listening to > 193.252.20.34:7000 > 2008/09/05 10:28:36.233 1 RasSrv.cxx(846) RAS Broadcast listener > listening at 0.0.0.0:1719(Bcast) > 2008/09/05 10:28:36.233 1 gkauth.cxx(282) GKAUTH default rule added > to check RAS: ARQ BRQ DRQ GRQ IRQ LRQ RRQ URQ, OTHER: SETUP SETUPUNREG > 2008/09/05 10:28:36.233 2 Routing.cxx(636) VQueue (CTI) Virtual > queues enabled (aliases:CC), request timeout: 10 s > 2008/09/05 10:28:36.233 2 singleton.cxx(29) Create instance: > Routing::Analyzer(8) > 2008/09/05 10:28:36.234 1 Routing.cxx(270) RoutingPolicy::OnARQ add > policy explicit,internal,parent,neighbor for prefix * > 2008/09/05 10:28:36.234 1 Routing.cxx(270) RoutingPolicy::OnLRQ add > policy explicit,internal,parent,neighbor for prefix * > 2008/09/05 10:28:36.234 1 Routing.cxx(270) RoutingPolicy::OnSetup add > policy explicit,internal,parent,neighbor for prefix * > 2008/09/05 10:28:36.234 1 Routing.cxx(270) RoutingPolicy::OnFacility > add policy explicit,internal,parent,neighbor for prefix * > 2008/09/05 10:28:36.234 2 gkacct.cxx(1014) GKACCT Successfully > logged event 8 > 2008/09/05 10:29:59.531 2 RasSrv.cxx(189) RAS Read from > 172.26.2.2:3719 > 2008/09/05 10:29:59.531 2 RasSrv.cxx(240) RAS Received GRQ > 2008/09/05 10:29:59.531 1 RasSrv.cxx(368) RAS GRQ Received > 2008/09/05 10:29:59.532 2 RasSrv.cxx(413) > GCF|172.26.2.2|0812345003:dialedDigits=00:60:4C:10:43:87:h323_ID|terminal; > 2008/09/05 10:29:59.532 2 RasSrv.cxx(252) RAS Send GCF to > 172.26.2.2:3719 > 2008/09/05 10:29:59.557 2 RasSrv.cxx(189) RAS Read from > 172.26.2.2:3719 > 2008/09/05 10:29:59.557 2 RasSrv.cxx(240) RAS Received RRQ > 2008/09/05 10:29:59.557 1 RasSrv.cxx(368) RAS RRQ Received > 2008/09/05 10:29:59.557 1 RasTbl.cxx(80) New > EP|172.26.2.2:4720|0812345003:dialedDigits=00:60:4C:10:43:87:h323_ID|terminal|8917_endp^M > > 2008/09/05 10:29:59.558 2 RasSrv.cxx(413) > RCF|172.26.2.2:4720|0812345003:dialedDigits=00:60:4C:10:43:87:h323_ID|terminal|8917_endp; > 2008/09/05 10:29:59.558 2 RasSrv.cxx(252) RAS Send RCF to > 172.26.2.2:3719 > 2008/09/05 10:30:01.326 1 GkStatus.cxx(503) STATUS New client > authenticated succesfully: 1 193.252.20.34:59771=>193.252.20.34:7000 , > login: > 2008/09/05 10:30:01.632 1 GkStatus.cxx(503) STATUS New client > authenticated succesfully: 2 193.252.20.34:59772=>193.252.20.34:7000 , > login: > 2008/09/05 10:30:01.632 1 GkStatus.cxx(503) STATUS New client > authenticated succesfully: 2 193.252.20.34:59772=>193.252.20.34:7000 , > login: > 2008/09/05 10:30:56.582 2 RasSrv.cxx(189) RAS Read from > 172.26.2.2:3719 > 2008/09/05 10:30:56.582 2 RasSrv.cxx(240) RAS Received RRQ > 2008/09/05 10:30:56.582 1 RasSrv.cxx(368) RAS RRQ Received > > I don't have the exact gatekeeper.ini used when the crash happened, but I > include the one we are using now. I know that there are verry little > changes (log rotation for example) > > > > Do you have any explanation of this segfault and if it is/will be solved. > I activated the core unlimited and will transfer you the dump if I see the > same happen again. > > > > Here is one other bug I found: > I had a gnugk running on a Linux making some routing. > eth1 has the address 172.28.35.1 and the gateway to 172.26.0.0/16 is > 172.28.35.5 > I created 2 loopback ip aliases (lo:0 -> 193.252.20.34/32 lo0:1 > ->193.251.213.149) > When clients are registering, they are using these loopback addresses. > The registrations went fine. > But on call, there was some trouble. > I include a tcpdump file with the apropriate problems > > > > Packet number(s) Comment > 1-4 172.26.2.2 registers to 193.252.20.34 > 10-13 172.26.1.2 registers to 193.251.213.249 > 38-44 172.26.1.2 wants to make a call to 172.26.2.2 > 45-46 The gnugk tries to call 172.26.2.2 with the > address ot eth0, not lo:1 which is the address the client registered. > So the call failed... > I thought, gnugk would use the address the client registered to discuss > with it, not any "random" IP the Linux has. > Please tell me if I'm wrong and if it is a bug, if it would be fixed. > > For the moment, I uses only one IP address (Home=193.252.20.34) which is > assigned to eth1 directly, the gateway is 193.252.20.1 and all clients are > registering with this single address. > > Thanks > > PS: sorry for my poor english. > -- > Pascal Greliche -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
