Troubleshoot CouchDB

Google Workspace Migrate can consume a large amount of disk space on the CouchDB server. You should periodically monitor the CouchDB disk to avoid running out of space.

If you can't monitor the disk, look for these indications that the CouchDB disk is full:

• Detailed bridge transaction information isn't accessible.
• Bridge partitions fail to launch.
• CouchDB administration page (http://localhost:5984/_utils or equivalent address based on your configuration) doesn't load.
• The service host logs on the Google Workspace Migrate platform or node server have CouchDB errors with the following strings:
  • badarg
  • unknown_error
  • function_clause

If you observe these symptoms, first ensure that CouchDB is running:

1. Sign in to the CouchDB machine.
2. Open the Windows Run command window and enter services.msc to open the Services app.
3. Find Apache CouchDB in the list of services.
4. If the service status is not Running, right-click Apache CouchDB and select Start. 

Option 1: Delete old data

You can free up space by deleting any bridges or projects that you no longer need. 

You can also free up space by clearing transaction log details from existing bridges:

1. Go to http://localhost:5131/#/clear-transaction-details (or equivalent address based on your configuration).

2. Select the bridges to clear and click Delete .

3. (Optional) To retain transaction detail information from the most recent execution of each bridge, select Preserve details from most recent executions.

   Note: This option clears a CouchDB disk that's full from running one bridge multiple times. We don't recommend selecting this setting if you run all your bridges at one time, as it won't free up extra space. If you don't select this option, all transaction detail information for the selected bridges is cleared while the transaction records are retained.

4. Click Yes to start the process.

5. Click Details to verify the bridge transaction logs are empty. The transaction detail information for the selected bridges should show No items to display.
6. Check CouchDB’s disk usage to make sure sufficient disk space is present. For details on CouchDB disk space requirements, go to System requirements.

Option 2: Increase the disk size

• Use Google Compute Engine to increase space. For details, go to Creating and attaching a disk.
• Move your CouchDB data directory to a larger disk. For details, consult your CouchDB documentation.

1. In your CouchDB installation, open the etc/local.ini file.
2. In the [admins] section, overwrite the password for the migrate user. Consult your CouchDB documentation for more information. 
3. Save the changes to the etc/local.ini file and then restart CouchDB.

Select a method below based on whether or not you can access the Google Workspace Migrate platform.

I can access the Google Workspace Migrate platform

1. In the Google Workspace Migrate platform, at the top, click Settings Database settings.
2. Enter the new password for CouchDB and for MySQL.

   Both passwords are required. If you don’t have the MySQL password, move to I can’t access the Google Workspace Migrate platform (below).

3. Click Continue and proceed to Step 3: Reassociate the nodes (below).

I can’t access the Google Workspace Migrate platform

1. Sign in to the machine that is running the platform.
2. On the taskbar, right-click Google Workspace Migrate and select Edit host settings. 
3. By CouchDB settings, click Password and enter the new password.
4. Click Save & CloseOK.
5. On the taskbar, right-click Google Workspace Migrate and select and select Stop Google Workspace Migrate service. Then, restart the service. 
6. Go to Step 3: Reassociate the nodes (below).

You need to complete this step to propagate the new database settings to the nodes.

1. In the Google Workspace Migrate platform, in the top-right corner, click Servers. 
2. Select all the nodes and click Delete .
3. Add the nodes using a CSV file or manually.

   For details, see Add the node servers.