Fixing Workspace Sync Issues - REL7210.5-17

Summary

This article outlines the steps system administrators must follow to resolve workspace sync failures. The fix includes updating spaceutil.php, restarting PHP services, and clearing stalled sync locks.

1. Update spaceutil.php

Steps

1. Navigate to the PHP directory: cd /mnt/data/magnum/secure/REL7210.5-17/php

2. Copy the updated spaceutil.php from S3: aws s3 cp s3://ssmdrive/php/spaceutil.php .

3. Update permissions: chmod 774 spaceutil.php

4. Update ownership: chown deploymentuser: spaceutil.php

2. Restart PHP 8.5

Restart the PHP-FPM service to apply the fix.

service php8.5-fpm restart

(Optional) Check status:

service php8.5-fpm status

3. Reset Workspace Sync Status

1. Open the sync status file: /mnt/data/private/_runningwsmsync.txt

2. If the file contains: 3 Change it back to: 0

4. Remove Sync Lock Directories

1. Navigate to the workspace directory (example shown): cd /mnt/data/private/_ws/110/

2. Remove stale sync lock folders: find . -type d -name "_mirror.txt_synclock" | xargs rm -rf

5. Validation Steps

After applying the fix:

• Confirm php8.5-fpm is running normally.
• Ask SO to initiate a workspace sync and ensure it completes.
• Verify no new _mirror.txt_synclock folders are generated unnecessarily: find . -type d -name "_mirror.txt_synclock"