Rewalk on schedule doesn't work

User avatar
John
Site Admin
Posts: 2622
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Rewalk on schedule doesn't work

Post by John »

You can run texis -LS to see which script is being run by the scheduler. It should be identical between the scheduler and manually started ones.

The default database can be specified in the texis.cnf file in the install directory (C:\Program Files\Thunderstone Software\Webinator), although you should not need to configure that.
John Turnbull
Thunderstone Software
markell
Posts: 15
Joined: Mon Aug 09, 2004 9:28 am

Rewalk on schedule doesn't work

Post by markell »

texis -ls :
Next run Schedule Script
-------------------------------------------------
in 16h 9m daily at 4 ...\webinator\dowalk/dispatch.txt
in 17h 9m daily at 5 ...\webinator\dowalk/dispatch.txt
<H6 ALIGN=right><A HREF="http://www.thunderstone.com/" TARGET="_top"><IMG SRC="/copy.gif" BORDER=0 WIDTH=304 HEIGHT=11 ALIGN=top ALT="Texis & Webinator Copyright (C) 2002 THUNDERSTONE - EPI, Inc."></A></H6>

This seems to be okay, right?

But, I do not find the file texis.cnf in that directory, or even on the computer. So, I guess we've found the problem ... and, I'm (pretty) sure that I haven't deleted it (as every user says ;-) ).
I installed Webinator first on a test-computer and even there is no config-file. A problem I had during the installation was that Webinator "told" it's running on a UNIX-system (that’s the reason I had to update the two scripts). Maybe that’s a reason of the missing config-file ... ???

What's the best way to create/get a proper config-file? ... please don't tell I have to reinstall Webinator :-)
User avatar
John
Site Admin
Posts: 2622
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Rewalk on schedule doesn't work

Post by John »

If you run with an uppercase -LS it will show the full path to the script.

The texis.cnf file can show up as a SpeedDial file in Windows Explorer, however you can open it in Notepad.
John Turnbull
Thunderstone Software
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Rewalk on schedule doesn't work

Post by mark »

If webinator running on windows says it's on unix you can force it correct by editing dowalk in the osinfo function. Change
<rex "winnt" $version>
<if "" neq $ret>
<$isnt=1><$pathseprex = "[/\\]">
<else><!-- otherwise Unix -->
<$isnt=0><$pathseprex = "/">
</if>
to
<$isnt=1><$pathseprex = "[/\\]">
markell
Posts: 15
Joined: Mon Aug 09, 2004 9:28 am

Rewalk on schedule doesn't work

Post by markell »

Okay, this time with uppercase ;-)

> texis -LS
Script: c:\program files\apache group\apache\htdocs\webinator\dowalk/dispatch.txt
Vars: profile= Intranet_Testsite what=sched
Schedule: daily at 4
Next run: 2004-09-03 04:00 (in 12h 6m)
Last run: 2004-09-02 04:00 (11h 53m ago) took 3m 26s with exit code 1
First run: 2004-08-26 04:00 (7d 11h ago)
Status: runnable, 8 executions, first last, id 412ca0bc7

Script: c:\program files\apache group\apache\htdocs\webinator\dowalk/dispatch.txt
Vars: profile=inside what=sched
Schedule: daily at 5
Next run: 2004-09-03 05:00 (in 13h 6m)
Last run: 2004-09-02 05:00 (10h 53m ago) took 3m 50s with exit code 1
First run: 2004-08-28 05:00 (5d 10h ago)
Status: runnable, 6 executions, first last, id 412ef22b4

<H6 ALIGN=right><A HREF="http://www.thunderstone.com/" TARGET="_top"><IMG SRC="/
copy.gif" BORDER=0 WIDTH=304 HEIGHT=11 ALIGN=top ALT="Texis & Webinator Copy
right (C) 2002 THUNDERSTONE - EPI, Inc."></A></H6>


It's not the problem that I can't open the texis.cnf, it really doesn't exist (I know this is maybe unbelievable, but trust me I checked a couple of times).


To mark: The problem with operating system is fixed. I just had to replace the dowalk and webinatoradmin scripts (it was your hint two weeks ago, thanks) ... I just thought the problems during the installation could be related with the missing config-file.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Rewalk on schedule doesn't work

Post by mark »

Here's a default windows texis.cnf for version 4.

