Discovery and Bulk Importing
Tester Privileges and "Testing the Tester"
Because it uses low-level socket calls the tester itself usually has to run with root privileges (this is usually a PHP or OS setting). If you want to try and run under different environments you can do so from the command-line using the test/ping.sh and test/test.sh scripts.
ping.sh simply takes a hostname/IP and uses the FreeNATS ping test method. A zero result exactly (with no decimal places shown) indicates the test has failed.
test.sh takes the internal FreeNATS name of a test, the hostname and optionally a parameter for the test. Not everything is available to be checked using this and any tests should at most require the same rights as the ping test so using ping.sh to test is recommended.
You can also run the entire test session in the foreground and view detail as follows...
Running Test Sessions in the Foreground for Debugging
You can run bin/tester.sh with the FreeNATS nodeid as a parameter to run a test session in the foreground (no nodeid will attempt to run all nodes). This will output a large amount of data to the console.
For example: ./tester.sh nodeid
When in the server/bin directory - you can also run the php script directly which does the same thing i.e. php tester.php nodeid
There are some optional switches you can pass to either the .sh or php script in addition to the nodeid (as of 1.21.2):
--forcerun will run the node(s) regardless of (a) the state of FreeNATS suspension, (b) the node already being marked as running, (c) outside of its current schedule --forcetests will (if the node is run) run the tests regardless of the frequency timings i.e. whether or not the node and tests are due to be tested
Note --forcerun is risky as it will ignore the safeguards to have tests running at the same time but --forcetests is safe(er) to use as it just ignores the delays between tests (useful for debugging when you want to see a test run even if its not due).
Can be used in combination.
You can pass through user authentication as documented here.
Getting a Specific VM Version
See this documentation.
Virtual Appliance Maintainance
You should ensure the Virtual Appliance is kept up-to-date via the rPath administration interface (https://THE.IP.ADDR:8003/) especially if it is in a live or exposed environment.