Unknown deployment error: Error: EBUSY: resource busy or locked

OttoFMS
1

Running Otto 4.10.3 and 21.1.4 on Windows. We have been getting a lot of deployment errors with these two versions. So this will likely be one of a few posts as I go through our release process this week.

migrating	FILENAME1.fmp12	End: Fri May  9 02:11:32 2025
4:41:46.366
migrating	-	Data migration of FILENAME1.fmp12 complete in 4:29:23	4:41:46.426
migrating	-	Data migration complete	4:41:46.474
installing	FILE NAME.fmp12	Backing up original FILE NAME.fmp12	4:41:46.522
installing	FILENAME1.fmp12	Backing up original FILENAME1.fmp12	4:41:46.570
installing	FILENAME2.fmp12	Backing up original FILENAME2.fmp12	4:41:46.615
installing	FILENAME3.fmp12	Backing up original FILENAME3.fmp12	4:41:46.663
installing	FILENAME4.fmp12	Backing up original FILENAME4.fmp12	4:41:46.709
installing	FILENAME5.fmp12	Backing up original FILENAME5.fmp12
unknown phase	-	Unknown deployment error: Error: EBUSY: resource busy or locked, rename 'D:\FMS_Data\FOLDERNAME\FILE NAME.fmp12' -> 'E:\FMS_Backups\OttoFMS\deployment-backups\deploy-10\sub-deploy-10\FILE NAME.fmp12'	4:41:46.804
installing	FILENAME1.fmp12	Backing up original FILENAME1.fmp12	4:41:53.730
installing	FILENAME2.fmp12	Backing up original FILENAME2.fmp12	4:41:53.781
installing	FILENAME3.fmp12	Backing up original FILENAME3.fmp12	4:41:53.830
installing	FILENAME4.fmp12	Backing up original FILENAME4.fmp12	4:41:53.879
installing	FILENAME5.fmp12	Backing up original FILENAME5.fmp12	4:41:53.929
installing	FILENAME6.fmp12	Backing up original FILENAME6.fmp12	4:41:53.979
installing	FILENAME7.fmp12	Backing up original FILENAME7.fmp12	4:41:54.029
installing	FILENAME8.fmp12	Backing up original FILENAME8.fmp12	4:41:54.079
installing	FILENAME9.fmp12	Backing up original FILENAME9.fmp12	4:41:54.132
reverting	-	No files to close	4:41:54.994
reverting	-	Reinstalling backup files	4:41:55.048
reverting	-	Backup file not found for FILE NAME.fmp12	4:42:08.294
reverting	-	Backup file not found for FILENAME1.fmp12	4:42:08.342
reverting	-	Backup file not found for FILENAME2.fmp12	4:42:08.388
reverting	-	Backup file not found for FILENAME3.fmp12	4:42:08.436
reverting	-	Backup file not found for FILENAME4.fmp12	4:42:08.483
reverting	-	Backup file not found for FILENAME5.fmp12	4:42:08.531
reverting	-	Backup file not found for FILENAME6.fmp12	4:42:08.578
reverting	-	Backup file not found for FILENAME7.fmp12	4:42:08.626
reverting	-	Backup file not found for FILENAME8.fmp12	4:42:08.673
reverting	-	Backup file not found for FILENAME9.fmp12	4:42:08.721
reverting	-	Backup file not found for FILENAME10.fmp12	4:42:08.768
reverting	-	Backup file not found for FILENAME11.fmp12	4:42:08.818
reverting	-	Backup file not found for FILENAME12.fmp12	4:42:08.864
reverting	-	Backup file not found for FILENAME13.fmp12	4:42:08.912
reverting	-	Backup file not found for FILENAME14.fmp12	4:42:08.959
reverting	-	All files reinstalled successfully	4:42:09.006
reverting	-	Opening files	4:42:09.054
opening	-	Starting to open files	4:42:13.425
opening	-	Files opened successfully	4:42:50.569
reverting	-	Reverted files opened successfully	4:42:50.618
post-deployment steps	-	Just in time build deleted from source server outbox	4:42:50.838
done	-	Deployment process failed. Original files are unmodified.

Note file names hidden to protect client info.

2

Are you self hosting this in AWS? Or is this on a hosted platform, out of interest?

Is this a virtualised environment, and if so, are you performing snapshots?

3

If you have an antivirus software that is checking the FMS Database folders they can cause issues like this as well. Essentially there is another program running that is reading your FileMaker file after it is closed by OttoFMS and when OttoFMS tries to read it it cannot because theres another program using it.

-Kyle

4

These are AWS EC2 Windows instances r5a.xlarge self-hosted as a healthcare system.

5

Do you have AWS snapshots enabled? We saw some issues with this, albeit trough a 3rd party hosting provider. From memory they applied some kind of storage device driver update, and we don’t see this any more, but I’m only repeating what I remember from a brief discussion with them. Might be worth investigating?

6

We have confirmed that the OttoFMS folder is on exclusion list from Windows Antivirus and the other security software installed on the machine. Also confirmed that no EC2 snapshots were running during the release.

What seems to have worked is ensuring we close the files manually before doing the release. My guess is that due to the size of the files, and it taking more than 10s to close, it is leaving one open or causing the failure.