Trouble with Rewalk Schedule

jay.upchurch · Post by **jay.upchurch** » Mon Apr 15, 2002 1:48 pm

I have a profile that has been set up for about a month. I manually ran a walk or two while figuring out the exact profile attributes. After determing the exact bells and whistles required for the profile, I set up the rewalk schedule to run daily at 1:00am. I set this up last week. To date, it has not run. Any ideas?

Post by **mark** » Mon Apr 15, 2002 2:21 pm

Did you get a confirmation message from the gui saying the schedule was set when you updated the schedule?
Does the walk status indicate anything good, bad, or otherwise?
Does "texis -LS" show the schedule?

See also other threads on this board about scheduling. Here's one:
http://thunderstone.master.com/texis/ma ... =3be3163f3

jay.upchurch · Post by **jay.upchurch** » Mon Apr 15, 2002 2:48 pm

I did get a confirmation message from the GUI saying the schedule was set when I updated the profile. In fact, the values are still there when I go into the admin area and view the "All Walk Settings".

The walk status indicates "Last complete walk: 2002-04-11 11:23:42".

And when I run "texis -LS", I see:
Schedule: daily at 1
Next run: 2002-04-16 01:00 (in 10h 27m)
Last run: 2002-04-15 01:00 (13h 32m ago) took 21 sec
First run: 2002-04-11 01:00 (4d 13h ago)
Status: runnable, 5 executions, first last, id 3cb47004e

So it looks like from this last perspective as if it is running. But I do not receive any confirmation emails tellling me the walk was executed. Nor does the walk status get updated.

Does there have to be an addition or removal of a page to the index db during a walk in order to send out a confirmation email or update the walk status?

Post by **mark** » Mon Apr 15, 2002 3:21 pm

Click "Walk Status" from the webinator's main menu on the left to get the detailed status. Scroll to the bottom to see the last thing reported. If there's nothing indicative there check the vortex.log and monitor.log files for errors.

jay.upchurch · Post by **jay.upchurch** » Mon Apr 15, 2002 3:34 pm

The "Walk Status" looks ok. At the bottom of the page I see an end of report message.

I also looked at the vortex.log file. There has not been any new entries to this log since March 25th.

I also looked at the monitor.log file. The only errors I see mention "timeout sending data to ls.thunderstone.com:80" and "Unable to remove semaphore: Invalid argument in the function Clear semaphore". Should I be worried about either of these?

I confused with your last posting. It looked like I reported conflicting reports. The first two indicated a last walk on 04/11, but the "texis -LS" indicated a walk on 04/15. Any reason for that?

Post by **mark** » Mon Apr 15, 2002 4:43 pm

The messages in monitor.log are probably innocuous unless there's some rogue process deleting semaphores at random.

The texis scheduler is a general purpose function. It can run any vortex script. Webinator uses it to perform periodic rewalks. The scheduler is saying it ran Webinator (dowalk) on schedule. But Webinator doesn't appear to be doing anything when the scheduler runs it. The status messages will only change if Webinator runs far enough to update those files, which it apparently is not doing.

Are you set for a "new" or "refresh" walk?

Check to ensure that you texis monitor is running as the same user that texis runs as when run from the web interface.

Try adding some debug prints to the beginning of the dispatch function of dowalk to see if it's getting that far:
<write append /tmp/dowalk.debug>
<fmt "dispatch %s called for profile %s at %t\n" $what $profile now>
</write>
Then check /tmp/dowalk.debug after a run. You might set your schedule to something more frequent for now.

jay.upchurch · Post by **jay.upchurch** » Mon Apr 15, 2002 4:48 pm

Its a new walk.

Would it be easier just to set up a cron job to execute the walk instead of using the scheduler?

Post by **mark** » Mon Apr 15, 2002 6:01 pm

cron should work with the same command you would use to run the walk by hand from the command line. See the manual for how to run the walk by hand.

It would still be interesting to know where the problem is on your system as it does work on all the ones we've tested as well as other people's sites.

jay.upchurch · Post by **jay.upchurch** » Mon Apr 15, 2002 6:03 pm

What information can I provide you to help determine the problem?

Post by **mark** » Tue Apr 16, 2002 9:59 am

See message 6. What's in dowalk.debug after a scheduled run?
You might also add
<exec nobr /usr/bin/id></exec>$ret
right after the <fmt ...> that's being written to dowalk.debug to confirm the user it's running as.