Not scheduled, but running as scheduled

[jamon]

We have a scheduled run starting at a specific time occasionally, but the admin interface shows no such schedule. Rewalk schedule: Frequency: None Hour: None.

Huh?

I haven't figured it out yet, but it may be that the scheduled run is starting on the day after we reboot the machine for some reason. It's not running every day.

We did have it scheduled at one time, but no longer.

Suggestions?

[John]

If you don't want any scheduled walks you can run texis -wipesched which will remove any walks scheduled in texis. Is it possible you scheduled with the Windows scheduler or AT in a boot script so that still gets fired?

[jason112]

Could something else be kicking off a walk (cron or some such)?

you can dump webinator's scheduling data by running the following from your morph3 dir:

bin/tsql -d texis/testdb "SELECT * from SYSSCHEDULE;"

[jamon]

I just did something that I thought was the equivalent of that:

<SCRIPT LANGUAGE=vortex>
<TIMEOUT=-1></TIMEOUT>

<A NAME=main public>
<vxinfo installdir>
<sum "%s" $ret "/texis/">
<$defaultdir=$ret>

<$testdbdir="TestDB">
<sum "%s" $defaultdir $testdbdir>
<$testdb=$ret>

<sql db=$testdb "select id,PATH,SUFFIX,SCHEDULE,NEXTRUN,VARS,OPTIONS from sysschedule">
$id, $PATH, $SUFFIX, $SCHEDULE, $NEXTRUN, $VARS, $OPTIONS
</sql>
</A> <!-- end main -->

</SCRIPT>


and I got this back:

41f11f7f4, d:\pathstuff\dowalk, /dispatch.txt, daily at 11, 2007-02-02 11:00:00, profile=WMCPress&what=sched, first last

So, why isn't this showing up in the admin screen?

[John]

It should show up on the profiles page with a recent version, however if the settings were changed to unschedule, and that failed, the admin page could show the fact it was unscheduled when it wasn't. You could reschedule and then unschedule the profile again.

[jamon]

Ahhh. I'm beginning to see the light.

I rescheduled and ran my little script. It showed TWO entries against that profile.

I unscheduled and reran my little script. It showed the ONE entry that I'm trying to eliminate.

I think this may have to do with a process in which we copied a profile to a new name, and deleted the old one, then recopied back to the old name, in an attempt to clean up something.

Does that sound feasible? If so, shouldn't the delete profile action also delete any related scheduled rewalks?

Does the wipesched thing wipe schedules for ALL profiles?

Thanks!

[jason112]

the wipesched does remove all schedules, but you can remove that certain one with a sql statement:

tsql -d texis/testdb "delete from SYSSCHEDULE where id = '41f11f7f4';"