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
=div>
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:
--Apple-Mail-6--825431670Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiIt 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.incRegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 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--825431670Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiIt =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
=div>
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:
Appending with +1 ... (1997)
GuestBook example (1997)
[username][password] not showing up. (2000)
[shownext] (1998)
[LOOKUP] (1997)
OK, here goes... (1997)
NetForms for email (1998)
Sort Order on a page search (1997)
[WebDNA] WebDNA slow processing (2011)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
carriage returns in data (1997)
WebCatalog Hosting (1996)
What am I doing wrong? (2000)
WebCat2b15MacPlugin - showing [math] (1997)
WebCat2b15MacPlugin - showing [math] (1997)
WebCat2: multiple currency support (1997)
GuestBook example (1997)
Cyberstudio and WebDNA (1997)
Smart caching problems with 2.1b3? (1997)
problems with 2 tags shakur (1997)