Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106888
interpreted = N
texte = 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
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/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
Associated Messages, from the most recent to the oldest:
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 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/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
Ronald Kirkland
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:
Adding up line items. (2000)
Sort Order on a page search (1997)
OT: How to get more traffic to a site? (2005)
Re:trouble (1997)
File Info Cache Size is out of range? (1998)
Stat analyzer (1997)
WebCatalog vs WebDNA (2002)
Upload Plugin (1998)
Help- Linux Install Serial number not taling. (2000)
Register First (2000)
[WebDNA] Manually push a new .db for WebDNA to adapt (2017)
Ad Serving Software (2002)
Trouble with emailer (2000)
A question on sub-categories (1997)
Anyone have a register your domain app? (2000)
[Fwd: F3 database munching] (1997)
webcat nt (1997)
OT (stupid redirect/refresh question) (2002)
Am I going senile? (Price recalc based on quantity) (1997)
Simple way to create unique SKU (1997)