Troubleshooting upgrades

Common problems and solutions for troubleshooting the Access Gateway upgrade process.

Topics

Upgrading from 2019.2.0

When updating from Access Gateway 2019.2.0, first you must remove the oracle-instantclient18.3-basic package.

To remove the package:

  1. Sign in to Access Gateway Management console.
  2. Select the System menu.
  3. Select Remove Package.
  4. Remove oracle-instantclient18.3-basic .
  5. Return to the System menu and select Update.
  6. Proceed with the update as usual.

Error accessing yum.oag.okta.com

If the Access Gateway yum repository is unreachable, you receive an upgrade error resembling:

Ensure that the repository, yum.oag.okta.com, is reachable from the Access Gateway node being upgraded. You can test access using a variety of commands.

Using the Access Gateway Management console, go to Network, choose d, and then enter yum.oag.okta.com.
For example:

Access Gateway Administration ...
1 - Network
...

Choice: 1 [cr]
Access Gateway Network Setup . . .
1 - Manage network interfaces
. . . 
d - DNS Lookup 
Choice: d [cr]
IP Address/Hostname to lookup: yum.oag.okta.com [cr]
IP Address/Hostname of DNS server: 8.8.8.8 [cr]

Server: 8.8.8.8
Address: 8.8.8.8
Non-authoritative answer:
yum.oag.okta.com	canonical name = yumalb-531408569.us-west-2.elb.amazonaws.com.
Name:	yumalb-531408569.us-west-2.elb.amazonaws.com
Address: 52.35.178.214
Name:	yumalb-531408569.us-west-2.elb.amazonaws.com
Address: 54.68.110.208

Using traceroute ensure that there is a route to yum.oag.okta.com from inside the network hosting Access Gateway.
Note that traceroute isn't able to trace a complete route to yum.oag.okta.com due to limitations of AWS EC2 configuration.
For example:

traceroute yum.oag.okta.com
. . . 
traceroute to yum. . . .amazonaws.com (. . . ), 64 hops max, 52 byte packets
1  10.0.0.1 (10.0.0.1)  5.436 ms  2.345 ms  1.925 ms
2  96.120.70.225 (96.120.70.225)  25.870 ms  11.372 ms  11.922 ms
3  96.110.31.121 (96.110.31.121)  11.035 ms  12.135 ms  11.204 ms
4  be-319-ar01.needham.ma.boston.comcast.net (96.108.47.81)  20.129 ms  13.427 ms  14.012 ms
5  be-32031-cs03.newyork.ny.ibone.comcast.net (96.110.42.9)  22.085 ms
6  be-32021-cs02.newyork.ny.ibone.comcast.net (96.110.42.5)  22.305 ms
. . . 
<ctrl-c>						

Note

Note

The traceroute command is not installed on Access Gateway nodes by default.

Related topics