Branching a master module fails | Voters

Branching a master module fails

complete

Antoine Adam

Branching a master module to dev sometimes fails. From the logs it seems to be an issue related to improper directory path generation and thus an incorrect path is passed to the system script handling file movement.

Created by David Wollesen

October 19, 2022

David Wollesen

marked this post as

complete

David Wollesen

marked this post as

in progress

Beta 6 features a completely re-engineered backend that solves all issues related to file handling, including this bug.

We're looking forward to offering a smooth onboarding :)

David Wollesen

Thank you for your report Jeroen Aarts! I have merged your report to a similar bug, although I see that your case is not related to the dev server being accessed over IP.

To see more in-depth logs you can open the Runner window and choose Operations from the sidebar. Then, choose an operation and enable detailed view by clicking the spanner in the upper right corner.

Other things to consider:

The master file gets backed up to a dated backup folder and then it should be moved to the DEVELOP folder.

Do you see the file in the backup folder?
How large is the file? If it is a large file, maybe the backup operation takes too long for the operation to timeout?
If the backup exists, can you copy it manually or do you get any permission issue or message saying that the file is still in use?

Jeroen Aarts

David Wollesen: Yes the backup is created. I have a larger and a smaller file. The smallest file (please refer to the the picture attached) is only 268 Kb. I have attached also a screenshot of the log in the runner window. 
The project name is 'Companies'. The module name is 'Contacts'. Please refer to the screenshots, the file is aligned with the naming conventions. Please note that the server has an additional database folder set up, but also creating a Companies_DEVELOP subfolder in the other folder does not solve the issue.
I can manually copy the backup file and paste it into the Companies_DEVELOP folder.

David Wollesen

Jeroen Aarts: Thanks for the detailed descriptions! I have just blurred the lines with your admin credentials from the screen shot. Beware that important info is shown in the logs :) And yes, Devin currently only works with both the default Database and Backup folders, however, if you would like to change this, you can manually edit the paths in the scripts that was installed during installation in the Scripts folder.

To solve this issue, I have a few things in mind that you could try:

Verify that all necessary Admin API params are being generated:
Click the first
TRACE
log line from your screen shot to show all info (There should be 5, fitting these paths:
move C:\Program Files\FileMaker\FileMaker Server\Data\Backups\"%1"\Databases\"%2"\"%3".fmp12" "C:\Program Files\FileMaker\FileMaker Server\Data\Databases\"%4"\"%5".fmp12"
)
Verify that the Admin API integration works:
Check whether the 5 params are shown as params in the Admin Console if you open up the schedule
DEVIN_fmdbBackupMove
. It will show the most recent params passed to the script.
Check FMS/System logs:
Check for any errors in the
Access
,
Events
or
fmdapi
logs for when the
BRANCH
operation was performed. Two system scripts are being called;
DEVIN_fmdbBackup
and
DEVIN_fmdbBackupMove
, which is the one failing). The latter should give us an answer.
Add wait time to the script moving the file:
In case the
DEVIN_fmdbBackupMove
script fails because the backed up file is still run by fms (either still part of the backup execution or part of
DEVIN_fmdbBackup script
, try to insert a sleep time in the
DEVIN_fmdbBackupMove
script before the move (for instance:
timeout 5
). This will wait 5 seconds before moving the file after it has been backed up.
Run system script manually from command-line to see errors:
If none of the above gives any clues, try to run the
DEVIN_fmdbBackupMove
script manually from the command-line with the 5 generated params and see if you get any errors.

Last question: If you move the file manually to the

DEVELOP

folder, are you then able to work with it in the Devin Workspace?

Jeroen Aarts

David Wollesen: 
Precisely because I suspected issues with non default paths, I only use the standard FileMaker Data path (in Program files).
Feedback:
Image 1: details of the TRACE you mentions
Image 2: Parameters to script schedule in the FMS Admin Console. Note that there is a space in it.
Image 3: Output when running the DEVIN_fmdbBackupMove.bat script from the command line, with the parameter copy/pated from the Admin Console (see above). 
Image 4: Location of the master databases
Image 5: Shows that there is a Companies_DEVELOP folder inside the default Databases location.
It appears that something goes wrong with the construction of the path of the backup file.

David Wollesen

Jeroen Aarts: Thanks! Appreciate it.
The space is intended, and is the only way we can pass multiple params to the Admin API. However, the time is supposed to be appended the _
 which I see it is not, and that seems to be the issue.
While we solve the issue, you can actually just manually make a copy of your master file and put it in the DEVELOP
 folder. 
rename it to Companies_DEVELOP_Companies_v1-0-X.fmp12
 (X being > 1)
open the project workspace
refresh the project from the activity viewer, and then you should see it on the dev branch :)
If you have the time I would appreciate one last thing: 
Can you try to find the last DEBUG line saying "Admin API Returned", click it, and then find the osScriptParam
 values for the script DEVIN_fmdbBackupMove
 as in this screen shot?

Jeroen Aarts

David Wollesen:

OK thanks. I manually copied and renamed the file and now I have the branch. Please refer to the screenshot to show the output from the last DEBUG line for 'Admin API Returned'.

David Wollesen

Jeroen Aarts: Thanks, it is indeed the time that is not being generated!

David Wollesen

Merged in a post:

Module branching fails

Jeroen Aarts

Install on dev server FMS 19.6 on Win2019. I am not able to branch a module. See output of Activity log. It appeared to me that there could be an issue with the OS password (in the logs it appeared that the fms admin pw was used) so I changed so that both passwords are the same. I also set security for the DEVELOP subfolder so that any user could write. It appears that the file copy fails? Are there any additional logs I can look into?

February 23, 2023

David Wollesen

marked this post as

planned

Seems to only affect installations where the Devin Engine connection is established over an IP address, and not for domain names using SSL.