You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am hitting a bug with the license whereby if your current license has expired, then an upgrade (including a new license) causes Octopus to error during the DB upgrade with a license violation message. I am using Azure Automation as the pull server, the compilation of the MOF goes through successfully including the new license, but in the log when the DSC runs through on a new set of servers I get an error (see log) that the license condition has not been met. I think what is happening here is the DB check is run first to get access to our database, then the schema needs upgrading which then gets us a license violation. I can fix this by manually pushing the new license using Octopus.Server license command, and then the DSC runs through ok.
I did also try to set SkipLicenseCheck to $True in the DSC but had the same results.
Our old license expired some time ago and I believe it was updated by someone else using the GUI or a local tool but the existing MOFs in the automation account put it back.
Is there any way we can run the license command before connecting to the DB to cope with such situations in the future?
Thanks.
Andrew.
2019-09-23 12:34:55.4661 3424 1 INFO ================================================================================
2019-09-23 12:34:55.4661 3424 1 INFO Changed log folder from C:\Users[redacted]\AppData\Local\Octopus\Logs to E:\Octopus\Logs
2019-09-23 12:34:57.4348 4172 1 INFO ================================================================================
2019-09-23 12:34:57.4348 4172 1 INFO Changed log folder from C:\Users[redacted]\AppData\Local\Octopus\Logs to E:\Octopus\Logs
2019-09-23 12:34:57.4348 4172 1 INFO Octopus.Server.exe version 2019.6.8 (2019.6.8+Branch.tags-2019.6.8.Sha.2813706b187ebc8c2f63ed14cd888df3dc271563) instance OctopusServer
2019-09-23 12:34:57.4504 4172 1 INFO Environment Information:
OperatingSystem: Microsoft Windows 10.0.14393
OsBitVersion: x64
Is64BitProcess: True
CurrentUser: [redacted]
MachineName: [redacted]
ProcessorCount: 1
CurrentDirectory: C:\windows\system32
TempDirectory: C:\Users[redacted]\AppData\Local\Temp
HostProcessName: Octopus.Server
PID: 4172
2019-09-23 12:34:57.4661 4172 1 INFO Loading plugins from: C:\Program Files\Octopus Deploy\Octopus\BuiltInExtensions
2019-09-23 12:34:57.5286 4172 1 INFO Loading BuiltIn extension: AzureAD (5.5.7.0)
2019-09-23 12:34:57.5602 4172 1 INFO Loading BuiltIn extension: Directory Services (5.6.5.0)
2019-09-23 12:34:57.5754 4172 1 INFO Loading BuiltIn extension: GoogleApps (5.5.7.0)
2019-09-23 12:34:57.5754 4172 1 INFO Loading BuiltIn extension: Guest (1.0.0.0)
2019-09-23 12:34:57.5911 4172 1 INFO Loading BuiltIn extension: Okta (5.5.7.0)
2019-09-23 12:34:57.6067 4172 1 INFO Loading BuiltIn extension: UsernamePassword (0.0.0.0)
2019-09-23 12:34:57.6067 4172 1 INFO Loading BuiltIn extension: GitHub Issue Tracker (1.1.5.0)
2019-09-23 12:34:57.6223 4172 1 INFO Loading BuiltIn extension: Jira Issue Tracker (1.2.4.0)
2019-09-23 12:34:58.4348 4172 1 INFO ==== DatabaseCommand ====
2019-09-23 12:34:58.4511 4172 1 INFO CommandLine: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe database --instance OctopusServer --connectionstring Data Source=[redacted]; Initial Catalog=Octopus; Integrated Security=SSPI;Max Pool Size=200 --create --masterKey ********
2019-09-23 12:34:58.4817 4172 1 INFO Setting master key
2019-09-23 12:34:58.7473 4172 1 INFO Setting database connection string to: data source=[redacted];initial catalog=Octopus;integrated security=SSPI;max pool size=200
2019-09-23 12:34:58.7630 4172 1 INFO ========== SQL Database Connection Details ========
2019-09-23 12:34:58.7630 4172 1 INFO SQL Server: [redacted]
SQL Database: Octopus
Authentication Type: Windows Integrated Security
User: [redacted]
2019-09-23 12:34:58.7786 4172 1 INFO ===================================================
2019-09-23 12:34:58.7786 4172 1 INFO Testing connection to the 'master' database...
2019-09-23 12:34:59.1692 4172 1 INFO Successfully connected to 'master' database!
2019-09-23 12:34:59.2317 4172 1 INFO Database 'Octopus' already exists on SQL Server at '[redacted]', no need to create it.
2019-09-23 12:34:59.7786 4172 1 INFO Checking the Octopus Master Key has been configured.
2019-09-23 12:34:59.8098 4172 1 INFO Making sure it's safe to upgrade the database schema...
2019-09-23 12:34:59.8098 4172 1 INFO Checking to see if database schema upgrade is required...
2019-09-23 12:34:59.9504 4172 1 INFO ====================================================================================
Database schema changes are required. Execution plan:
2019-09-23 12:34:59.9661 4172 1 INFO Ensuring pre-conditions for upgrading the database are satisfied...
2019-09-23 12:35:00.2006 4172 1 INFO Searching for indexes that might upset the database upgrade process...
2019-09-23 12:35:00.2317 4172 1 INFO - PASS: All columns use the default collation.
2019-09-23 12:35:00.2317 4172 1 INFO - FAIL: Your Octopus Server would not be compliant with your license if we allowed the upgrade to continue. Here is the summary of the license check: You are not licensed to run Octopus Server 2019.6.8 which is considered to be part of the 2019.6 feature release. It was released on Monday, 01 July 2019. Your maintenance period ended on Sunday, 24 March 2019 (99 days before this version of Octopus Server was released). You will be prevented from performing certain key actions, like creating and deploying releases. Please visit https://g.octopushq.com/licenseupgrade to renew your license.
2019-09-23 12:35:00.2317 4172 1 INFO - PASS: We've done our best to remove any unexpected database indexes.
2019-09-23 12:35:00.2473 4172 1 FATAL One of the pre-conditions to safely upgrade your database has failed, and the upgrade cannot continue.
PASS: All columns use the default collation.
FAIL: Your Octopus Server would not be compliant with your license if we allowed the upgrade to continue. Here is the summary of the license check: You are not licensed to run Octopus Server 2019.6.8 which is considered to be part of the 2019.6 feature release. It was released on Monday, 01 July 2019. Your maintenance period ended on Sunday, 24 March 2019 (99 days before this version of Octopus Server was released). You will be prevented from performing certain key actions, like creating and deploying releases. Please visit https://g.octopushq.com/licenseupgrade to renew your license.
PASS: We've done our best to remove any unexpected database indexes.
Please take the following steps to get your Octopus Server back up and running:
Step 1: Re-run the installer for the version of Octopus Server you were using just before trying this upgrade. Your data hasn't been changed and everything will go back to how it was beforehand. This will give you time to solve the problem and try the upgrade again.
Step 2: Contact [email protected] with a copy of your Octopus Server log file so we can help you upgrade successfully.
The text was updated successfully, but these errors were encountered:
Hi,
DSC module version: 4.0.713
I am hitting a bug with the license whereby if your current license has expired, then an upgrade (including a new license) causes Octopus to error during the DB upgrade with a license violation message. I am using Azure Automation as the pull server, the compilation of the MOF goes through successfully including the new license, but in the log when the DSC runs through on a new set of servers I get an error (see log) that the license condition has not been met. I think what is happening here is the DB check is run first to get access to our database, then the schema needs upgrading which then gets us a license violation. I can fix this by manually pushing the new license using Octopus.Server license command, and then the DSC runs through ok.
I did also try to set SkipLicenseCheck to $True in the DSC but had the same results.
Our old license expired some time ago and I believe it was updated by someone else using the GUI or a local tool but the existing MOFs in the automation account put it back.
Is there any way we can run the license command before connecting to the DB to cope with such situations in the future?
Thanks.
Andrew.
2019-09-23 12:34:55.4661 3424 1 INFO ================================================================================
2019-09-23 12:34:55.4661 3424 1 INFO Changed log folder from C:\Users[redacted]\AppData\Local\Octopus\Logs to E:\Octopus\Logs
2019-09-23 12:34:57.4348 4172 1 INFO ================================================================================
2019-09-23 12:34:57.4348 4172 1 INFO Changed log folder from C:\Users[redacted]\AppData\Local\Octopus\Logs to E:\Octopus\Logs
2019-09-23 12:34:57.4348 4172 1 INFO Octopus.Server.exe version 2019.6.8 (2019.6.8+Branch.tags-2019.6.8.Sha.2813706b187ebc8c2f63ed14cd888df3dc271563) instance OctopusServer
2019-09-23 12:34:57.4504 4172 1 INFO Environment Information:
OperatingSystem: Microsoft Windows 10.0.14393
OsBitVersion: x64
Is64BitProcess: True
CurrentUser: [redacted]
MachineName: [redacted]
ProcessorCount: 1
CurrentDirectory: C:\windows\system32
TempDirectory: C:\Users[redacted]\AppData\Local\Temp
HostProcessName: Octopus.Server
PID: 4172
2019-09-23 12:34:57.4661 4172 1 INFO Loading plugins from: C:\Program Files\Octopus Deploy\Octopus\BuiltInExtensions
2019-09-23 12:34:57.5286 4172 1 INFO Loading BuiltIn extension: AzureAD (5.5.7.0)
2019-09-23 12:34:57.5602 4172 1 INFO Loading BuiltIn extension: Directory Services (5.6.5.0)
2019-09-23 12:34:57.5754 4172 1 INFO Loading BuiltIn extension: GoogleApps (5.5.7.0)
2019-09-23 12:34:57.5754 4172 1 INFO Loading BuiltIn extension: Guest (1.0.0.0)
2019-09-23 12:34:57.5911 4172 1 INFO Loading BuiltIn extension: Okta (5.5.7.0)
2019-09-23 12:34:57.6067 4172 1 INFO Loading BuiltIn extension: UsernamePassword (0.0.0.0)
2019-09-23 12:34:57.6067 4172 1 INFO Loading BuiltIn extension: GitHub Issue Tracker (1.1.5.0)
2019-09-23 12:34:57.6223 4172 1 INFO Loading BuiltIn extension: Jira Issue Tracker (1.2.4.0)
2019-09-23 12:34:58.4348 4172 1 INFO ==== DatabaseCommand ====
2019-09-23 12:34:58.4511 4172 1 INFO CommandLine: C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe database --instance OctopusServer --connectionstring Data Source=[redacted]; Initial Catalog=Octopus; Integrated Security=SSPI;Max Pool Size=200 --create --masterKey ********
2019-09-23 12:34:58.4817 4172 1 INFO Setting master key
2019-09-23 12:34:58.7473 4172 1 INFO Setting database connection string to: data source=[redacted];initial catalog=Octopus;integrated security=SSPI;max pool size=200
2019-09-23 12:34:58.7630 4172 1 INFO ========== SQL Database Connection Details ========
2019-09-23 12:34:58.7630 4172 1 INFO SQL Server: [redacted]
SQL Database: Octopus
Authentication Type: Windows Integrated Security
User: [redacted]
2019-09-23 12:34:58.7786 4172 1 INFO ===================================================
2019-09-23 12:34:58.7786 4172 1 INFO Testing connection to the 'master' database...
2019-09-23 12:34:59.1692 4172 1 INFO Successfully connected to 'master' database!
2019-09-23 12:34:59.2317 4172 1 INFO Database 'Octopus' already exists on SQL Server at '[redacted]', no need to create it.
2019-09-23 12:34:59.7786 4172 1 INFO Checking the Octopus Master Key has been configured.
2019-09-23 12:34:59.8098 4172 1 INFO Making sure it's safe to upgrade the database schema...
2019-09-23 12:34:59.8098 4172 1 INFO Checking to see if database schema upgrade is required...
2019-09-23 12:34:59.9504 4172 1 INFO ====================================================================================
Database schema changes are required. Execution plan:
Planned pre-upgrade scripts (non-transactional):
Planned schema upgrade scripts (single transaction for all scripts):
Planned post-upgrade scripts (non-transactional):
2019-09-23 12:34:59.9661 4172 1 INFO Ensuring pre-conditions for upgrading the database are satisfied...
2019-09-23 12:35:00.2006 4172 1 INFO Searching for indexes that might upset the database upgrade process...
2019-09-23 12:35:00.2317 4172 1 INFO - PASS: All columns use the default collation.
2019-09-23 12:35:00.2317 4172 1 INFO - FAIL: Your Octopus Server would not be compliant with your license if we allowed the upgrade to continue. Here is the summary of the license check: You are not licensed to run Octopus Server 2019.6.8 which is considered to be part of the 2019.6 feature release. It was released on Monday, 01 July 2019. Your maintenance period ended on Sunday, 24 March 2019 (99 days before this version of Octopus Server was released). You will be prevented from performing certain key actions, like creating and deploying releases. Please visit https://g.octopushq.com/licenseupgrade to renew your license.
2019-09-23 12:35:00.2317 4172 1 INFO - PASS: We've done our best to remove any unexpected database indexes.
2019-09-23 12:35:00.2473 4172 1 FATAL One of the pre-conditions to safely upgrade your database has failed, and the upgrade cannot continue.
Please take the following steps to get your Octopus Server back up and running:
Step 1: Re-run the installer for the version of Octopus Server you were using just before trying this upgrade. Your data hasn't been changed and everything will go back to how it was beforehand. This will give you time to solve the problem and try the upgrade again.
Step 2: Contact [email protected] with a copy of your Octopus Server log file so we can help you upgrade successfully.
The text was updated successfully, but these errors were encountered: