Upgrading Version 0 to 1
Version 1 has a lot of changes from version 0.
Although you should be able to upgrade using the standard process please make doubly sure you have backed up your database first if possible.
The upgrade process may take a considerable time to run.
The tests for example are now handled mostly via plug-in modules and the code may no longer work correctly in your environment.
The main tester scripts are no longer .sh but .php files (.sh files are still included and should still work ok) and it is recommended that you update your scheduler to run via
The system can also now accommodate variable test timings and you should update your scheduler to run the main test script every minute (nodes are by default set to run at five-minute intervals so should run at the same frequency as before until you change them if you wish) - Virtual Appliance users see below.
Following upgrade to version 1 you are advised to run the test script manually to have a look at the output and make sure no tests are failing to be run or errors are displayed.
Virtual Appliance Users
The Virtual Appliance (up to and including 3.3b) is setup for five minute test intervals. If you want to use shorter test periods then you must either apply the patch (below) or... upgrade to 1.x, backup your config, download a newer virtual appliance and restore your config onto it.
Virtual Appliance Patch
If you are using the Virtual Appliance up to and including 3.3b and you want to use variable test intervals below five minutes then you must apply a patch as follows:
This patch only applies to VM 3.3b or earlier users wishing to run FreeNATS version 1 - not version 0 users!
Login to the console as root and do the following commands
cd /tmp wget http://www.purplepixie.org/freenats/patch/vm/280708/crontab
You should see the file download at this point
mv /etc/crontab /etc/crontab.old mv crontab /etc/crontab /etc/rc.d/init.d/crond stop
You should see an OK message
You should see a FAILED message
You should see an OK message and cron is now running at minute intervals
By default all your nodes will have five minute test cycles set (and all the tests zero minutes meaning they run every time the node is tested).