Re: [WebDNA] An unknown error occured // Deadlock avoided

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106890
interpreted = N
texte = --Apple-Mail-6--825431670 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii It does seem to be coming regularly from one template that shares a heap = of code with other templates. I do get it on a few other templates but not on a regular basis. There is NO [exclusivelock] context anywhere in the site. At first I thought that the problem was a DOS attack as it has the same = effect. Rebooting the server always fixes the problem, this is because = the infinite loop that is causing the problem is broken. I have just had another look at my errorlog.txt and see that it has = happened 38 times in one second in one instance when I really load up = the server with a big search. It may be a not enough RAM, but the machine is fairly well speced. DB's = range from 20-70MB. I can not pin it down to certain instances, as it does not always happen = as you would expect if there was bad code. It may be a general error message that is not worded correctly that = should read something along the lines of "An error has occurred to = which there is no known cause" . This is the line from my errorlog.txt: 04/07/201114:25:15ShowPage089.000.100.031An = unknown error occurred:
DBError
^data/pendingorders.db
Failed = to aquire lock on database - Possible deadlock averted

= /pending_scan03.htmlpending/pending_order.inc Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 11/07/2011, at 9:01 AM, Ronald Kirkland wrote: > Well sadly it would appear you are not alone. I did a quick Google > search for the error message and it appears that FirstNorth.com, > starnewsgroup.com, www.laserdisken.dk, and a few others are having the > same issue. This does appear to be a WebDNA generated error (not > saying it is caused by WebDNA). >=20 > Stuart, how often does this happen? Can you trigger the behavior when > you do something specific or it is completely random? >=20 >=20 >=20 > On Sun, Jul 10, 2011 at 3:52 PM, Stuart Tremain = wrote: >>=20 >> 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. >>=20 >> 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. >>=20 >> Regards >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >> On 07/07/2011, at 5:10 AM, Tommy Bell wrote: >>=20 >> Hello everyone, a few days ago a post was made about >> "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 >>=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 > --------------------------------------------------------- > 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-6--825431670 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii It = does seem to be coming regularly from one template that shares a heap of = code with other templates.

I do get it on a few other = templates but not on a regular basis.

There is NO = [exclusivelock] context anywhere in the site.

At = first I thought that the problem was a DOS attack as it has the same = effect. Rebooting the server always fixes the problem, this is because = the infinite loop that is causing the problem is = broken.

I have just had another look at my = errorlog.txt and see that it has happened 38 times in one second in one = instance when I really load up the server with a big = search.

It may be a not enough RAM, but the = machine is fairly well speced. DB's range from = 20-70MB.

I can not pin it down to certain = instances, as it does not always happen as you would expect if there was = bad code.

It may be a general error message = that is not worded correctly that should read something along the lines = of  "An error has occurred to which there is no known cause" = .

This is the line from my = errorlog.txt:

04/07/2011= 14:25:15= ShowPage= 089.000.100.031An unknown error occurred:<br>DBError<br>^data/pendingorders.db<br>Failed to aquire lock on database - Possible = deadlock averted<br><br>/pending_scan03.html= pending/pending_order.inc


=


Regards

Stuart = Tremain
IDFK Web Developments
AUSTRALIA




On 11/07/2011, at 9:01 AM, Ronald Kirkland wrote:

Well = sadly it would appear you are not alone. I did a quick Google
search = for the error message and it appears that FirstNorth.com,
starnewsgroup.com, www.laserdisken.dk, and a few = others are having the
same issue. This does appear to be a WebDNA = generated error (not
saying it is caused by WebDNA).

Stuart, = how often does this happen? Can you trigger the behavior when
you do = something specific or it is completely random?



On Sun, = Jul 10, 2011 at 3:52 PM, Stuart Tremain <webdna@idfk.com.au> = wrote:

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
"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

--------------------------------------------------------- = 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
--= -------------------------------------------------------
This message = is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To = unsubscribe, E-mail to: <talk-leave@webdna.us>
archi= ves: http://mail.webdna.us/l= ist/talk@webdna.us
Bug Reporting: support@webdna.us

