Pawtucket2: access to /media directory via symbolic link doesn't work

RalphMA

I installed Pawtucket2 in a /pawtucket subdirectory of the Providence installation, as indicated in your manual instructions. I then created a symbolic link in /pawtucket to the /media directory of Providence. However, when accessing Pawtucket in the web browser, the following error message appears: “It looks like the media directory is not writable by the webserver ...”.

I then removed the symbolic link as a test and created a new directory /media/name-of-my-ca-installation in /pawtucket instead. Now the error message in the web browser is gone, but of course the images from Providence are missing in Pawtucket.

What could have gone wrong when creating the symbolic link, that explains the error message? The /media directory is writable by the web server, I checked that. So the error message is not correct. I used relative paths when creating the symbolic link; maybe that's the problem?

Sizzly

What operating system are you using? What command did you run to generate the symbolic link?

RalphMA

The server is running with FreeBSD. This is the SSH command I used (in the providence root directory):
ln -s media pawtucket/media

Sizzly

That sure looks right.

Did you run it as a sudo command? what's the output of ls -al|grep media in the pawtucket directory? Also, readlink -f <full path to pawtucket media directory> could shed some light on what's going on.

RalphMA

Sudo didn't help either. But I solved the problem: It was actually due to the relative paths. I executed the command in the root directory usingi absolute paths. Now it works.

Thanks for the help anyway!