; This is a sample texis.cnf config file. Move it to texis.cnf in the
; directory you installed Texis in (typically C:\morph3).
; It controls various settings in Texis, Vortex, and monitors. Typical
; default settings are commented out. Semi-colon (;) or pound-sign (#)
; start comments, end-of-line ends them. See the Texis manual for more
; on these settings.
; $Id: texis.cnf.src,v 1.30 2004-07-22 12:03:23-04 kai Exp $

; ---------------------------- Texis settings --------------------------------
[Texis]

; Locations for the thesaurus and user thesaurus
;equivs = builtin
;eqvsusr = %INSTALLDIR%/eqvsusr

; Lib Path is the path to search when loading Texis shared or dynamic
; libraries (such as JavaScript or SSL). It is a semicolon-separated
; list of directories to check, in given order. The following special
; variables will be replaced if embedded in the Lib Path value:
; %INSTALLDIR% The Texis installation dir
; %BINDIR% The Texis binary (executables) dir
; %SYSLIBPATH% The system-dependent dynamic library search path
; %% A percent sign
; NOTE that Lib Path only controls the run-time loading of Texis libs,
; *not* system libs such as the C lib (libc).
; Lib Path = %BINDIR%;%SYSLIBPATH%

; Log Bad SYSLOCKS can be set to save a copy of the SYSLOCKS if there
; are problems detected:
; Log Bad SYSLOCKS = 0

; Pipe filename to use for monitor statistics collection:
;Statistics Pipe = \\.\pipe\texisstats

; Pipe filename for compilation:
;Compile Pipe = \\.\pipe\texiscompile

;License: license file name.
;License = %INSTALLDIR%/license.key

; Vortex settings: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

; ScriptRoot is the root directory for Vortex scripts run from the web.
; (note to vhttpd users: this can be overridden by conf/vhttpd.conf.)
; It can be changed here if you wish to move scripts elsewhere.
; It defaults to your web server's DOCUMENT_ROOT directory:
;ScriptRoot = %INSTALLDIR%\htdocs

; ErrorScript is the file path to a Vortex script that will be run if
; a web-requested Vortex script cannot be started, eg. missing script,
; compile error, etc. This script can then take alternate action
; (eg. display error page, redirect, etc.):
ErrorScript = %INSTALLDIR%/texis/scripts/errorscript

; ErrorFile is the file path to a simple HTML file that will be sent to
; the Web client if a web-requested Vortex script cannot be started,
; *and* ErrorScript is either unspecified or unstartable. Ie. it is a
; "fallback" for ErrorScript:
ErrorFile = %INSTALLDIR%/texis/scripts/errorfile

; Vortex Log is where Vortex logs its errors. It defaults to texis/vortex.log
; in your install directory (%INSTALLDIR%). Note that this can be
; overridden by conf/vhttpd.conf for vhttpd:
;Vortex Log = %INSTALLDIR%/texis/vortex.log

; Default Database is the default database for Vortex. It defaults to
; texis/testdb in your install directory (%INSTALLDIR%):
;Default Database = %INSTALLDIR%/texis/testdb

; Default Script is the Vortex script to run if no script is specified
; when Vortex is run from the web server. It defaults to texis/testdb/index
; in your install directory (%INSTALLDIR%):
;Default Script = %INSTALLDIR%/texis/testdb/index

; Entropy Pipe is the path to the prngd daemon's Unix socket, if non-standard.
; Only required if Unix, using SSL, no random device, and custom socket:
;Entropy Pipe = %INSTALLDIR%/etc/egd-pool

; CGI Debug enables -dump in CGI mode: for debugging CGI env or path issues:
;CGI Debug = 0

; Charset Converter is an external program and arguments that translates
; its stdin in one charset to stdout in another. The variables
; %CHARSETFROM% and %CHARSETTO% will be replaced with charsets when run;
; embedded-space args may be double-quoted:
;Charset Converter = "%INSTALLDIR%/etc/iconv" -f %CHARSETFROM% -t %CHARSETTO% -c

; -------------------- Texis and Database Monitor settings -------------------
[Monitor]

; Run Level: for Texis Monitor
; bit 0: run as license monitor bit 1: exit if default db removed
;Run Level = 1

; Where to log errors and informational messages:
;Log File = %INSTALLDIR%/texis/monitor.log

;Log Native IO: for debugging; use native system calls for log file I/O
;(Windows only)
;Log Native IO = 0

;Log Reopen: for debugging; re-open log file every message
;Log Reopen = 0

;Pid File: optional file to store PID in. For debugging.
;Pid File =

;Trace Dns: aka Dns Trace; for debugging; trace DNS calls if >0
;Trace Dns = 0

;Trace Socket: for debugging; trace socket calls if >0
;Trace Socket = 0

;Trace Fcgi: for debugging; trace FastCGI calls if >0
;Trace Fcgi = 0

; How often to put a timestamp in the Log File, in seconds. 0 is never:
;Timestamp = 0

; Display Refresh and keyboard read intervals for ltest and chkind displays.
;Refresh = 5
;Keyboard Read = 1

; How often to check for stuck semaphores on the database
;Semaphore = 10

; The monitor will check the database every Removal seconds. If the
; database has been removed, or has been idle for more than DB Quiet
; seconds then the monitor will quit.
;Removal = 60
;DB Quiet = 120

; The monitor can check the database to see if your database was created
; with an older version of Texis. If so it can upgrade the SYSTEM tables.
; This can be set to 0 to disable this, which will ensure that older
; software can still use the database. This is discouraged as new features
; may not work as intended, and mixing versions of Texis on a database is
; strongly discouraged.
;Upgrade SYSTEM tables = 0

; How often (in seconds) to check monitor statistics:
;Statistics = 3600

; Whether to use blocking I/O when communicating with other monitors.
; Should be 0 (non-blocking) for all but Linux 1 kernels which may panic:
;Stats Block = 0

; Virtual-memory usage limit for monitors; will exit if exceeded.
; Default is no limit. Used for debugging:
;Mem Limit = 100MB

; Whether to allow monitor to fork() for subprocesses (vs. exec). Unix only.
; Bit 0: for monitor -s Bit 1: for monitor -C
;Fork = 3

; Maximum allowed internal scheduler failures:
;Max Scheduler Fails = 5

; -------------------------- Check-Index settings ----------------------------
[Chkind]

; How often to check for tables that need to be checked.
;Refresh = 120

; Only check indexes in SYSMETAINDEX
;SYSMETAINDEX = 0

; Automatically invoke chkind if 1. Set to 0 if you're doing manual index
; updates, ie. after a batch table update:
;Automatic = 1

; Verbosity: bit 0: msgs for updates bit 1: msgs for checks
;Verbose = 0

; --------------------------- Webinator settings -----------------------------
[Webinator]

; Where the live dowalk script lives. This is needed by the command-line
; replacement for gw.
dowalk = %INSTALLDIR%\Webinator\dowalk

; ------------------------ Anytotx (plugin) settings -------------------------
[Anytotx]

; Where the rule file is: details how to recognize and translate file types:
;Rule File = %INSTALLDIR%/conf/formats.rule

; Where the MIME types config file is: maps file extensions to MIME types:
;Types Config = %INSTALLDIR%/conf/mime.types

; -------------------------- Vortex scheduler settings -----------------------
[Scheduler]

;Run Level:
; bit 0: run schedule server
; bit 1: exit on startup error
; bit 2: respond to GETs for watchdog/monitor
;Run Level = 1

;BindAddress: local IP to listen to. This should be 127.0.0.1 for security.
;BindAddress = 127.0.0.1

;Port: TCP port to listen to.
;Port = 10005

;Texis: texis executable to run scheduled Vortex scripts
;Texis = %INSTALLDIR%\texis.exe

; ------------------------- Monitor web server settings ----------------------
[Httpd]

; >>> NOTE: These settings affect the experimental monitor web server. <<<
; >>> NOTE: You probably want vhttpd settings, in conf/vhttpd.conf. <<<

; Run Level: bit 0: run web server bit 1: exit monitor if startup error
;Run Level = 0

; Port: TCP port to listen on
;Port = 80

; Document Root: where to server documents from.
;Document Root = %INSTALLDIR%/htdocs

; Transfer Log: where to log transfers.
;Transfer Log = %INSTALLDIR%/logs/transfer.log

; Max Backlog: maximum number of pending connections. 0: OS default
;Max Backlog = 0

; Timeout: seconds to time out connections. <=0: default of 30 seconds
;Timeout = 30

; Bind Address: IP address to listen to. Default is any local address.
;Bind Address =

; User: local user to run CGI texis as. Default is same user as monitor.
;User =

; Pass: password to login User. Required if User is given.
; NOTE that this is plaintext: use EncPass instead. Overrides EncPass.
;Pass =

; EncPass: encrypted password to login User. Create with monitor -E:
;EncPass =

; Fast Logon: nonzero: use fast logon method for User (not recommended):
;Fast Logon = 0

; Max Clients: maximum concurrent connections.
;Max Clients = 32

; Max Header Size: maximum size of request + headers.
;Max Header Size = 4096

; Vortex Path: URL prefix indicating this is a Vortex request.
;Vortex Path =

; Texis Exe: local file path to Vortex executable to run Vortex scripts.
;Texis Exe = %INSTALLDIR%\texis.exe

; Index Files: space-separated list of local file names to check for
; directory index HTML.
;Index Files = index.html index.htm

; Directory Indexing: whether to do directory indexing if Index Files not found
;Directory Indexing = 1

; Pass Env: space-separated list of additional environment vars to pass on
; from startup server environment
;Pass Env =

; ---------------------- Monitor web server environment ----------------------
[Httpd Set Env]
; This section's settings are extra env vars for Monitor web server requests:

; ------------------------ Monitor web server FastCGI ------------------------
;[Httpd Fast CGI]
; This section may be repeated, once per FastCGI mapping.

; URL Prefix: maps URL prefix to this FastCGI server.
;URL Prefix = /fastcgi

; Command Line: command line and args to start local FastCGI server.
; Only needed if server is not already running on Local Bind Path.
;Command Line = /some/program my args "my quoted arg"

; Local Bind Path: host:port to bind and connect to local FastCGI server.
; Default is localhost:11000+.
;Local Bind Path = localhost:11000

; Buffer Size: max size of buffers (3). Should not exceed 64k.
;Buffer Size = 64k

; Pre Start: 1 if local FastCGI server should be started at web server init,
; rather than waiting for first web request (default).
;Pre Start = 0

; Kill On Exit: 1 if local FastCGI server should be killed at web server exit.
;Kill On Exit = 0
markell
Posts: 15
Joined: Mon Aug 09, 2004 9:28 am

Rewalk on schedule doesn't work

Post by markell »

I tried a couple of things and collected some information ...

Because "scheduled walk" still isn't working I installed Webinator 4.3 on my local computer, where "scheduled walk" is running without problems. So it seems "scheduled walk" is buggy on version 4.0.5, which we bought.
And the Webinator 4.3 which I installed is also a commercial version, at least it was shown like that on the admin-page ...

What I tried next was to install Webinator 4.3 on our live-webserver, because it is in a DMZ and behind a proxy it couldn't connect to the license-server. And because of that (I guess that's the reason) it's running as freeware version.
So I updated the license with texis -update with the file license.upd (which was shipped on the CD Webinator 4.0.5), like it was explained somewhere in the forum.