= --Apple-Mail-6--825431670-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] An unknown error occured // Deadlock avoided (Stuart Tremain 2011)
  2. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  3. Re: [WebDNA] An unknown error occured // Deadlock avoided (Ronald Kirkland 2011)
  4. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  5. Re: [WebDNA] An unknown error occured // Deadlock avoided (Dan Strong 2011)
  6. Re: [WebDNA] An unknown error occured // Deadlock avoided (Ronald Kirkland 2011)
  7. Re: [WebDNA] An unknown error occured // Deadlock avoided (Govinda 2011)
  8. Re: [WebDNA] An unknown error occured // Deadlock avoided (Paul Willis 2011)
  9. Re: [WebDNA] An unknown error occured // Deadlock avoided (Dan Strong 2011)
  10. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  11. Re: [WebDNA] An unknown error occured // Deadlock avoided (Dan Strong 2011)
  12. Re: [WebDNA] An unknown error occured // Deadlock avoided (christophe.billiottet@webdna.us 2011)
  13. Re: [WebDNA] An unknown error occured // Deadlock avoided ( 2011)
  14. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  15. Re: [WebDNA] An unknown error occured // Deadlock avoided (Dan Strong 2011)
  16. Re: [WebDNA] An unknown error occured // Deadlock avoided ( 2011)
  17. Re: [WebDNA] An unknown error occured // Deadlock avoided ( 2011)
  18. Re: [WebDNA] An unknown error occured // Deadlock avoided (Govinda 2011)
  19. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  20. Re: [WebDNA] An unknown error occured // Deadlock avoided (Dan Strong 2011)
  21. Re: [WebDNA] An unknown error occured // Deadlock avoided ( 2011)
  22. Re: [WebDNA] An unknown error occured // Deadlock avoided (Dan Strong 2011)
  23. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  24. Re: [WebDNA] An unknown error occured // Deadlock avoided ( 2011)
  25. Re: [WebDNA] An unknown error occured // Deadlock avoided (Ronald Kirkland 2011)
  26. Re: [WebDNA] An unknown error occured // Deadlock avoided (Tommy Bell 2011)
  27. Re: [WebDNA] An unknown error occured // Deadlock avoided (Tommy Bell 2011)
  28. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  29. Re: [WebDNA] An unknown error occured // Deadlock avoided (Stuart Tremain 2011)
  30. Re: [WebDNA] An unknown error occured // Deadlock avoided (christophe.billiottet@webdna.us 2011)
  31. Re: [WebDNA] An unknown error occured // Deadlock avoided (Ronald Kirkland 2011)
  32. Re: [WebDNA] An unknown error occured // Deadlock avoided (Stuart Tremain 2011)
  33. RE: [WebDNA] An unknown error occured // Deadlock avoided ("Terry Nair" 2011)
  34. Re: [WebDNA] An unknown error occured // Deadlock avoided (Ronald Kirkland 2011)
  35. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  36. Re: [WebDNA] An unknown error occured // Deadlock avoided (christophe.billiottet@webdna.us 2011)
  37. Re: [WebDNA] An unknown error occured // Deadlock avoided (Ronald Kirkland 2011)
  38. Re: [WebDNA] An unknown error occured // Deadlock avoided (Ronald Kirkland 2011)
  39. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  40. Re: [WebDNA] An unknown error occured // Deadlock avoided (Tommy Bell 2011)
  41. Re: [WebDNA] An unknown error occured // Deadlock avoided (Kenneth Grome 2011)
  42. Re: [WebDNA] An unknown error occured // Deadlock avoided (christophe.billiottet@webdna.us 2011)
  43. Re: [WebDNA] An unknown error occured // Deadlock avoided (Tommy Bell 2011)
  44. Re: [WebDNA] An unknown error occured // Deadlock avoided (christophe.billiottet@webdna.us 2011)
  45. Re: [WebDNA] An unknown error occured // Deadlock avoided (Tommy Bell 2011)
  46. Re: [WebDNA] An unknown error occured // Deadlock avoided (Govinda 2011)
  47. Re: [WebDNA] An unknown error occured // Deadlock avoided (christophe.billiottet@webdna.us 2011)
  48. [WebDNA] An unknown error occured // Deadlock avoided (Tommy Bell 2011)
