Scheduled Refresh

hess · Post by **hess** » Wed Jan 09, 2002 1:39 pm

Hi-
I'm using the freeware version of Webinator 4 on a RedHat Linux 7.2 box. I've had no troubles with walking the site and accessing the database. I've tried to set up a scheduled refresh, but it doesn't seem to be working. I've tried both an "on change" refresh and a timed refresh, but neither seem to be working. Any ideas?

Thanks!
Tara

Post by **mark** » Wed Jan 09, 2002 1:49 pm

We'll need more details.
In what way is it not working? Never happens, gets errors, ??
What Frequency and Hour are you using?
When you click "Update" to set the schedule it should say at the top of the page, in a gray box, what it did. Do you get any errors there? Does it say it set the schedule?
Are you using more than one scheduled walk on that machine? (Webinator 4 currently only supports one scheduled walk at time).
Check your "Walk Status" page and the "vortex.log" file in the texis subdirectory of your installation directory.

hess · Post by **hess** » Wed Jan 09, 2002 2:04 pm

Thanks for your reply. In answer to your questions:

*The refresh never happens unless you go into the administration section and run it manually (i.e. by clicking on the "go").
*I started out using the "on change" option using a webpage I knew changed frequently. I then switched to an hourly refresh option.
*When I click the "update" button after setting the schedule I get no gray box at the top of the page. I get no errors, either.
*We are using webinator to walk only one site - so there are no other scheduled walks on the machine.
*The "Walk Status" page gives the date and time of the last refresh that was run manually.
*The vortex.log file is filled with hourly errors -
002 Jan 9 12:45:00 /installtest: Can't open source file /web/WWW/docs/installtest: No such file or directory
002 Jan 9 13:45:00 /installtest: Can't open source file /web/WWW/docs/installtest: No such file or directory
And so on and so on. What is it looking for here?

Thanks again for your help!!!
-Tara

Post by **mark** » Wed Jan 09, 2002 2:58 pm

It looks like maybe some other script has somehow been scheduled for hourly execution. Run
texis -LS
to get a dump of what's scheduled. Run
texis -wipesched
to clear all schedules.

Check vortex.log after attempting to set a schedule to see if there are any errors reported then.