Broken since updating to 1.4.0.4 (during database migration??)
See original GitHub issueSince updating to 1.4.0.4 syncthing-fork is always shutting down. It seems there are errors in migrating the database (see attached log). The mentioned pictures are,since long ago, not on my mobile anymore. I don’t understand other error ‘another instance may be already running’ since it’s the only session. If I remove and install the app it’s working as long as I don’t import my settings…
23:23:08 [start] INFO: syncthing v1.4.0 "Fermium Flea" (go1.13 android-arm64) vagrant@basebox-stretch64 2020-03-06 19:52:22 UTC
23:23:10 [start] INFO: No automatic upgrades; STNOUPGRADE environment variable defined.
23:23:10 [GMFW6] INFO: My ID: 12345-67890-blahblah-blah-blah-blah
23:23:11 [GMFW6] INFO: Single thread SHA256 performance is 1446 MB/s using crypto/sha256 (1374 MB/s using minio/sha256-simd).
23:23:11 [GMFW6] INFO: Hashing performance is 593.53 MB/s
23:23:11 [GMFW6] INFO: Migrating database to schema version 9...
23:26:29 [GMFW6] WARNING: Database schema: leveldb/table: Writer: keys are not in increasing order: "\x01\x00\x00\x00\x00Camera/IMG_20181226_190237.jpg\x01\t\xe0h\x00\x00\x00\x00", "\x01\x00\x00\x00\x00Camera/IMG_20181226_160004.jpg\x01w\x92\x12\x00\x00\x00\x00"
23:26:29W/SyncthingRunnable exit reason = exitError. Another Syncthing instance may be already running.
23:26:29I/SyncthingService onServiceStateChange: from ERROR to DISABLED
23:26:29I/Util runShellCommandGetOutput: Exited with code 0
23:26:29W/ApiRequest Request to https://127.0.0.1:8384/rest/system/shutdown failed, java.net.ConnectException: Failed to connect to /127.0.0.1:8384
23:26:36I/Util runShellCommandGetOutput: Exited with code 0
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Layouts fail when migrating from local to staging server. #403
I'm exporting the database using Migrate DB, to automate all the renaming, and it works fine for everything other than Elementor.
Read more >Broken database migrations: How we finally fixed an ...
The issue. Upgrades of Sourcegraph instances, including on-premise deployments and our Cloud environment, would often fail with a dreaded " ...
Read more >Troubleshooting migration tasks in AWS Database Migration ...
Troubleshoot issues when migrating data using AWS Database Migration Service (AWS DMS).
Read more >Oracle Zero Downtime Migration Release Notes, Release 19c
Issue: Zero Downtime Migration writes the source and target log files to the /tmp/zdm-unique id directory in the respective source and target database...
Read more >Fix List for Rational Synchronization Server - IBM
When you describe a problem to an IBM software support specialist, ... to the local database should not be considered for migration or ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So it looks like my database is broken (don’t know why, but see https://forum.syncthing.net/t/keys-not-in-increasing-order/14720) and I close this issue…
Edit: ok you already got feedback there.