--Apple-Mail-6--825431670 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii It does seem to be coming regularly from one template that shares a heap = of code with other templates. I do get it on a few other templates but not on a regular basis. There is NO [exclusivelock] context anywhere in the site. At first I thought that the problem was a DOS attack as it has the same = effect. Rebooting the server always fixes the problem, this is because = the infinite loop that is causing the problem is broken. I have just had another look at my errorlog.txt and see that it has = happened 38 times in one second in one instance when I really load up = the server with a big search. It may be a not enough RAM, but the machine is fairly well speced. DB's = range from 20-70MB. I can not pin it down to certain instances, as it does not always happen = as you would expect if there was bad code. It may be a general error message that is not worded correctly that = should read something along the lines of "An error has occurred to = which there is no known cause" . This is the line from my errorlog.txt: 04/07/201114:25:15ShowPage089.000.100.031An = unknown error occurred:
DBError
^data/pendingorders.db
Failed = to aquire lock on database - Possible deadlock averted

= /pending_scan03.htmlpending/pending_order.inc Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 11/07/2011, at 9:01 AM, Ronald Kirkland wrote: > Well sadly it would appear you are not alone. I did a quick Google > search for the error message and it appears that FirstNorth.com, > starnewsgroup.com, www.laserdisken.dk, and a few others are having the > same issue. This does appear to be a WebDNA generated error (not > saying it is caused by WebDNA). >=20 > Stuart, how often does this happen? Can you trigger the behavior when > you do something specific or it is completely random? >=20 >=20 >=20 > On Sun, Jul 10, 2011 at 3:52 PM, Stuart Tremain = wrote: >>=20 >> 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. >>=20 >> 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. >>=20 >> Regards >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >> On 07/07/2011, at 5:10 AM, Tommy Bell wrote: >>=20 >> Hello everyone, a few days ago a post was made about >> "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 >>=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 > --------------------------------------------------------- > 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-6--825431670 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii It = does seem to be coming regularly from one template that shares a heap of = code with other templates.

I do get it on a few other = templates but not on a regular basis.

There is NO = [exclusivelock] context anywhere in the site.

At = first I thought that the problem was a DOS attack as it has the same = effect. Rebooting the server always fixes the problem, this is because = the infinite loop that is causing the problem is = broken.

I have just had another look at my = errorlog.txt and see that it has happened 38 times in one second in one = instance when I really load up the server with a big = search.

It may be a not enough RAM, but the = machine is fairly well speced. DB's range from = 20-70MB.

I can not pin it down to certain = instances, as it does not always happen as you would expect if there was = bad code.

It may be a general error message = that is not worded correctly that should read something along the lines = of  "An error has occurred to which there is no known cause" = .

This is the line from my = errorlog.txt:

04/07/2011= 14:25:15= ShowPage= 089.000.100.031An unknown error occurred:<br>DBError<br>^data/pendingorders.db<br>Failed to aquire lock on database - Possible = deadlock averted<br><br>/pending_scan03.html= pending/pending_order.inc


=


Regards

Stuart = Tremain
IDFK Web Developments
AUSTRALIA




On 11/07/2011, at 9:01 AM, Ronald Kirkland wrote:

Well = sadly it would appear you are not alone. I did a quick Google
search = for the error message and it appears that FirstNorth.com,
starnewsgroup.com, www.laserdisken.dk, and a few = others are having the
same issue. This does appear to be a WebDNA = generated error (not
saying it is caused by WebDNA).

Stuart, = how often does this happen? Can you trigger the behavior when
you do = something specific or it is completely random?



On Sun, = Jul 10, 2011 at 3:52 PM, Stuart Tremain <webdna@idfk.com.au> = wrote:

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
"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

--------------------------------------------------------- = 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
--= -------------------------------------------------------
This message = is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To = unsubscribe, E-mail to: <talk-leave@webdna.us>
archi= ves: http://mail.webdna.us/l= ist/talk@webdna.us
Bug Reporting: support@webdna.us

= --Apple-Mail-6--825431670-- Stuart Tremain

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

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...

Related Readings:

Max Record length restated as maybe bug (1997) [WebDNA] Build Name for 6.1 (2008) [WebDNA] Email Log.txt (2014) restarting service remotely on NT (1997) WC Database Format (1997) 2.0Beta Command Ref (can't find this instruction) (1997) WYSIWYG Entry of text fields (2001) Encrypting WebDNA Templates and eligible files (1999) Listserver problem (1997) question: back button prevention (1997) Webcat/Webmerchant part II (1998) WebCatb15 Mac CGI -- [purchase] (1997) Webmerchant PC auth (1998) Criticism of WebCatalog: Keep It Coming! (1998) SSI *nix 4.5 build (2002) db merge problem (2002) Replace command help (1998) [format xs] freeze (1997) [ShowNext] feature in 2.0 (1997) Help! WebCat2 bug (1997)