Unable to upgrade from 1.4.4 to 2.0

[dclsystems]

Hello, when we run the update shell script it shows the following:


===========================
Nagios Log Server 2 Upgrade
===========================

Upgrading to version 2 requires active maintenance on your license. Please double check before upgrading.

Once upgraded, the Log Server interface will not be usable until you have activated. You can activate do this directly in
the interface after upgrade.

You will need the following information to activate:

- Log Server license key
- Account ID or Token


Then it exits. We have confirmed with sales that our support benefits was renewed recently. Can you advise us how to solve this problem?
Thank you.

[kyang]

If you have renewed support benefits, then you should activate your Nagios Log Server in the interface.

Are you able to get to the Log Server interface?

You should be able to activate it when going to Log Server home page --> Admin --> under General click License Information.

Enter the license key there.

Let us know if this helps!

[tjloftin]

I'm getting the same thing...we just purchased a month ago.....what was the resolution.....our license key is valid.

[dclsystems]

We ended up opening a support ticket.
They weren't sure why but they sent us a custom upgrade.sh file, looks like it they just commented out that check so it doesnt exit. That worked for us.

[cdienger]

The script appears to be bailing after the following code in the upgrade script:

Code: Select all

    fmt -s -w $(tput cols) <<-EOF

#===========================
#Nagios Log Server 2 Upgrade
#===========================

#Once upgraded, the Log Server interface will not be usable until you have activated. You can activate do this directly in the interface after upgrade.

#You will need the following information to activate:

#- Log Server license key
#- Account ID or Token

EOF

Commenting it out allows it to go directly to the "Do you want to continue" prompt. It's not clear right now as to why it seems to be bailing after the fmt section, but we're looking into it. I've attached a modified script commenting it out in case anyone else runs into this problem.