But I got the following error-message on the admin-page:
This site has been in violation of its license since 2004-09-23 15:17:02
Max Texis Version (20000(0)rows/10000(2)hits)
Upgrade your webinator

Output with texis -license:
Texis Web Script (Vortex) Copyright (c) 1996-2003 Thunderstone - EPI, Inc.
Commercial Webinator Version 4.03.1049392341 of Apr 3, 2003 (i686-intel-winnt-32-32)



What's the right way to update the license when the server is behind a proxy?
Or is there another problem?
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Rewalk on schedule doesn't work

Post by mark »

Webinator comes with a copy of Texis. Your Texis license is for the version you purchased. Not newer versions. You need to install the version you were shipped. You can then install the latest version 4 Webinator scripts obtained from the website. Most, if not all, schedule problems were related to the scripts, not the underlying Texis.
markell
Posts: 15
Joined: Mon Aug 09, 2004 9:28 am

Rewalk on schedule doesn't work

Post by markell »

That's what I did, see above ...

Installed Webinator 4.0.5, updated Scripts Webinator 4.4.17 dowalk & webinatoradmin ... but "scheduled walk" isn't working.

So, what else could I do to fix it?

And, why do I get a commercial version when I install our Webinator 4.3 on my desktop, and a freeware version (with the same install-file) on the server? (proxy-problem?)


... something else, maybe we bought the update to 4.3, at least I have a installation-file and it looks like it is a commercial version on my desktop (it is shown "commercial version" in admin-page).
But I'm not sure (there's no CD), I just started at that company 2 month ago and the guy who did this job left without any documentation ... and the Webinator was never running ...
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Rewalk on schedule doesn't work

Post by mark »

Sorry, the thread's too old and too long to remember or try to figure out what the state of things is. Just tried to answer your last question.

The installed version relies on the license.upd file. If your license happened to have been installed correctly on a machine and subsequently contacted the license server it will remember that machine and give it that license again if it loses it. If you're installing from a CD the license should be installed automatically. If you're installing from a downloaded version you need to install the license by hand.

Perhaps you should open a tech support ticket to get your version questions sorted out. Then remove everything related to webinator and start with a clean install.
Post Reply