If your interworx license is coming up as invalid, do this:
Contents |
Make sure the clock is synchronized correctly
service ntpd stop ntpdate tick.usno.navy.mil service ntpd start
Edit the file /etc/ntp.conf Zoom down to where it says server 127.127.1.1 and change it to server tick.usno.navy.mil
The IP is 192.5.41.40 in case the server is DNSless.
Then run this command:
~iworx/cron/license.pex --sync
After fixing ntp, add this command to set the correct date in BIOS:
# hwclock --systohc
Check the log files
Sometimes the invalid license in interworx is caused by log files. If you try synchronizing the license and you get this error:
[root@server9 root]# /home/interworx/cron/license.pex --sync File size limit exceeded
Generally, if the sync runs, there is no message at all. A file limit exceeded error usually means a log file is full. Check /var/logs first for any logs 2GB or larger.
[root@server9 log]# ls -lh total 2.1G -rw------- 1 iworx iworx 9.5M Feb 2 14:44 access.log -rw------- 1 iworx iworx 0 Jan 16 2004 access.log.1 -rw------- 1 iworx iworx 11M Feb 2 07:50 error.log -rw------- 1 iworx iworx 8.2K Jan 16 2004 error.log.1 -rw-r--r-- 1 iworx iworx 22K Feb 2 07:44 horde.log -rw------- 1 iworx iworx 1.6M Jan 22 2004 iworx-65.110.53.100.log.gz -rw------- 1 root root 2.0G Jan 31 04:28 iworx.log -rw------- 1 iworx iworx 514 Jan 16 2004 iworx.log.1 -rw------- 1 iworx iworx 7.6K Oct 15 18:59 mysqld.log -rw------- 1 iworx iworx 658 Jan 16 2004 mysqld.log.1 [root@server9 log]# pwd /home/interworx/var/log
This is the next place you check. As you can see above, the iworx log is 2GB, the limit of ext file systems.
[root@server9 log]# mv iworx.log iworx.log_old [root@server9 log]# touch iworx.log [root@server9 log]#
[root@server9 log]# /home/interworx/cron/license.pex --sync [root@server9 log]# ^^^^^^^^^
No errors, that's good.
You could safely remove the file if you'd like, but since this isn't my server I'd rather not do that.
Check the License Key in the INI file
- Attempt to restart the iworx service and see if it restarts successfully. If it gives a license error, continue on.
- Check the iworx log file
tail /home/interworx/var/log/iworx.log
- See if it reads that the license key is not active. If it is not active, contine. If it is active, this section will not fix your issues.
- Pull up the iworx.ini, usually located in /usr/local/interworx/iworx.ini
vi /usr/local/interworx/iworx.ini
- Search for SAGO, which is contained in the license key
- Pull up the Provisioning Report for the server and check the "InterWorx-CP License Key:" field.
- If they do NOT match, change the INI file to match what is shown in the provisioning report.
- Save and exit the INI file
- Sync the server with Interworx
~iworx/cron/license.pex --sync
- Restart the iworx service
Check the Disk Usage
Check and see if the partition that iworx runs in is full. If it is, you can receive a license error (odd but true.)
