Typically in the past when I would view the Detailed Log for a deployment, I would see the DMT’s verbose logging and info for each table. Recently, I’ve seen more an more of my deployments are only showing a summary of the migration, without any of the detail. Is this something that has change in OttoFMS, or a change in the DMT itself? Or am I just missing something very obvious, and need more caffiene?
Hey Josh,
Is this during a running deployment or after the deployment is done? Both should have an option to see the full detailed log. For the running deployment there is a switch at the bottom of the page, for the finished deployment there is another tab which shows the detailed log. Do you have a screenshot of the page you’re looking at?
-Kyle
This is both during the deployment and when looking at the detailed log post-migration.
- While looking at the live log with the “full detailed log” option on. I see “Started” for ~5 mins, then the summary of the migration once it completes.
- Attached is a screenshot of the detailed log screen.
- This same deployment showed the verbose log back in September, but not in October or November. ( we do this migration less often than other ).
- This same deployment showed the verbose log back in September, but not in October or November. ( we do this migration less often than other ).
Here is the screenshot from the September deployment.
Well that is strange. Which operating system and version of FMS are you running?
-Kyle
This particular server:
Ubuntu 22.04.4
FileMaker Server 20.3.2
I don’t think we’ve changed anything about the arguments we passed to the DMT in any versions recently, did you upgrade FileMaker versions between those deployments? its possible they’re logging out of the DMT differently.
-Kyle
Is it just one of your servers or are there multiple where you’re seeing this?
-Kyle
The only thing updated between those 2 migrations is the version of OttoFMS.
The other servers for this client, have not been showing the verbose log for a lot longer.
This particular server, though, is the one that I told you was getting the OttoFMS folder accidentally deleted as part of another cron job running on that server. I stopped that process. That makes me start to wonder if this is a permissions issue some where… but you may know where to look at quicker than me.
I’m going to download the files and do a manual migration with both the 20.3.2 DMT and 21.1. I feel like when I did an unrelated manual migration last week ( damaged file stuff ), that I don’t think it gave me the verbose log either. But I think I put the -v switch at the end.
Its funny, we were just looking at this, OttoFMS is not even using the -v flag. The “verbose” log that we’re showing is just the default logs that come out, and the verbose version shows even more on top of that. So i have no idea how you’re not getting any of the interim logs back. It could be an idiosyncrasy of the single FMS deployment, let me know how your testing goes!
-Kyle
Will do. Thank you for the responses. At least I know something is up, and it’s worth digging more.
This seems to be the “issue”, and tracks, recently they moved from using a [Full Access] account to using DMT specific credentials.
For accounts with the Full Access privilege set, provides a detailed report about the data migration process. For accounts with the fmmigration extended privilege, in both normal and verbose modes, the tool provides only a brief report without displaying any information about the schema.
2 Likes
Ah interesting, that would definitely do it. Thanks for the investigation Josh! I can add a callout in the docs where we talk about the migration credentials so this is less surprising in the future.
-Kyle
2 Likes
Feels like we need something like an extended privilege to allow the verbose logging, and not uses a FA account. Feature request, here I come.