Re: JMRI Profile File Written With Zero Bytes
|
Paul, The "compare" process does a temporary store and compares that to the last loaded xml data file. ?If there are differences, then there have been changes since the last store. ?The default settings in Preferences -> Shutdown are to notify you that have changes that have not been stored. ?You are then given the option of continuing the shutdown (discarding the changes) or to do a store before the shutdown continues. ?This has no impact on the actual store process. The symptoms indicate that Linux was not able to flush the file cache before the Pi shutdown. Note: ?I assume that the "profile file" is the layout data xml file, aka "panel" file. ?"profile file" normally refers to the "profile.xml" file that contains the connection and start up settings. Dave Sand ----- Original message ----- From: Paul Wash <paul.wash@...> Subject: [jmriusers] JMRI Profile File Written With Zero Bytes Date: Sunday, April 06, 2025 4:50 PM Hopefully this can help others who experience the same problem. This has happened 3 or 4 times in the last 5 years - so not often. When opening JMRI, you get the dreaded unexpected EOF error loading the profile. Sure enough - the profile file is zero bytes. ? Easy fix - in the active jmri-profile folder there is a backupPanels folder under the railroad name. Simply copy that file back under the railroad folder - rename to whatever the profile file is called in your settings. Hopefully it is recent enough you didn't lose much of anything. The backup interval looks like when the profile is saved. All shutdowns have been nominal. No idea why it happens...Maybe it's an RPI thing, maybe it took to long to write and I did a system shutdown before it was ready? Who knows. ? The folder structure is below. ? ? For more info - Specs: RPI 5 bookworm with all latest updates running JMRI 5.10. The log file is below - it shows whenever this happens there is a compare failure. Guess that writes out 0 bytes and keeps on truckin... ? ? ? |