Re: The found out bugs in gnugk

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hmm, very strange. Does it happen only when the gatekeeper
is acually doing something or an idle gatekeeper also hangs up?
Does it happen always or sometimes only?

----- Original Message ----- 
From: "kompnet" <kompnet@xxxxxxxxx>
Sent: Friday, March 11, 2005 9:48 AM


On 10 Март 2005 19:54, Zygmuntowicz Michal wrote:
> Is there at least note about receiving a HUP signal
> in the log? Did you try reloading by hand, using kill -HUP PID?

After reloading with #kill -HUP `cat /var/run/gnugk.pid`
there is
2005/03/11 11:01:38.454 5                job.cxx(169)   JOB     Worker 6151
started
2005/03/11 11:01:38.454 5                job.cxx(186)   JOB     Starting Job
HouseKeeping at Worker thread 6151
2005/03/11 11:03:46.083 1                 gk.cxx(269)   GK      Gatekeeper
Hangup (signal 1)
2005/03/11 11:03:46.084 1                 gk.cxx(879)   GK      Logging 
closed
(reopen log file)
2005/03/11 11:03:46.084 1                 gk.cxx(908)   GK      Logging
restarted
2005/03/11 11:03:46.086 5            Toolkit.cxx(771)   GK      Trying file
name /tmp/gnugk.ini-319 for temp config
in logfile.
Simlink /tmp/gnugk.ini-319 on /etc/gnugk/gnugk.ini exists and works 
correctly.


> Maybe /var/run/gnugk.pid contains and incorrect PID

gnugk.pid contains CORRECT PID.
After sending kill -HUP PID I can see the same processes with
#ps ax
as before, but gnugk cann't serve any calls and cann't response any commands
through statusport (connection to status port can be established).
But if I've been connected to status port BEFORE sending HUP signal, I can 
see
this:
3387 pts/13   S<     0:00 /opt/openh323/gnugk-2.2.2 -c
/etc/gnugk/gnugk-2.2beta5.ini -o /var/log/gnugk/gnugk.log -tttttt
 3389 pts/13   Z<     0:00 [gnugk-2.2.2 <defunct>]
Allways the second gnugk process became zombie.
Have you checked up whether gnugk is alive after config reload?

> or the HUP signal is mapped to something else, I don't
> have any idea. Or maybe the build is broken.

What does it mean "build is broken"?
There wasn't any errors during compilation, and I've built GNUGK on wo
different hosts with the same result.
Is it possible to do anything else for error localisation?
Maybe debug building? Or some system commands?

Igor Prokhorov



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click

_______________________________________________________

List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id…49
Homepage: http://www.gnugk.org/

[Index of Archives]     [SIP]     [Open H.323]     [Gnu Gatekeeper]     [Asterisk PBX]     [ISDN Cause Codes]     [Yosemite News]

  Powered by Linux