Can not find outputInfo.json file

[Joseallencali]

When I finished launching the orbit chain, an outputInfo.json file was printed according to step 4 in the readme, but it was not found. There were a few errors along the way, but I have resolved them and completed the startup of the chain.

Is there a problem with my procedure? Is my L3 chain deployed successfully?

[hbksagar]

I am also stuck at the same issue from last few days. This might be due to fact that Bridge transaction (i.e. Deployment TX: 0x8c28... in your case) though executed its partially failing due to which its not going to the next step.
I tried skipping the step but its no help as it fails in step 7 while transferring ownership.

Did you manage to find any solution? @Joseallencali

P.S: I have updated the orbit-setup-script to latest commit (f9ce0cc) and I am running a AnyTrust based Orbit chain.

Adding @Jason-W123 for help

[Jason-W123]

This issue is because you are in an old commit which has some bugs, but we already fixed it in this pr, we recommend the easiest way to solve this is pull the latest commit, create a fresh rollups in this website then re-execute it.

[hbksagar]

Hey @Jason-W123, I am on the latest commit f9ce0cc. I am getting the same error.

[Jason-W123]

I know, I mean could you re-create a new rollup and re-deploy this? This is the easiest way to solve it

[hbksagar]

I pulled the latest commit hash with nginx setup and deployed from the sratch. Again stuck at the same step
Retryable ticket (ID 0x445799.......) status: FUNDS_DEPOSITED_ON_L2. In case you need more details do let me know. Happy to share.

[Jason-W123]

We know if you first run the old version script failed, then second run will fail into this error. This is because some reason about the retryable ticket, so the easiest way is you can re-create a new rollup from here, then copy the new rollup info into the script and then re-run.

[hbksagar]

We know if you first run the old version script failed, then second run will fail into this error. This is because some reason about the retryable ticket, so the easiest way is you can re-create a new rollup from here, then copy the new rollup info into the script and then re-run.

Hey @Jason-W123, I have deployed a new Rollup with updated codebase and updated config files from the Scratch. And I still got the same error. I tried in my mac (Which didn't work for me because of db dependency) so I deployed it on AWS with Ubuntu. I am still getting the same error. I will try to deploy with different owner address now. I will let you know the update.

Meanwhile, sharing the error on mac

ERROR: Cannot extend service 'db' in ./orbit-setup-script/docker-compose/services/db.yml: services with 'depends_on' cannot be extended

[Jason-W123]

Which docker-compose version are you using?

[hbksagar]

Which docker-compose version are you using?

It was docker-compose version 1.29.2, build 5becea4c on mac and that seems to be the problem. Since this is unrelated to this issue I will close this.

meanwhile, I was able to create the orbit instance with new EOA account in first attempt. I will check once again with the old EOA account and update. Thank you for the help and Guidance @Jason-W123