Actually I think I fixed it... I had originally had the -c in to tell htdig which config file to use, but later changed it to all -v verbose usage. I had to update the LD_LIBRARY_PATH and PATH within the script. I updated this environment information to fix the problems, but somewhere within changing things, something else broke.. ;-) Everything seems to be working now.
thanks, Dan -----Original Message----- From: Neil Kohl [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 2:54 PM To: Sixbury, Dan; [EMAIL PROTECTED] Subject: RE: [htdig] Issues with Cron Dan, The configuration directory is a compiled-in value that can be overridden with the CONFIG_DIR environment variable. The default config file name is htdig.conf. You can override the defaults with the -c switch. If you've got two sites with two diffferent config files, you need to run two jobs: rundig -c /path/to/atlas.conf rundig -c /path/to/wolf.conf As you noted it's funny that rundig works on the command line but not in cron. Your setup should not work on the command line if you just do a "rundig" as it needs to find one of the two config files -- is htdig.conf a link to one of these (or vice versa)? There are other rundig options that you might want to pass such as -a (use alternate work files so the search engine will remain online while the site gets reindexed). I set -v -v -v and redirect rundig output to a file. The verbose rundig output is a good starting point for resolving search problems because the first thing you need to know is whether the file(s) in question get indexed. Neil Kohl Manager, ACP-ASIM Online American College of Physicians - American Society of Internal Medicine [EMAIL PROTECTED] 215.351.2638, 800.523.1546 x2638 >>> "Sixbury, Dan" <[EMAIL PROTECTED]> 01/27/03 02:50PM >>> Neil, After I added the -v to the rundig line within the script I received some of the following (Below)... We have this report emailed to us upon completion of the script. I wasn't getting this information previously, so I assume the -v gave me the extra output. I did a find for the htdig.conf and the only one I found was /opt/htdig-3.1.6/installdir/htdig.conf. I'm the systems admin, so I don't follow everything that happens with HtDig, but of course I had to download, compile, install, and maintain it. I just looked and it looks like we have two .conf files atlas.conf and wow.conf which correspond to the two sites that we are doing digs on. Odd that if I run the script manually it seems to work, but from cron it doesn't work. Where does it know to use the atlas or wow .conf file as opposed to htdig.conf? thanks, Dan ------------------------------------------------------------------------------- rundig: Start time: Mon Jan 27 13:15:00 CST 2003 htdig: Unable to find configuration file '/opt/www/htdig/conf/htdig.conf' rundig: Done Digging: Mon Jan 27 13:15:00 CST 2003 htmerge: Unable to open word list file '/opt/www/htdig/db/atlas/db.wordlist.work'. Did you index anything? Check your config file and try running htdig again. rundig: Done Merging: Mon Jan 27 13:15:00 CST 2003 rundig: End time: Mon Jan 27 13:15:00 CST 2003 ------------------------------------------------------------------------------- -----Original Message----- From: Neil Kohl [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 12:59 PM To: Sixbury, Dan; [EMAIL PROTECTED] Subject: Re: [htdig] Issues with Cron And there's no errors or anything unusual in output from your cron job? Try adding -v -v -v to the args for rundig and see if the output is more helpful. Neil Kohl Manager, ACP-ASIM Online American College of Physicians - American Society of Internal Medicine [EMAIL PROTECTED] 215.351.2638, 800.523.1546 x2638 >>> "Sixbury, Dan" <[EMAIL PROTECTED]> 01/27/03 11:50AM >>> I have been working with the cron script for running htdig on a Solaris 8 server. I have been looking through the archives of this newsgroup to find anything, but haven't found the answer to my problem as of yet. Like some of the other people, the rundig script works fine when run manually, but if run from cron, it completes immediately and doesn't to the "dig" or the "merge". Typically if a script runs manually, but not through a cron it means that there is an environment setting that is missed, but all of the paths are explicitly stated in the cron script. Any suggestions? My cron job looks almost exactly like the cron from the htdig web site that was offered by Geoff Hutchison in one of the newsgroup threads. Thanks, Dan ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld =omething 2 See! http://www.vasoftware.com _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld =omething 2 See! http://www.vasoftware.com _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
