I have found that opening up a browser on the server and copy the URL from the CRON file into the address to help in trouble shooting. You have probably tried this.

 

Without seeing the entry in the CRON file we are just shootin’ in the dark ;-)

 

Ben Johansen - http://www.pcforge.com
Authorized Witango Reseller
http://www.pcforge.com/WitangoGoodies.htm 
Latest downloads & List Archives @
http://www.witango.ws

-----Original Message-----
From: Jon van der Raadt [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 05, 2003 8:49 AM
To: witango.com witango talk
Subject: Witango-Talk: crontab

 

Does anyone have any ideas why our crontab no longer works? We were using it successfully with t2k but since upgrading to the version 5 server we get the following in the log:

03/02/2003 16:04:13 0 [Cron] Failed
http://(null):(null)/Time/timeditems.taf?f=PhaseComplete

Where do the nulls come from? If I substitute the port, I get

03/02/2003 16:04:13 0 [Cron] Failed
http://(null):80/Time/timeditems.taf?f=PhaseComplete

This is the same if we use
localhost
127.0.0.1
192.168.1.6 (ip address of the machine)

This is a serious suituation as our application relies heavily on timed processing...

Jon
---
Jon van der Raadt

TeamOnly
Web Solutions

412, Alastair Ross Technology Centre
3553 - 31 Street NW
Calgary, Alberta Canada T2L 2K7

http://www.teamonly.net


Office: (403) 286-5586
Fax: (403) 286-5576

Cell: (403) 863-6304
Email: [EMAIL PROTECTED]

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to