Monitoring, Management & Location Tracking

***QUESTION***
My upgrade is failing as follows:

ALTER TABLE 
SET 
SET 
make[2]: *** [postgresql] Hangup 
make[1]: *** [src_install] Hangup 
make: *** [upgrade] Hangup 



What does this mean? 

How do I proceed?


***SOLUTION***

This meassage is usually generated when an SSH session terminates while the upgrade is still in progress.

To complete the upgrade process run the following commands:

# root (alias for: cd /root/svn/mercury)

# make


If the upgrade fails again and if you are seeing something like this:

DB::Q->scalar must return exactly one value: got 0 rows, N/A cols at Mercury/Utility/Assert.pm line 45 
3 ( Mercury/DB/Q.pm:55) ASSERT 
2 (Mercury/MigrateDB/CheckInterfaceUIDs.pm:16) Mercury::DB::Q::scalar('Mercury::DB::Q', 'select version from seas_config') 
1 ( -e: 1) Mercury::MigrateDB::CheckInterfaceUIDs::check('Mercury::MigrateDB::CheckInterfaceUIDs') 

make: *** [check_interface_uids] Error 2


...see below for further steps. If you are not seeing the message above, try running the make command again:

# make

If the upgrade still does not complete successfully, please contact Support.

----------------------------------------
make: *** [check_interface_uids] Error 2
----------------------------------------

If you were upgrading from 6.x to 7.0 continue... If not, please contact Support. 

The likely cause of this message is:
- During the upgrade process AMP updated the version number in the database;
- The data has not been fully upgraded from the previous version
- when you try to upgrade again AMP runs a check that is not valid for the version you are upgrading from

First, you will need to reset the version in the database to a pre-7.0 version. (IT DOES NOT matter what version you were actually on.)

# dbc "update seas_config set version='6.4.1';"

Then run the make command again:

# make

If the upgrade still does not complete successfully, please contact Support.