Can you suggest a patch in the installation script to remove the check of the CGI URL? I've got Webinator running by copying over my RH7.2 installation, but it is not automatically walking (I probably missed some cron entry the install script does).
We were able to test on a RedHat 7.1 machine and could not reproduce the problem. However we're adding a patch that should handle the resulting erroneous "not a full path" issues better. You can do the same by editing the install script and adding double quotes around the second arg to getdir calls. For example, on line 1220, change this:
getdir "CGI URL prefix" $CgiUrl url
to this:
getdir "CGI URL prefix" "$CgiUrl" url
Neither the install script nor Webinator uses cron; Webinator has its own scheduling API via the Texis Monitor process which is started by any Texis or Webinator program.
You should have a process (ps auxw) called "monitor" running. Look in INSTALLDIR/texis/monitor.log to check for monitor errors.
The Webinator admin interface will generally complain if monitor is not running or there is a problem setting the schedule. What did you set the rewalk schedule to?
Actually, the monitor.log looks fine. There were some permission complaints back in November when I was messing with it...
200 Nov 15 06:28:54 Texis Monitor version 04.00.1005676548 starting (pid 2587)
100 Nov 15 06:28:54 Warning: monitor running as root
200 Nov 15 06:28:54 Database Monitor on /usr/local/morph3/texis/testdb/ starting (pid 2589)
006 Nov 15 06:47:24 Can't write to license file /usr/local/morph3/license.new: Permission denied
I probably changed directory permissions or something to get rid of the complaint a little later:
200 Nov 18 02:39:27 Contacting license server
200 Nov 18 02:39:29 Successful reply from license server
006 Nov 18 02:39:29 Can't write to license file /usr/local/morph3/license.new: Permission denied
000 Nov 18 02:39:29 Invalid license /usr/local/morph3/license.key
200 Nov 18 02:39:29 Texis Monitor exiting due to error (pid 2227)
200 Nov 18 06:31:04 Texis Monitor version 04.00.1005676548 starting (pid 13827)
200 Nov 18 06:31:04 License Violation (License Server Contact)
200 Nov 18 06:31:04 Contacting license server
200 Nov 18 06:31:05 Successful reply from license server
200 Nov 18 06:31:06 Database Monitor on /usr/local/morph3/texis/testdb/ starting (pid 13835)
I generally have a different database set to walk each morning at 1am. Here's monitor.log for early this morning:
200 Jan 2 23:21:36 Database Monitor on /usr/local/morph3/texis/FccOmd/db1/ exiting (pid 28575)
200 Jan 3 01:57:21 Database Monitor on /usr/local/morph3/texis/FccRules/db1/ starting (pid 28709)
200 Jan 3 02:02:21 Database Monitor on /usr/local/morph3/texis/FccRules/db1/ exiting (pid 28709)
200 Jan 3 02:06:51 Database Monitor on /usr/local/morph3/texis/FccRules/db1/ starting (pid 28750)
200 Jan 3 02:11:51 Database Monitor on /usr/local/morph3/texis/FccRules/db1/ exiting (pid 28750)
Looking at my query log, the times correspond to times people have done searches. I see nothing about an attempt to start a walk.
There should have been a walk of FccCsb this morning at 1am. The last walk was one manually started by me:
Perhaps the script realizes it has not been a week since the site was walked and therefore decided to not walk it this morning? Maybe I just have to wait a week...
Ideas?
You guys are great! Especially since I'm still using the free version. I'll try to squeeze the money together soon for the commercial version.
Recentness of walk is irrelevant to the scheduler. It walks when scheduled. What are the actual settings of your "Rewalk Type" and "Rewalk Schedule" "Frequency" and "Hour"?
Check your "Walk Status" for evidence of trying to rewalk.
If there's no evidence of attempts, try changing the schedule to something else, click update (not go), then change it back and update (not go) again. Maybe there was a problem setting the schedule the first time and you didn't notice the warning/error message.
