What to do if an upgrade did not start

[bianca_vaccarin]

Here is how to check the Upgrade Log for errors if your Upgrade that is scheduled to start, does not.

First thing you need to do is check the Upgrade scheduled job to determine if the Next Action is set to the correct time. Next, you will have to check the Upgrade scheduled job to verify if the System ID is set to None. This will result in the Upgrade Client script include will assign the job to the appropriate node, so do not specify one. Then, verify that the glide.war system properties are set to the correct values. Finally, browse through the Upgrade Log for errors.

This should allow you to determine and trouble shoot why an upgrade did not start. From there, you can remedy the errors and start again.

See Troubleshooting an upgrade that did not start   KB0535198 for more information on what to do if an upgrade did not start.

[Yvonntje]

Hi Bianca,

I wrote a blog regarding upgrades and thought you might be interested in reading:

Upgrading an Instance

Cheers,

Yvonne

[pawan k singh]

Upgrade Jobs runs every 60 minutes, to find out the (.war) file and upgrade the instance, there are two important schedules in the instance to note.

• Check Upgrade Distribution: Runs every 60 minutes to detect a new .war file after an upgrade request.

• Check Database for Upgrade: After a node restart, it checks for a new .war file and updates the database. The upgrade job runs every 60 minutes, not always on the hour.

To Modify Upgrade schedule follow below steps

1. Go to System Scheduler > Scheduled Jobs.

2. Find the Check distribution for possible upgrade job.

3. Check the Next action column to see when the job runs next (e.g., 11:10:00). It will run every hour at 10 minutes past the hour.

Refer this KB for more info : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0743666

Please mark this answer helpful it helped you !

Regards

Pawan K Singh