Jungle Disk uses databases for a variety of purposes, such as local caching of file/folder information, sync information, and backups vaults. We've included examples of the most common errors on this guide along with instructions on how to fix them.
- Disk I/O Error
- Database Locked on Startup or Sync
- Database Malformed on Startup
- Database Malformed on Sync
Disk I/O Error
Backup failed Warning Details (Jungle Disk Server Edition 3.16 Win32) ------------------------ Failed to commit Chunk in Backup DB Exception Code: xDatabaseFailure (83) Time: 8/5/2015 7:22:46 AM (GMT-8) Detailed Message: Database request failed [10]: disk I/O error Error Location: BaseDB.cpp:176 SqlStatement::Step via BaseDB.cpp:196 BaseDB::CommitTransaction
This error indicates that the drive your Cache Directory is in has run out of space.
Typically, the best way to approach this would be to move your Cache Directory to a drive that has more free space.
The amount of space you need free varies and depends on the size of your database file and cached data.
Database Locked on Startup or Sync
Failed to sync between "C:\Users\Jimmy\Desktop\" and "/sync/Destkop/" Warning Details (Jungle Disk Workgroup 3.16 Win64) ------------------------ xDatabaseFailure - Failed to open database file C:\Users\Jimmy\Desktop\.sync.db: unable to open database file (14) Exception Code: xDatabaseFailure (83) Time: 03/22/20xx 1:19:36 PM (GMT-5) Detailed Message: Failed to open database file C:\Users\Jimmy\Desktop\.sync.db: unable to open database file (14) Error Location: BaseDB.cpp:38 BaseDB::Open via SyncJob.cpp:1380 SyncJob::OpenSyncDb via SyncJob.cpp:240 SyncJob::InitializeDb via SyncJob.cpp:62 SyncJob::Run via SyncManager.cpp:532 SyncManager::ExecuteAsyncThread
This error is due to a database (that Jungle Disk uses) being in a locked state (indicating it's 'in use') before the Jungle Disk service you're using has a chance to access the database.
Jungle Disk uses databases for a few different reasons, but the most common for this error would be for Backup Vaults or for Network Drive Cache, but this can happen for Sync Folders as well.
A common way this error comes up is if you have multiple Jungle Disk processes running at the same time (an issue usually due to receiving an error message when trying to restart the Jungle Disk Service in Windows).
Here are some steps to address this:
- If you do not have administrative privileges on this computer:
- Restart your computer
- If you do have administrative privileges on this computer:
Windows
- Open the Services program (Start > type "services" and run the "Services" or "Local Services" program)
- Here, find and Stop the "JungleDisk..." service.
- Minimize Services and Open Task Manager (CTRL+ALT+DELETE).
- Navigate to the Processes tab and sort it by Name.
- If you see the option to 'show processes for all users' in the bottom-left, click this option (you will need to be an administrator of this computer.
- Examine it to verify if you see any "JungelDisk..." services running as the "SYSTEM" user. If you do, right-click and select to end the process tree for each of them.
- Afterwards, return to the Services window and right-click the "JungleDisk..." service to select Start.
Mac
- Open Activity Monitor (/Applications/Utilities/Activity Monitor.app)
- Ensure your title says "Activity Monitor (All Processes). If it does not, then select View > All Processes.
- Select the CPU tab and run a search for "Jungle"
- Select each process one by one and click the Stop icon to the far left of the button bar and click Force-Quit
- Processes running as "ROOT" will automatically start back up again if they are supposed to (no problem there), but you will now need to Open the Jungle Disk app again (you can find this under /Applications)
This should get things working for you again, but please contact us if you have any trouble with these steps or if they don't seem to work for you.
Database Malformed on Startup
![]() |
![]() |
This would mean that one of your databases is corrupt and will need to be deleted so that Jungle Disk can either re-download or recreate that database to get things working again.
- If you do not have administrative privileges on this computer:
- Contact your administrator and share this guide with him/her.
- If you do have administrative privileges on this computer:
Windows
- Open the Services program (Start > type "services" and run the "Services" or "Local Services" program)
- Here, find and Stop the "JungleDisk..." service.
- Minimize Services and open Windows Explorer, then paste this directory path into your address bar:
C:\ProgramData\JungleDisk\
- If you're using Desktop Edition, then double-click on the "cache" folder... or if using Jungle Disk ( Formerly Workgroup) Edition, double-click on the "wg-cache" folder instead.
- Here, delete all folders except for the "logs" folder.
- Once done, open Services again and Start the "JungleDisk..." service.
Mac
Open Terminal (/Applications/Utilities/Terminal.app) and run the following commands:
- Versions 3.31.2 and higher
- Jungle Disk (Formerly Workgroup)
- sudo launchctl unload ~/Library/LaunchAgents/com.jungledisk.workgroupservice.plist
- find ~/Library/Caches/jungledisk/wg-cache/* ! -name 'logs' -type d -maxdepth 0 -exec rm -rf {} +
- sudo launchctl load ~/Library/LaunchAgents/com.jungledisk.workgroupservice.plist
- Desktop Edition
- sudo launchctl unload ~/Library/LaunchAgents/com.jungledisk.service.plist
- find ~/Library/Caches/jungledisk/cache/* ! -name 'logs' -type d -maxdepth 0 -exec rm -rf {} +
- sudo launchctl load ~/Library/LaunchAgents/com.jungledisk.service.plist
- Jungle Disk (Formerly Workgroup)
- Versions 3.30.6 and lower
- Jungle Disk (Formerly Workgroup)
- sudo launchctl unload /Library/LaunchDaemons/com.jungledisk.workgroupservice.plist
- find /Library/Caches/jungledisk/wg-cache/* ! -name 'logs' -type d -maxdepth 0 -exec rm -rf {} +
- sudo launchctl load /Library/LaunchDaemons/com.jungledisk.workgroupservice.plist
- Desktop Edition
- sudo launchctl unload /Library/LaunchDaemons/com.jungledisk.service.plist
- find /Library/Caches/jungledisk/cache/* ! -name 'logs' -type d -maxdepth 0 -exec rm -rf {} +
- sudo launchctl load /Library/LaunchDaemons/com.jungledisk.service.plist
- Jungle Disk (Formerly Workgroup)
Database Malformed on Sync
Failed to sync between "C:\Users\jimmy\Desktop\Data" and "/sync/Data/" Warning Details (Jungle Disk Desktop 3.16 Win32) ------------------------ xDatabaseFailure - Database request failed [11]: database disk image is malformed Exception Code: xDatabaseFailure (83) Time: 7/5/2015 3:18:56 PM (GMT-6) Detailed Message: Database request failed [11]: database disk image is malformed
This error is saying that the .sync.db
file (hidden in each local root directory you're syncing with) has become corrupt/malformed. It will need to be deleted and here's how to do so:
- Open the Jungle Disk Activity Monitor and right-click the Errors & Warnings panel, then click "Clear All Errors" (so we notice new errors if they happen).
- Click Configure and navigate to the Sync Folders section for your first online disk in the list and uncheck all folders from this page. (this would be under Online Disk > Network Drive > Sync Folders)
- When all folders are unchecked, click OK to save the changes. This should cause the local Sync Folders'
.sync.db
files to be deleted - After this, click Configure again and return to the Sync Folder section.
- Add back your sync folders as you had them before and it should work for you now.
If that doesn't fix the problem for you, please contact our support team and let us know that you've already completed the steps on this guide and still need help.