Question

Dear all, I installed twiki and configured it following the instructions in the web manual. I cannot start the "twiki configure" and I always get the errors (apache error logs):

- "(13)Permission denied: exec of '/Library/WebServer/twiki/bin/view' failed" and

- "(13)Permission denied: exec of '/Library/WebServer/twiki/bin/configure' failed".

The authentication window is properly displayed and the user account is configured in .httpasswd twiki directories and file owners: www:www Thanks to those that could help.

Environment

-- YvesDoat - 13 Apr 2008

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

Check the ownerships for /Library/Webserver/twiki directory to make sure. I'm running 10.4.11 and am using www:admin.

* Another point to check is that Apache on the mac expects to find stuff under /Library/Webserver/Documents

• • I believe that the /Library/Webserver directory may in fact be access controlled (check /etc/httpd.conf and look for a call relating to that.
  • In fact, since the default is "deny from all" for all other directories, you probably have to specifically enable a for /Library/Weberver/twiki

Yup, this really smells like a tricky access issue.

For the Apache issues: Start by disabling the .htaccess files (if you are using them) in /twiki/bin Also check you httpd.conf or your /users/twiki_httpd.conf files to make sure you aren't limiting yourself their either.

For the file system issues: I basically walked through all the directories and "ls -a" over and over to find culprits.

-- RedByer - 15 May 2008

We installed under /Library/WebServer/twiki, and it worked out fine. But we found that the Mac's built-in Apache expected the cgi scripts to have a .cgi extension. Once we added the extension to the scripts, we were able to run configure.cgi. There we were able to configure TWiki to use the scripts with their new extensions.

-- DavidWolfe - 15 May 2008

FYI: You shouldn't have to have the .cgi extension required. For my installation, I actually placed it at the top level of the drive at /twiki and did not have to do any modifications other than made sure the twiki_httpd.conf was in place.

-- RedByer - 15 May 2008

The difference might be that we're running on Leopard Server. We had a 4.1 installation running on Tiger desktop and didn't have to add .cgi. But we couldn't get anything to run on Leopard Server. Poking around in Server Admin's Web Service pane > Settings > MIME Types > Content Handlers, we saw that cgi-script had a .cgi suffix set. We tried various things to get a cgi-script content handler that didn't have an extension at all, but were unable to do so. (We had the same experience on Tiger Server a few months ago.) As soon as we set the .cgi extension on Configure, we were immediately able to access it, but not any other scripts. So we added the extensions to all the scripts and set the extension in Configure.cgi, and all worked like magic.

-- DavidWolfe - 15 May 2008

Closing this question after more than 30 days of inactivity. Please feel free to re-open if necessary.

-- PeterThoeny - 23 Jul 2008