Typically, the FOP2 package is updated to a new version on a yearly (annual) basis. If it has been over a year since you installed the FOP2 package on your AstLinux system you may want to consider updating to the latest FOP2 version.
If you have not purchased a FOP2 license and are using the “Lite Version” then upgrading is straightforward via the System Tab of the web interface under “Add-On Packages:”, and you can stop reading here. On the other hand, if you have purchased a FOP2 license, upgrading will most likely require you to purchase a new “Annual Software Maintenance” License Upgrade.
If you have a FOP2 license, follow the steps outlined below to make sure FOP2 sees this as an “upgrade” and not a “new install”. The FOP2 license seems to be verified against the MAC-address of the first NIC and your hostname. So be careful on VMs (MAC) or changing your hostname!
Note: AstLinux 1.2.1 or later is required
First, check if there is a newer available version of FOP2 from what is currently installed…
upgrade-package fop2 check
If the response is, “Package 'fop2' is currently the newest available version” then you don't need to upgrade.
Next, make sure your license is valid…
service fop2 test
If the response is something like “Flash Operator Panel 2 - Valid License” you are good to continue with the upgrade.
Alternatively, if the response shows “Invalid license…” See Below: Fixing Invalid FOP2 License
and return back here when the license issue is resolved.
Before you upgrade it is best to first purchase the “Annual Software Maintenance” License Upgrade so you will have the “license upgrade code”, usually sent via email.
Upgrade to the latest available FOP2 version…
upgrade-package fop2 upgrade
You should see something like “Successful package 'fop2' upgrade, 'fop2' is not running.” in response.
Using your newly purchased “upgrade code”, issue the command…
/usr/local/fop2/fop2_server --upgrade
and enter the “upgrade code” from your email when prompted.
Test if the new install looks good…
service fop2 test
If you'll get the error “Could not contact registration server, please try again later.”, try this option (from FAQ):
/usr/local/fop2/fop2_server --upgrade --rp=http
Sometimes the “service fop2 test” command will show you that you need to “reactivate” your license…
/usr/local/fop2/fop2_server --reactivate
Finally, start FOP2 with the newly updated version…
service fop2 init
Tip -> Should there be a problem with the new FOP2 version you may revert to the previous FOP2 version with “upgrade-package fop2 revert”.
Tip -> If you made customizations to the FOP2 files, those file are saved in the “/stat/var/packages/fop2-OLD/” directory tree.
If you have a FOP2 license, you should upgrade using the CLI as managing the license codes require CLI access.
If you have not purchased a FOP2 license and are using the “Lite Version” then click on the System Tab of the web interface, under “Add-On Packages:” select “fop2” and “Upgrade/Install”.
An invalid license could be caused by a few reasons, if all else fails contact FOP2 support (and be sure to remember exactly the output of the service fop2 test command).
First, using your original “serial code” you purchased, try to register…
/usr/local/fop2/fop2_server --register
If you'll get the error “Could not contact registration server, please try again later.”, try this option (from FAQ):
/usr/local/fop2/fop2_server --register --rp=http
If that fails, try to revoke your current license and then re-register…
/usr/local/fop2/fop2_server --revoke /usr/local/fop2/fop2_server --register
If that fails, contact the fine folks at: FOP2
If you have an installation with a license and want to rebuild or move the install to a different drive, a little planning with the following steps will make managing your FOP2 license easier.
Before you rebuild the install…
service fop2 stop /usr/local/fop2/fop2_server --revoke
It then asks for the original registration code, hopefully “succeeded”.
Re-Image your drive, install a fresh FOP2 package via the System tab, then via the CLI…
service fop2 test /usr/local/fop2/fop2_server --register
It will again ask for the original registration code, hopefully “succeeded”.