Follow us on Twitter...
Stay up to date with the latest news, special offers and advice from CensorNet on Twitter... we are Tweeting regularly!
This article explains the probable reasons, and the means of solving the problem of repeated license failures.
If you have been running your CensorNet fine and the license failed once, you may well have contacted Technical Support in order to resolve the problem.
If you suddenly find it has happened again, or repeatedly fails, you might need to contact them again - or you may be able to resolve the problem yourself by following the instructions in this article.
We have identified a problem, on some hardware, to successfully communicate with the real time clock (rtc) chip. In this case, the clock gets hopelessly out of sync and eventually the License Manager deems the license to be invalid.
Log into the CensorNet's command line as root and type
hwclock --show
If you receive an error saying
select() to /dev/rtc to wait for clock tick timed out
you have identified that your hardware does suffer from this problem.
To fix it run these commands
date 'the current local time now'
(The above command should not be typed literally, click on this link to see how to set the date/time.)
hwclock --systohc --directisa
/usr/lib/cnv4/update_config /etc/init.d/hwclock.sh HWCLOCKPARS=--directisa
The first command sets the date and time. The second writes this to the BIOS clock. The third updates the system initialisation script to work around the hardware issue.
Once you have completed these steps, reboot the CensorNet by typing
reboot
Once the machine has rebooted, check that the time is correct, either by going to System->Configuration->Timezone on the web interface, or by typing
date
at the command line.
So long as it does show the correct time, you should have no further problems with repeated license failures.