![]() ![]() ![]() ![]() USER=syncthing GROUP=sc-syncthing SHARE_PATH=ħ 09:19:13 upgrade syncthing 1.17.0-22 End postuninst ret=ħ 09:19:13 upgrade syncthing 1.17.0-22 Begin preinstħ 09:19:13 => Step preinst. USER=sc-syncthing GROUP=sc-syncthing SHARE_PATH=ħ 09:16:21 upgrade syncthing 1.17.0-22 End preupgrade ret=ħ 09:16:21 upgrade syncthing 1.17.0-22 Begin preuninstħ 09:16:21 => Step preuninst. Looking at the package log, I can't see anything that differs from previous upgrade entries - though I am confused by `Begin /bin/rm -rf - I can't see how the app data is preserved through this.ħ 08:41:45 install syncthing 1.17.0-22 Begin start-stop-status stopħ 08:41:48 install syncthing 1.17.0-22 End start-stop-status stop ret=ħ 09:09:45 (system) trigger syncthing 1.17.0-22 Begin start-stop-status stopħ 09:09:46 (system) trigger syncthing 1.17.0-22 End start-stop-status stop ret=ħ 09:16:21 upgrade syncthing 1.17.0-22 Begin preupgradeħ 09:16:21 => Step preupgrade. Looking in (the DSM7 location), I can see a full complement of setup files - but these have been generated anew. Looking in (the DSM6 location), I can only see new `config.xml` and `nf` files - the `index-v0.14.0.db` folder etc are entirely missing. On launching Syncthing after this, I was greeted with a default setup. ![]() Repaired the Syncthing package after the DSM upgrade. Ensured the Syncthing package was up to date I've not had any such problems before (and I have successfully upgraded another Synology NAS with the same configuration), but today I performed the following sequence of actions: Syncthing setup files were apparently deleted. Syncthing setup files should be preserved ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |