ROOT folder being recreated every time we run updates

Mike Ryan shared this problem 7 years ago

Hi there,

Our current process for when we run updates is this:

Please note we have renamed "ROOT" in webapps to "eaglebi"

1. Stop Yellowfin service

2. Copy folder "eaglebi" into same directory (i.e. "eaglebi - copy")

3. Rename "eaglebi - copy" to "ROOT"

4. Run Yellowfin update

5. Copy entire contents from "ROOT" to "eaglebi"

6. Delete "ROOT"

7. Start Yellowfin service

This seems to be causing a couple of minor issues - in particular, it seems that the updater deletes some files during the process.

These files that should have been deleted remain in the eaglebi directory, because even though they are deleted from the ROOT folder during the update, they are not at any point deleted from eaglebi and obviously copying the contents of ROOT to eaglebi does not do this either.

When we try to run an update without copying "eaglebi" and renaming it "ROOT" (steps 2 and 3 above), the updater creates a "ROOT" folder automatically and seemingly runs the update in that directory.

We have followed the steps in this article (we did this a long time ago when first implementing the software).

We've reconfirmed that it is still correct as per this article.

Are we missing something?

How do we make it so that we can simplify the update process and simply stop the service, run the update, and then restart the service?

Thanks in advance for your help.

Replies (3)


Hi Danielle,

The update process should be like this:

1. Stop the Service

2. Run the updater and point it to the eaglebi folder

after finishing the update

3. Start the Service.

You don't have to rename the folder.

Please let me know if you have any questions on this.




Great, thank you.


Hi Danielle,

I am closing this case, as this has been answered.

The other ticket with defect is still open.

Let me know if you have any questions.



Leave a Comment
Attach a file