Re: [WebDNA] "Safe Write for Database" setting....
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112636
interpreted = N
texte = 219 If a reboot doesn=92t fix it, maybe write some troubleshooting code. On the form, write to a debug file exactly what webdna is going to write = to the database. Directly after, do a search on that database and write = to the debug file the result of what happened after the database = transaction. Surround the entire thing in [elapsedtime] and record that as well.=20 Sincerely, Donovan On Mar 15, 2016, at 9:52 PM, Rich Kwas
= wrote: > Like usual, it happened 2x on 2 different ad listings I'm being told, = and been stable ever since. > That's what makes it so frustrating. Can't seem to pin down the why. >=20 > I'll keep my eye on those error logs.. >=20 >=20 >=20 >=20 > On Tuesday, March 15, 2016 7:45 PM, Donovan Brooke = wrote: >=20 >=20 > This means that you haven't had any issues with your database. (No = need to mess with safe write) =20 >=20 > Watch that your error logs don't get too big, now that you've turned = them on.=20 >=20 > Lots of stuff can change on a server in 10 years ;-) (Even if you = don't touch it) >=20 > I'd start with Stuart's suggestion.=20 >=20 > D. Brooke Mobile >=20 > On Mar 15, 2016, at 5:13 PM, Rich Kwas = wrote: >=20 >> I don't seem to have any .db-tmp files anywhere . >> They would be in the same "globals " folder as the main database = right? >>=20 >> I did not have error logging turned on. >> Just enabled that. >>=20 >> Nothings changed in this site really for years and years. Same db, = same admin area, same everything. Just every now and then this occurs. >>=20 >>=20 >>=20 >>=20 >> On Tuesday, March 15, 2016 4:43 PM, Stuart Tremain = wrote: >>=20 >>=20 >> Are you getting a lot of .db-tmp files being written for the db ? >>=20 >> If you are then there could be a problem with either your code or = some of the content, based on the fact that the site has been = operational for many years, I would open the .db file and check the = content, also check your error log.txt >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 16 Mar 2016, at 08:09, Rich Kwas = wrote: >>>=20 >>> I already using [COMMITDATABASE db=3DFileName] in all the admin = pages where they edit these ads... >>>=20 >>> Problem still pops up every now and then, like today again. >>>=20 >>> Thoughts on the "Safe Write" setting? >>>=20 >>>=20 >>> On Tuesday, March 15, 2016 4:01 PM, Stuart Tremain = wrote: >>>=20 >>>=20 >>> =46rom memory, there was a bug in =93Automatically commit databases = to disk after modification=94, I wonder if this was associated with your = problem ? >>>=20 >>> You can always add [COMMITDATABASE db=3DFileName] after the = modification just to make sure. >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On 16 Mar 2016, at 07:15, Rich Kwas = wrote: >>>>=20 >>>> Is it safe to disable ""Safe Write for Database" in Preferences??? >>>>=20 >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> Safe Write DB: >>>> Enabled by default. Sets the WebDNA engine to create a temporary = file when writing the contents of a database to disk. The temporary file = contents are then moved to the original database file after the entire = database is completely flushed to disk. This helps to eliminate = corruption of the original database file if there is an interruption = during the database write process. >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >>>>=20 >>>> If I disable this setting will all changes be written to the db on = the HD immediately, without that need for a temporary file? >>>>=20 >>>> I've been having this issue "again" where a client says they make = changes to ad listings stored in the database, but then all the changes = are gone a few moments later. Like they never were altered in the first = place.... >>>>=20 >>>> This site has been for over 10 years and the admin area has not = been changed recently or much over that time span... >>>>=20 >>>> There is no consistency to this issue. >>>> It happens (like today) but may not happen for days or weeks. >>>>=20 >>>> I'm wondering if this "temporary file" and the original database on = disk are somehow under some circumstances getting out of sync. >>>>=20 >>>> The db isn't that large, having 2,111 records,151 Fields and using = 4,759K of ram. >>>>=20 >>>> I'm wondering if disabling "Safe Write" might be an option to try = and prevent this in the future. >>>>=20 >>>> Very frustrating for the client.I can't seem to duplicate it = myself,but I believe them when they say it happens.I may have posted = about this issue in the past as well. >>>>=20 >>>>=20 >>>> I'm on Windows Server2008 using vers.6.2 >>>> I have nearly 1gb of unused ram on the server, plenty of hard drive = space.... >>>>=20 >>>>=20 >>>> I've attached a screen capture of my Preferences in case anything = else can be tinkered with. >>>>=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 >>>=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 >>=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 > --------------------------------------------------------- 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 >=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 .
Associated Messages, from the most recent to the oldest:
219 If a reboot doesn=92t fix it, maybe write some troubleshooting code. On the form, write to a debug file exactly what webdna is going to write = to the database. Directly after, do a search on that database and write = to the debug file the result of what happened after the database = transaction. Surround the entire thing in [elapsedtime] and record that as well.=20 Sincerely, Donovan On Mar 15, 2016, at 9:52 PM, Rich Kwas = wrote: > Like usual, it happened 2x on 2 different ad listings I'm being told, = and been stable ever since. > That's what makes it so frustrating. Can't seem to pin down the why. >=20 > I'll keep my eye on those error logs.. >=20 >=20 >=20 >=20 > On Tuesday, March 15, 2016 7:45 PM, Donovan Brooke = wrote: >=20 >=20 > This means that you haven't had any issues with your database. (No = need to mess with safe write) =20 >=20 > Watch that your error logs don't get too big, now that you've turned = them on.=20 >=20 > Lots of stuff can change on a server in 10 years ;-) (Even if you = don't touch it) >=20 > I'd start with Stuart's suggestion.=20 >=20 > D. Brooke Mobile >=20 > On Mar 15, 2016, at 5:13 PM, Rich Kwas = wrote: >=20 >> I don't seem to have any .db-tmp files anywhere . >> They would be in the same "globals " folder as the main database = right? >>=20 >> I did not have error logging turned on. >> Just enabled that. >>=20 >> Nothings changed in this site really for years and years. Same db, = same admin area, same everything. Just every now and then this occurs. >>=20 >>=20 >>=20 >>=20 >> On Tuesday, March 15, 2016 4:43 PM, Stuart Tremain = wrote: >>=20 >>=20 >> Are you getting a lot of .db-tmp files being written for the db ? >>=20 >> If you are then there could be a problem with either your code or = some of the content, based on the fact that the site has been = operational for many years, I would open the .db file and check the = content, also check your error log.txt >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 16 Mar 2016, at 08:09, Rich Kwas = wrote: >>>=20 >>> I already using [COMMITDATABASE db=3DFileName] in all the admin = pages where they edit these ads... >>>=20 >>> Problem still pops up every now and then, like today again. >>>=20 >>> Thoughts on the "Safe Write" setting? >>>=20 >>>=20 >>> On Tuesday, March 15, 2016 4:01 PM, Stuart Tremain = wrote: >>>=20 >>>=20 >>> =46rom memory, there was a bug in =93Automatically commit databases = to disk after modification=94, I wonder if this was associated with your = problem ? >>>=20 >>> You can always add [COMMITDATABASE db=3DFileName] after the = modification just to make sure. >>>=20 >>> Kind regards >>>=20 >>> Stuart Tremain >>> IDFK Web Developments >>> AUSTRALIA >>> webdna@idfk.com.au >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>> On 16 Mar 2016, at 07:15, Rich Kwas = wrote: >>>>=20 >>>> Is it safe to disable ""Safe Write for Database" in Preferences??? >>>>=20 >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> Safe Write DB: >>>> Enabled by default. Sets the WebDNA engine to create a temporary = file when writing the contents of a database to disk. The temporary file = contents are then moved to the original database file after the entire = database is completely flushed to disk. This helps to eliminate = corruption of the original database file if there is an interruption = during the database write process. >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >>>>=20 >>>> If I disable this setting will all changes be written to the db on = the HD immediately, without that need for a temporary file? >>>>=20 >>>> I've been having this issue "again" where a client says they make = changes to ad listings stored in the database, but then all the changes = are gone a few moments later. Like they never were altered in the first = place.... >>>>=20 >>>> This site has been for over 10 years and the admin area has not = been changed recently or much over that time span... >>>>=20 >>>> There is no consistency to this issue. >>>> It happens (like today) but may not happen for days or weeks. >>>>=20 >>>> I'm wondering if this "temporary file" and the original database on = disk are somehow under some circumstances getting out of sync. >>>>=20 >>>> The db isn't that large, having 2,111 records,151 Fields and using = 4,759K of ram. >>>>=20 >>>> I'm wondering if disabling "Safe Write" might be an option to try = and prevent this in the future. >>>>=20 >>>> Very frustrating for the client.I can't seem to duplicate it = myself,but I believe them when they say it happens.I may have posted = about this issue in the past as well. >>>>=20 >>>>=20 >>>> I'm on Windows Server2008 using vers.6.2 >>>> I have nearly 1gb of unused ram on the server, plenty of hard drive = space.... >>>>=20 >>>>=20 >>>> I've attached a screen capture of my Preferences in case anything = else can be tinkered with. >>>>=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 >>>=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 >>=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 > --------------------------------------------------------- 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 >=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 .
Donovan Brooke
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:
Mozilla/4. and Browser Info.txt (1997)
no global [username] or [password] displayed ... (1997)
[subtotal] and others (1997)
OT: Poll Results (2002)
searchable list archive (1997)
Summ=T Problem (1997)
Purchase command error problem (1997)
Lots of bounce errors (2007)
WebCat2b12 CGI Mac - [shownext] problem (1997)
Cookies (1999)
WebCatalog can't find database (1997)
Communigate+Webcat (2001)
Customer - again (1998)
WCS Newbie question (1997)
Calculating multiple shipping... (1997)
Sorting by date (1997)
shipCost (2000)
WebCat2b12plugin - [search] is broken ... not! (1997)
[WebDNA] Just drop the Server version (2015)
passing search criteria (1997)