[Top][All Lists]

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

RE: PR Submission (Change of state) gets locked

From: Michael Loftis
Subject: RE: PR Submission (Change of state) gets locked
Date: Tue, 28 Jan 2003 02:24:31 -0800

/proc/kcore is the *kernel* core. /proc/* contains information about the current system state. Depending on your OS you'll need to look for a file named 'core' or 'executable.core' (ie 'gnatsd.core') or maybe some other variant.

--On Tuesday, January 28, 2003 3:44 PM +0530 Chandra Ramesh <address@hidden> wrote:


        Thanks for the pointer. I think as you have pointed, the gnatsd
daemon          might be crashing. There is a "kcore" file created in
/proc directory.          Is there a way that I can debug this "kcore"
file to know why gnatsd          is crashing?

        I checked up the files under gnats-adm directory and found it to
be          of right syntax.

        Does "gnatsd" daemon crash only because that the database config
files          are not in the right syntax OR are there any other reason
that it can crash?

        Please let me know.

Thanks and Regards,
Ramesh Chandra

-----Original Message-----
From: Yngve Svendsen [mailto:address@hidden
Sent: Monday, January 27, 2003 3:20 PM
To: Chandra Ramesh; address@hidden
Subject: RE: PR Submission (Change of state) gets locked

At 14:26 27.01.2003 +0530, Chandra Ramesh wrote:


        The lock file is not a stale file. It is getting created every
        time  the moment I click on the submit button after entering the
        reqd  changes.

        Probably, the lock file should be created to prevent a
simultaneous modification
        by an other user. The problem is that the lock file should get
deleted on it's own
        and but it is not.

This probably means that gnatsd crashes while processing your changes.
Have  you made any changes to the database config files (categories etc.)
lately?  gnatsd 3.x does not handle syntax errors there gracefully and
may leave  stale lock files behind when it dies. You should probably have
a look at  your config.

Yngve Svendsen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]