Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106887
interpreted = N
texte = --Apple-Mail-2--828833925 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Very strange that this problem is happening to another Windows Server = user. I reported the same problem last week on a system that has been = running for 5+ years and have NEVER seen the problem in 12+ years of = WebDNA experience. The problem tends to create a loop and brings the server to a grinding = halt by constantly using 100% of CPU. After reading the many rants in this thread I do suspect that it MAY be = a Windows problem brought about from a Windows update. "Failed to aquire lock on database - Possible deadlock averted" The error that is being published in the errorlog.txt does not come from = the errormessages.db so must be coming from the WebDNA engine itself. Chris, maybe you could look into this please. Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 07/07/2011, at 5:10 AM, Tommy Bell wrote: > Hello everyone, a few days ago a post was made about=20 > "Failed to aquire lock on database" >=20 > I have been experiencing this for quite some time, and recently it has = gotten much worse, I was hoping someone could enlighten me to where to = go bug hunting, or just offer some tips with regards to what I could be = doing wrong. >=20 > This is the error i get (One amongst many db's, not just online.db) > An unknown error occurred: > DBError > ../../database/online.db > Failed to aquire lock on database - Possible deadlock averted >=20 > /Tommy >=20 >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --Apple-Mail-2--828833925 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Very = strange that this problem is happening to another Windows Server user. I = reported the same problem last week on a system that has been running = for 5+ years and have NEVER seen the problem in 12+ years of WebDNA = experience.
The problem tends to create a loop and = brings the server to a grinding halt by constantly using 100% of = CPU.
After reading the many rants in this thread = I do suspect that it MAY be a Windows problem brought about from a = Windows update.
"Failed to aquire lock on = database - Possible deadlock averted"
The error = that is being published in the errorlog.txt does not come from the = errormessages.db so must be coming from the WebDNA engine = itself.
Chris, maybe you could look into this = please.
On 07/07/2011, at 5:10 AM, Tommy Bell wrote:
Hello = everyone, a few days ago a post was made about
"Failed to aquire lock on database"
I have been experiencing this for quite some time, and recently it has gotten much worse, I was hoping someone could enlighten me to where to go bug hunting, or just offer some tips with regards to what I could be doing wrong.
This is the error i get (One amongst many db's, not just online.db)
An unknown error occurred:
DBError
../../database/online.db
Failed to aquire lock on database - Possible deadlock averted
/Tommy
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/l= ist/talk@webdna.us Bug Reporting: support@webdna.us
= --Apple-Mail-2--828833925--
Associated Messages, from the most recent to the oldest:The problem tends to create a loop and = brings the server to a grinding halt by constantly using 100% of = CPU.
After reading the many rants in this thread = I do suspect that it MAY be a Windows problem brought about from a = Windows update.
"Failed to aquire lock on = database - Possible deadlock averted"
The error = that is being published in the errorlog.txt does not come from the = errormessages.db so must be coming from the WebDNA engine = itself.
Chris, maybe you could look into this = please.
On 07/07/2011, at 5:10 AM, Tommy Bell wrote:
Hello = everyone, a few days ago a post was made about
"Failed to aquire lock on database"
I have been experiencing this for quite some time, and recently it has gotten much worse, I was hoping someone could enlighten me to where to go bug hunting, or just offer some tips with regards to what I could be doing wrong.
This is the error i get (One amongst many db's, not just online.db)
An unknown error occurred:
DBError
../../database/online.db
Failed to aquire lock on database - Possible deadlock averted
/Tommy
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/l= ist/talk@webdna.us Bug Reporting: support@webdna.us
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...