Subject: Buildout file permissions wrong? - msg#00078

Previous Message by Date: click to view message preview

TextIndexNG3 error

Hello Im trying to move a site to another server, but I get this error: Site Error An error was encountered while publishing this resource. Error Type: ImportError Error Value: The zopyx package could not be imported. Please check the installation of the TextIndexNG extension modules! I dont know what to do cause I had copy the same products (TextIndexNG3) of the old site, and it was working ok. Thanks, Yude pd: sorry my english, I speak spanish.

Next Message by Date: click to view message preview

Re: Buildout file permissions wrong?

Hi Jim,It sounds like you've done the right thing. The top-level Plone-3.1 directory does need to be world-readable (or at least, minimally, group-readable for a group that includes the "plone" user). It sounds like the Unified Installer probably needs to set the umask when doing a root install.SteveOn Tue, Jul 29, 2008 at 3:23 AM, JimL <jim.leek-rWG4PoLyIT+Fxr2TtlUqVg@xxxxxxxxxxxxxxxx> wrote: Hi, I have built Plone using buildout on Solaris 10 (sparc) as root. Two parts in my buildout.cfg file are "unifiedinstaller" (to generate the startup scripts) and "chown" (supposedly to set correct permissions for my root install): [chown] # This recipe is used to set permissions -- and ownership for root mode installs recipe = plone.recipe.command command =    chmod 600 .installed.cfg    touch ${buildout:directory}/var/log/zeoserver.log    find ${buildout:directory} -type d -name var -exec chown -R ${client1:effective-user} \{\} \;    find ${buildout:directory} -type d -name LC_MESSAGES -exec chown -R ${client1:effective-user} \{\} \;    find ${buildout:directory} -name runzope -exec chown ${client1:effective-user} \{\} \; update-command = ${chown:command} [unifiedinstaller] recipe = plone.recipe.unifiedinstaller user = ${client1:user} primary-port = ${client1:http-address} However, when I attempt to start the server using my startcluster.sh it won't start. I've tracked this down to file permissions (if I set the whole Plone directory to world readable - (chmod -R a+rx /opt/Plone) the server starts fine). Does anyone know the correct permissions I should use in my buildout? Cheers,  Jim -- View this message in context: http://n2.nabble.com/Buildout-file-permissions-wrong--tp612545p612545.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list Setup-G3yHMj00SlOLbbK5bonKug@xxxxxxxxxxxxxxxx http://lists.plone.org/mailman/listinfo/setup -- ______________________________________________________Steve McMahonReid-McMahon, LLCsteve-HR5nRXif9uVv8oa/uYrpnQ@xxxxxxxxxxxxxxxx steve-6oXym+Fh+UE@xxxxxxxxxxxxxxxx

Previous Message by Thread: click to view message preview

TextIndexNG3 error

Hello Im trying to move a site to another server, but I get this error: Site Error An error was encountered while publishing this resource. Error Type: ImportError Error Value: The zopyx package could not be imported. Please check the installation of the TextIndexNG extension modules! I dont know what to do cause I had copy the same products (TextIndexNG3) of the old site, and it was working ok. Thanks, Yude pd: sorry my english, I speak spanish.

Next Message by Thread: click to view message preview

Re: Buildout file permissions wrong?

Hi Jim,It sounds like you've done the right thing. The top-level Plone-3.1 directory does need to be world-readable (or at least, minimally, group-readable for a group that includes the "plone" user). It sounds like the Unified Installer probably needs to set the umask when doing a root install.SteveOn Tue, Jul 29, 2008 at 3:23 AM, JimL <jim.leek-rWG4PoLyIT+Fxr2TtlUqVg@xxxxxxxxxxxxxxxx> wrote: Hi, I have built Plone using buildout on Solaris 10 (sparc) as root. Two parts in my buildout.cfg file are "unifiedinstaller" (to generate the startup scripts) and "chown" (supposedly to set correct permissions for my root install): [chown] # This recipe is used to set permissions -- and ownership for root mode installs recipe = plone.recipe.command command =    chmod 600 .installed.cfg    touch ${buildout:directory}/var/log/zeoserver.log    find ${buildout:directory} -type d -name var -exec chown -R ${client1:effective-user} \{\} \;    find ${buildout:directory} -type d -name LC_MESSAGES -exec chown -R ${client1:effective-user} \{\} \;    find ${buildout:directory} -name runzope -exec chown ${client1:effective-user} \{\} \; update-command = ${chown:command} [unifiedinstaller] recipe = plone.recipe.unifiedinstaller user = ${client1:user} primary-port = ${client1:http-address} However, when I attempt to start the server using my startcluster.sh it won't start. I've tracked this down to file permissions (if I set the whole Plone directory to world readable - (chmod -R a+rx /opt/Plone) the server starts fine). Does anyone know the correct permissions I should use in my buildout? Cheers,  Jim -- View this message in context: http://n2.nabble.com/Buildout-file-permissions-wrong--tp612545p612545.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list Setup-G3yHMj00SlOLbbK5bonKug@xxxxxxxxxxxxxxxx http://lists.plone.org/mailman/listinfo/setup -- ______________________________________________________Steve McMahonReid-McMahon, LLCsteve-HR5nRXif9uVv8oa/uYrpnQ@xxxxxxxxxxxxxxxx steve-6oXym+Fh+UE@xxxxxxxxxxxxxxxx