Failed to open searchwords.log

[Ray]

I can't create a searchwords.log file with content. Running 5.1 Standard, I configured the file path log/searchwords.log, and enabled Log searches made on your site.

Can you clarify if you mean that the log file was writing successfully prior to upgrading to V5.1 (if so, which version were you using)? Or have you never got log file working on this server before?

I keep a copy of the site on my computer, where Zoom saves its output files. The sitesearch/log is both on the web and computer server. I even created an empty file siteserach/log/searchwords.log with Notepad.

No log has been recorded on the web or locally. What am I doing wrong? I thought it might be a path error - but can find no trace of an errant file.

Have you set the file/folder permissions? This is important. Please refer to the instructions on this page:
http://www.wrensoft.com/zoom/support/logging.html

[kiwibrit]

I can't create a searchwords.log file with content. Running 5.1 Standard, I configured the file path log/searchwords.log, and enabled Log searches made on your site.

The Zoom files ares in the web folder sitesearch and I have created the folder sitesearch/log.

I keep a copy of the site on my computer, where Zoom saves its output files. The sitesearch/log is both on the web and computer server. I even created an empty file siteserach/log/searchwords.log with Notepad.

No log has been recorded on the web or locally. What am I doing wrong? I thought it might be a path error - but can find no trace of an errant file.

[mjones]

Hey thanks,

I just didn't have write permission to the log file. Being a Windows person, I didn't think to look, but Unix is a strange animal.

What I mean by two levels of security is that just because you give user access to a directory in Unix, does not imply you give access to the directories under it. You have to give each directory below it user names and passwords, too. No kidding. At least that's the way it is with this pain in the neck web server.

Much appreciated,

Michele

[mjones]

Hi,

I can set the file permissions on the Unix server. I'll read the details in the link you sent and let you know how it goes.

Previously, I had it set not to log search words, but now I'd like to get it working, if not for this website, for others.

Thanks for responding,

Michele

[David]

The easy solution is to turn search word logging off. Then the error message, "Unable to write to log file", will disappear.

You can turn off logging from the advanced tab in the Zoom configuration window (it is off by default in fact).

I am not sure what exactly you mean by having, two levels of directory security. But I doubt it affects this issue, or you might be confusion your FTP/Telnet login details with file permissions?

Anyway, if you want to get logging working, then it requires some knowledge of the Unix file system permissions (if as you say, you are hosting on Unix). You need to set the permissions to allow the creation of the log file.

[mjones]

Hi,

I hope someone can help with this. I'm afraid the answer may be a bit over my head.

When running a search, it seems to be working fine in general, except I get this messae about the log file:

Warning: fopen(searchwords.log) [function.fopen]: failed to open stream: Permission denied in /home/minusfor/public_html/employee/home/Search/search.php on line 2039. Unable to write to log file (searchwords.log). Check that you have specified the correct log filename in your Indexer settings and that you have the required file permissions set.

The web server is Unix and I'm using a search.php file (which doesn't work in XP Pro localhost, but that's another story). There is directory security on the webserver. (Don't get me going on how much I hate it and the web hosting company.)

There are two levels of security, but the username/password is the same for both levels. The log file is in the same directory as search.php.

I don't know what else to say except please help! I'd like to use this program for another website on the same Unix server, too.

Thanks a bunch,

Michele