book
Article ID: KB0094797
calendar_today
Updated On:
Description
The upgrade.log file is generated once the broker is upgraded (for example, upgrading from 5.7.x to 5.8) and started after the entire upgrade process is finished. This means, once the upgrade is done from SF broker Admin UI on the browser, you have to stop the broker's Tomcat server and start it again. Once Tomcat server is started, refresh the browser pointing to Admin UI (URL http://[Broker_HOST]:8080) and click the "After restarting, click here to login" link on the UI. At this point, you will see the upgrade.log file getting generated under the fabric/webapps/livecluster/WEB-INF/log folder.
The upgrade.log file is also generated when one applies a Hotfix (for example, SF 5.7.1 Hotfix 6) on the existing SF broker version (SF 5.7.1). Once the Hotfix is applied and the broker is restarted, this file will be generated under the fabric/webapps/livecluster/WEB-INF/log folder.
Issue/Introduction
At what stage is the upgrade.log file generated