Thanks Robert for the tips. It's indeed a DNS problem...not crontab.
Thanks! MC At 05:17 AM 8/4/2007, you wrote:
Cron works fine in all versions of 5.5. What you might be seeing is the inability of Witango to get to your website/network/dns service. Try using the internal IP of the website, or assign another mapping like 192.168.1.22:1234 to the website for Witango to use. It very mush depends on your network, firewalls, and permissions of the Witango service to know what the right thing to do is. Robert -----Original Message----- From: MC Tay [mailto:[EMAIL PROTECTED] Sent: Saturday, August 04, 2007 3:19 AM To: [email protected] Cc: [EMAIL PROTECTED] Subject: Witango-Talk: Problem using CRONTABFILE in v5.5.009 Hi: Does anyone has any problem with using CRONTABFILE on WiTango v5.5.009? It worked for me on v5.5.003 and not v5.5.009. In my Witango.ini, I have: CRONTABFILE=C:\\website\\crontab\\testalive.txt In the testalive.txt, I have: 0 0-23 * * * http://www.<my website domain>.com/testalive.taf At the hour when it executes, I got an error in the log as follows: [Cron] Failed http://www.<my website domain>.com:/testalive.taf For some reason, it put a colon : right after the .com. The above scenario works fine on v5.5.003 but failed in v5.5.009. Any idea? Thanks! MC ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
