ottoFMS normally completes migration on this particular server in less than 5 minutes. Now it gets to “building file 4 of 4” and get’s stuck. I’ve updated both Deploy and ottoFMS and there is no change to behavior.
Hi Rob,
I would start by checking the logs. Both servers have extensive logs you can view with the log viewer. You can also get the debug info for the deployment. That combines all the logs together, making it easier to see everything in one place.
Next I would consider building ahead of time. You can configure a build, then run it. Then you can use that build as the source for your deployment. This helps to break apart the problem into smaller discrete steps.
Todd
OK. While I review the logs–that has a boatload of questions I’m not going to burden you with…but help me understand builds. As configured, I am using JIT builds because this is an automated deployment process. This client receives their new build every Wednesday for work completed through the week on the days in between.
Normally, this works flawlessly–then it bonks inexplicably. “Back to the logs.” I have to restart Ottos since trying to manually push on demand results in “Build already in process.”
Yesterday’s log failure was "UnauthroizedError: Invalid session token- {“service”:“express-error-handler”}. I have no idea what that means. But that was the automated one running in the middle of the night.
When I attempted to re-push it manually yesterday it would start and then just hang. I guess in those instances, I could run the build first–but I’ve never done that before.
OH dang! Update. I just checked the source server and clicked on the Builds tab and I have 4 jit builds that are in status “zipping.” One from 3:00 AM, 6:56 AM, 7:31 AM, and 8:15 AM yesterday.
Bingo!
So, now–why?
I’ll restart this instance and looks like I"m 1 v behind on 4.10.3.
Hi Rob,
You can automate the entire process even if you separate it into builds ahead of time.
The build logs should have some info about the zipping starting and stopping. If you want to send us those debug logs we can take a look.
Todd