|
I retested with version 2.2.3-2 but as
before this version was killing most of the calls with dcc 41. So, I
couldn't get to the point to see if the freezing problem would happen with this
version.
All the timers that were available in the
[RoutedMode] section were increased for retest and it didn't change anything. I
am not sure if reading and setting this timers should have been written in the
logs since I didn't see anything. Please let me know if it is supposed to be
shown in the logs then I would know that I didn't set them
properly.
I increased the fdset number from 4096 to
32768 and again it didn't change anything. The version 2.2.1 froze even
with the higher number of fdset. The maximum no of calls on the GNUGK was about
50 and I am not sure if lack of socket with this number of
concurrent calls is something to think about !
The OS that I am using is RedHat 9. If
there is something else that I should do to increase the number of sockets
beside increasing the fdset and in OS level, please let me know and I'll go for
it.
Thanks,
Bahram.
----- Original Message -----
Sent: Wednesday, November 23, 2005 6:44
PM
Subject: Re: Could we
call this a CRASH?
Could you please test this again with the
current 2.2.3-2 version ?
2.2.1 is about a year old now and we fixed some
socket issues since
then.
If you are running out of sockets you
probably also have trouble
establishing new calls.
How to increase the
number of sockes depends on the OS you are using.
Bahram S. Biria
wrote:
> Freddy,
>
> Thanks for the reply. I have couple of
questions though.
>
> - Shouldn't something be written in the log
files to show the system
is
> running out of free socket for further
requests?
>
> - If the number of sockets is the cause, shouldn't
it affect just the
> new tries for connection not the whole
system?
>
> - Is increasing the number of sockets equal to
increasing the fd_set
> number for the GNUGK and the system? If is not,
could you please give
> me some heads up about the proper procedure for
increasing the number
> of sockets?
>
> Thanks,
>
Bahram.
>
> > This is a multi-part message in MIME
format.
> >
> >
> > This seems like a socket
issue. Try increasing the number of sockets
> > that your process is
allowed to use. I believe I posted this bug a
> long
> > time
ago, not sure if the latest versions of gnugk have fix this
>
issue.
> >
> >
> >
> >
Freddy
> >
> >
> >
> >
________________________________
> >
> > From: openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx
>
> [mailto:openh323gk-users-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf
Of
> > Bahram S. Biria
> > Sent: Wednesday, November 23,
2005 3:05 PM
> > To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
>
> Subject: Could we call this a CRASH?
> >
> >
> >
> > Hi,
> >
>
>
> >
> > Because of the other issue that I have
(dcc 41 on versions higher
than
> > 2.2.1) I used version 2.2.1
until it gets clear how the issue with
dcc
> > 41 could be
addressed on the newer versions.
> >
> >
>
>
> > The version 2.2.1 seems to work fine without a major
problem on
> > disconnecting or dropping calls. But after awhile of
working I will
> lose
> > the connection to it. The calls
wouldn't get terminated through it
and
> > trying to telnet to
status port would result the following
> >
> >
> >
> > [root@MTGK01 root]# telnet 127.0.0.1 7000
>
> Trying 127.0.0.1...
> > Connected to 127.0.0.1.
> >
Escape character is '^]'.
> >
> >
> >
> >
> >
> > The process is available and
the process usage shows almost the same
> > usage as when the calls
were getting terminated. I've never had an
> > online call when this
happened so I cannot say what would happen to
> the
> > online
calls in this situation.
> >
> >
> >
> > In the logs also there is nothing interesting. The log has
the
regular
> > result for the calls and nothing more.
>
>
> >
> >
> > Could we call this a
Crash on GNUGK? Is it a known issue and if so
is
> > there any
remedy to not get into it?
> >
> >
> >
> > Thanks,
> >
> > Bahram.
--
Jan
Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/
-------------------------------------------------------
This
SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for
problems? Stop! Download the new AJAX search engine that
makes
searching your log files as easy as surfing the web.
DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________________
Posting:
mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive:
http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Unsubscribe:
http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage:
http://www.gnugk.org/
|
