Scheduled script does not execute

Post Reply
michel.weber
Posts: 256
Joined: Sat Oct 08, 2005 12:40 pm

Scheduled script does not execute

Post by michel.weber »

I tried to schedule a script for regular execution, but it does not seem to work.

The script is scheduled alright, but it does not seem to do anything (the walk status page is not updated), and i don't find an error anywhere.

What am i missing?

"D:\Program Files\Thunderstone\MORPH3\texis.exe" -r profile=mwmw -sched "weekly on mon at 2" "D:\Program Files\Thunderstone\MORPH3\texis\scripts/dowalk\reindex.txt"

I set the shcedule to 5 minutes and here is the shcedule info :

E:\Temp>texis -LS
Script: D:\Program Files\Thunderstone\MORPH3\texis\scripts\dowalk\reindex.txt
Vars: profile=mwmw
Schedule: every 5 min
Next run: 2010-02-26 19:40 (in 2m 26s)
Last run: 2010-02-26 19:35 (2m 34s ago) (never exited)
First run: 2010-02-26 19:35 (2m 34s ago)
Status: runnable, 1 executions, first last, id 4b8813590

Wat does the 'never exited' next to the 'last run' column mean
User avatar
mark
Site Admin
Posts: 5513
Joined: Tue Apr 25, 2000 6:56 pm

Scheduled script does not execute

Post by mark »

Never exited implies that it's still running. It just started 2 minutes ago so it may not be complete.

Did you look in vortex.log and monitor.log to see if anything shows up there?

Maybe you have a permission problem. ie running texis on the command line as a different user than from the web interface.

Why did you schedule a reindex for every week? That should not be needed at all under normal operation.
michel.weber
Posts: 256
Joined: Sat Oct 08, 2005 12:40 pm

Scheduled script does not execute

Post by michel.weber »

When i run the command from the command prompt, it works, and it takes 9 seconds

There was no particular reason for the interval of one week, i was just testing. I used reindex because i can see the result in walk status.


At the time the schedule fired i found the following :
Monitor.log :
015 2010-02-26 22:16:00 (568) Recursive mutex lock (depth 2) obtained at syssched.c:293: previous lock held at syssched.c:1662 in the function TXlockmutex
100 2010-02-26 22:20:22 (568) Job "D:\Program Files\Thunderstone\MORPH3\texis.exe" -r -sched iscmdln profile=mwmw "D:\Program Files\Thunderstone\MORPH3\texis\scripts\dowalk/\reindex.txt" returned exit code 24

vortex.log :
002 2010-02-26 22:16:00 D:\Program Files\Thunderstone\MORPH3\texis\scripts\dowalk/: Cannot open source file: Invalid argument

Schedule info :

E:\Temp>texis -LS
Script: D:\Program Files\Thunderstone\MORPH3\texis\scripts\dowalk\reindex.txt
Vars: profile=mwmw
Schedule: daily at 10:16pm
Next run: 2010-02-27 22:16 (in 23h 55m)
Last run: 2010-02-26 22:16 (4m 59s ago) took 4m 22s with exit code 24
First run: 2010-02-26 22:16 (4m 59s ago)
Status: runnable, 1 executions, first last, id 4b8839e30
User avatar
John
Site Admin
Posts: 2597
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Scheduled script does not execute

Post by John »

I noticed there is an extra \ in the message: dowalk/\reindex.txt" returned exit code 24

You may need to schedule with forward slashes for the path, e.g. dowalk/reindex.txt
John Turnbull
Thunderstone Software
michel.weber
Posts: 256
Joined: Sat Oct 08, 2005 12:40 pm

Scheduled script does not execute

Post by michel.weber »

OK

Converting all \ into / helped.
Now the job is fired up correctly. It takes about 8 seconds before the 'Reindex finished' message appears in the 'walk status' report, but a monitor process continues to consume 50% of CPU for about 5 minutes.
During this time it shows up as 'never exited' in the scheduler, but then it seems to end normally (no exit status and no error message in any of the log files).


Script: D:\Program Files\Thunderstone\MORPH3\texis\scripts\dowalk/reindex.txt
Vars: profile=mwmw
Schedule: daily at 17:00
Next run: 2010-03-02 17:00 (in 23h 56m)
Last run: 2010-03-01 17:00 (2 sec ago) still running
...
Last run: 2010-03-01 17:00 (3m 27s ago) (never exited)
...
Last run: 2010-03-01 17:00 (5m 6s ago) took 4m 6s
Post Reply