At around 3PM, my web service on my server stopped.
Now a few minutes later I can’t even access Interworx.
Is there any current network problems, maybe at Sagonet.com?
At around 3PM, my web service on my server stopped.
Now a few minutes later I can’t even access Interworx.
Is there any current network problems, maybe at Sagonet.com?
Yikes, Sagonet.com rebooted my server, and now I get this message:
ERROR #LIC04: the current license is invalid or has expired. Please notify your server administrator if this error persists.
Hi RWF,
For some reason the reboot resulted in the time and date on your server to be totally wrong.
[root@server1 root]# date
Fri Jul 30 22:32:29 EDT 2004
[root@server1 root]#
That was the source of the problem.
Paul
I keep getting an invalid license error too, Except my server IS not being rebooted. Just out of the blue it will do it (Every 11 hours or so). I know typing “~iworx/cron/license.pex --sync” as root will fix this but it keeps happening. How can I help this from not doing this so often?
That’s very odd as the lic checks should run via cron by default and refresh your lic every so often. Can you paste the output of :
cat /var/spool/cron/iworx
in this thead so I can make sure the lic cron is even attempted to be run.
Chris
[root@server1 root]# cat /var/spool/cron/iworx
SHELL=/bin/bash
MAILTO=root
38,43,48,53,58,3,8,13,18,23,28,33 * * * * cd /home/interworx/cron ; ./iworx.pex --fively
39,54,9,24 * * * * cd /home/interworx/cron ; ./iworx.pex --fifteenly
49 * * * * cd /home/interworx/cron ; ./iworx.pex --hourly
30 16,22,4,10 * * * cd /home/interworx/cron ; ./iworx.pex --quad_daily
40 3 * * * cd /home/interworx/cron ; ./iworx.pex --daily
44 8 * * 5 cd /home/interworx/cron ; ./iworx.pex --weekly
38 0 15 * * cd /home/interworx/cron ; ./iworx.pex --monthly
Thanks for the reply quickly.