Thank you for your reply. Good suggestions. Yes, plain vanilla node on Ubuntu 18.04. Definitely editing in exactly one browser tab. Not using Bob. $:/config/AutoSave says yes.
I've put the whole wiki into git and set up gitwatch saving on a 60-second interval. If I can just figure out how to get git to tell me what change happened when, at least I'll have the sequence of events. Either the changes aren't making it to the server or they're getting overwritten. If I can tell which, then I can start working to correct it. On Monday, September 2, 2019 at 11:07:12 PM UTC-4, TonyM wrote: > > Kevin, > > I do not necessarily have the skills to help but are you using vanila node > and what platform? presumably a linux flavor. > > - Could you have the same wiki open in more than one > window/tab/browser? so latest tiddler save wins? > - The Bob versions help combat multi-access issues, bob.exe is very > easy to use (but may be awaiting 5.1.20) > - If you have a link to such wikis you may consider using a link that > includes the target=wikname so that every time you click on the link it > opens in the save window/tab, presumably you have autosave to immediately > save changes? > > In some single file wikis, I have not looked at on node yet, you could use > 5.1.20's local storage plugin to save changes locally, pending the wiki > save. > > Regards > Tony > > On Tuesday, September 3, 2019 at 7:06:53 AM UTC+10, Kevin Kleinfelter > wrote: >> >> It just happened again. >> >> - I specifically checked to be sure the save icon went from red to >> gray. >> - Then I opened the tiddler and copied it to the clipboard. >> - Then I went to the server and issued 'sudo reboot'. >> >> The wiki came up with a multiple versions old edition of that tiddler. I >> opened the tiddler and pasted in my clipboard to restore. >> >> What's happening here? I really need my wiki not to forget edits! >> >> On Monday, September 2, 2019 at 4:38:32 PM UTC-4, Kevin Kleinfelter wrote: >>> >>> I'm running multiple node.js tiddlywikis. Twice in the last few days >>> I've lost some data. I need help to improve my operating practices! >>> >>> The symptom is that I have lost the last 2-3 edits to a tiddler. I've >>> been mostly editing the same long tiddler. I've had a need to reboot my >>> Linux server, so I connected to it via ssh and issued 'sudo reboot'. >>> >>> My Tiddlywikis generally push their updates to the server within a few >>> seconds. I have no reason to believe that didn't happen on these occasions. >>> >>> Due to the server restart, I've received the failed-to-sync message for >>> the skinny tiddler list. I refresh the browser page. That's when I >>> discover that the tiddler I've been editing off and on all day has reverted >>> back 2-3 editions. Ouch! >>> >>> Can someone please walk me through the steps (at the elementary lever) >>> to ensure that I don't lose node.js TW data when I restart my server? >>> Maybe it is something like this? >>> >>> 1. Check each browser tab with a Tiddlywiki. Confirm that the save >>> icon is NOT red. >>> 2. >>> >>> ps -ef | grep node | grep tiddly >>> 3. >>> >>> sudo reboot >>> >>> Do I need to specifically shut-down the node processes which are running >>> TiddlyWiki? (I have other node.js running too.) >>> Do I need to send a SIGHUP to the node processes? >>> >>> TIA >>> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/dd4ec81c-108f-4b6d-acba-305de69838f0%40googlegroups.com.
