Reset Search
 

 

Article

Extreme Control Postgres Database Does Not Start After BIN-based Upgrade

« Go Back

Information

 
TitleExtreme Control Postgres Database Does Not Start After BIN-based Upgrade
Symptoms
  • Authentications to one or more upgraded Extreme Control appliances fail.
  • The Extreme Control appliance upgrade using the BIN nac_appliance upgrade image may appear to complete successfully, however upon restart of the appliance the /var/log/tag.log may indicate that the database "could not complete schema update" with the primary failure "Connection refused."
  • /var/log/tag.log indicates the following during startup:
2019-10-14 08:14:53,498 INFO  [com.enterasys.tesNb.server.NACInfoLogger] (main:) Starting NAC Engine version: 8.3.1.9 on IP: 192.168.1.194
2019-10-14 08:14:53,537 INFO  [com.enterasys.tesNb.server.NACInfoLogger] (main:) Disabling TSO for all interfaces on Virtual Machine NAC: IA_V
2019-10-14 08:14:54,433 INFO  [com.enterasys.tesNb.server.NACInfoLogger] (main:) Checking for database updates...
2019-10-14 08:14:54,570 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (main:) could not complete schema update
org.apache.commons.dbcp.DbcpException: org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
       at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:101)
       at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:184)
       at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(Unknown Source)
       at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:110)
Environment
  • Extreme Control (NAC)
  • Software Release 8.1.x, 8.2.x, 8.3.x
  • BIN upgrade
Cause
The upgrade script does not properly upgrade nor remove the prior postgresql package leading to a conflict on restart.
Resolution
This issue is resolved in the upgrade script starting with Extreme Control 8.4.0.

For prior releases two workarounds are available:
  • Re-attempt the BIN upgrade on the same appliance a second time. During this additional upgrade the scripts will correctly purge the prior database packages.
  • Install a fresh NAC virtual appliance, re-IP and re-Enforce via Extreme Management Center.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255