Freshed installation, with the same error. But this time, when I connected to main via http, I got 503 instead of 404.
On Thu, Jan 12, 2012 at 9:46 PM, Magicloud Magiclouds <[email protected]> wrote: > OK. Trying that. > But, just out of curiosity, it does not seem to give an obvious > (detailed) error message. So I could diag where is the problem. As you > may know, some ips are not accessible in China. For these, I'd have to > take special actions, like downloading them myself through a proxy. > > About the last point, your way works with instance-debug (listened on > 8080). But in production version, connecting directly to main.conf's > port (http://localhost:80/) would give the 404 error. There was no > chance to create Plone site. > > On Thu, Jan 12, 2012 at 4:24 PM, Mike Muzurakis <[email protected]> wrote: >> About the missing packages errors, there are some connection timeouts >> according to the log. You can try running: >> >> $ sudo bin/buildout -vN -c production.cfg >> >> the -N switch will bring only the missing packages, so you don't have to >> wait an hour for the buildout to run again. >> >> The final error message means that the plumi site was not created. You can >> easily create it now: >> - Visit your server address (e.g. http://localhost:8080) and click on create >> Plone site (don't check any of the products yet). The default username and >> password are admin:admin unless you changed them on site.cfg >> - After the site get's created, go to the site setup on the top right, pick >> Add/Remove products and install the Plumi product. >> - Install Plumi Skin if it is not installed. >> - That's it. If you want to publish videos as the admin user, log in from a >> different browser for the admin workspace to be created. >> >> >> On 01/12/2012 08:56 AM, Magicloud Magiclouds wrote: >>> >>> Here is the final error message. I think this is why the plumi site >>> was not created. >>> >>> patch: successfully patched >>> >>> /opt/plumi.app-4.3/eggs/plone.app.upgrade-1.1.4-py2.6.egg/plone/app/upgrade/v41/alphas.py >>> Installing plumisite. >>> Generated script '/opt/plumi.app-4.3/bin/plumisite'. >>> Installing auto-install-plumisite. >>> Traceback (most recent call last): >>> File "/opt/plumi.app-4.3/bin/zeoserver", line 56, in<module> >>> import plone.recipe.zeoserver.ctl >>> File >>> "/opt/plumi.app-4.3/eggs/plone.recipe.zeoserver-1.2.2-py2.6.egg/plone/recipe/zeoserver/__init__.py", >>> line 9, in<module> >>> import zc.recipe.egg >>> ImportError: No module named recipe.egg >>> ********************************************* >>> Overwriting versions/last-production-versions.cfg >>> ********************************************* >>> >>> On Thu, Jan 12, 2012 at 1:28 PM, Magicloud Magiclouds >>> <[email protected]> wrote: >>>> >>>> OK. I am starting a clean installation. >>>> It has not finished. But I see some error message, some warnings, some >>>> download error. >>>> But the process is still going. Not sure if these are important. >>>> >>>> $ sudo bin/buildout -c production.cfg >>>> Getting distribution for 'buildout.dumppickedversions'. >>>> Got buildout.dumppickedversions 0.4. >>>> Getting distribution for 'mr.developer==1.18'. >>>> warning: no files found matching 'README.txt' >>>> Got mr.developer 1.18. >>>> Getting distribution for 'argparse==1.1'. >>>> zip_safe flag not set; analyzing archive contents... >>>> Got argparse 1.1. >>>> mr.developer: Queued 'collective.contentlicensing' for checkout. >>>> mr.developer: Cloned 'collective.contentlicensing' with git. >>>> Couldn't develop '/opt/plumi.app-4.3/src/plumi.skin' (not found) >>>> Couldn't develop '/opt/plumi.app-4.3/src/collective.transcode.recipe' >>>> (not found) >>>> Couldn't develop '/opt/plumi.app-4.3/src/plumi.locales' (not found) >>>> Couldn't develop '/opt/plumi.app-4.3/src/collective.transcode.star' (not >>>> found) >>>> Couldn't develop >>>> '/opt/plumi.app-4.3/src/collective.piwik.mediaelement' (not found) >>>> Develop: '/opt/plumi.app-4.3/.' >>>> warning: no files found matching '*' under directory 'plumi' >>>> warning: no files found matching 'TODO' >>>> warning: no previously-included files matching '*pyc' found anywhere >>>> in distribution >>>> Couldn't develop '/opt/plumi.app-4.3/src/collective.transcode.daemon' >>>> (not found) >>>> Couldn't develop '/opt/plumi.app-4.3/src/collective.seeder' (not found) >>>> Couldn't develop '/opt/plumi.app-4.3/src/collective.piwik.core' (not >>>> found) >>>> Couldn't develop '/opt/plumi.app-4.3/src/plumi.content' (not found) >>>> Develop: '/opt/plumi.app-4.3/src/collective.contentlicensing' >>>> warning: no files found matching '*.css' under directory 'collective' >>>> warning: no files found matching '*.pdf' under directory 'collective' >>>> warning: no files found matching '*.png' under directory 'collective' >>>> warning: no previously-included files matching '*.pyc' found anywhere >>>> in distribution >>>> warning: no previously-included files matching '*~' found anywhere in >>>> distribution >>>> warning: no previously-included files matching '*.mo' found anywhere >>>> in distribution >>>> Couldn't develop '/opt/plumi.app-4.3/src/collective.medialementjs' (not >>>> found) >>>> Download error: [Errno 110] Connection timed out -- Some packages may >>>> not be found! >>>> Getting distribution for 'zc.recipe.egg==1.2.2'. >>>> Got zc.recipe.egg 1.2.2. >>>> Getting distribution for 'plone.recipe.zeoserver==1.2.2'. >>>> Got plone.recipe.zeoserver 1.2.2. >>>> >>>> >>>> On Thu, Jan 12, 2012 at 1:20 AM, Dimitris Moraitis<[email protected]> wrote: >>>>> >>>>> Hello again, >>>>> >>>>> sounds like the Plumi portal was not created. Did you get an error in >>>>> the production buildout? Running ./bin/plumisite might fix the problem. >>>>> >>>>> If that doesn't work can you run tail -f var/log/instance?.log and send >>>>> the output after trying to access the portal? >>>>> >>>>> Cheers, >>>>> Dimitris >>>>> >>>>> >>>>> On Jan 10, 2012, at 3:21 PM, Magicloud Magiclouds wrote: >>>>> >>>>>> Sorry I put this in another thread. Just got 4.3 running in my Debian >>>>>> Squeeze box. >>>>>> >>>>>> But it does not seem to working. Following docs/INSTALL.txt, >>>>>> bin/supervisorctl status indicates that everything is running. But >>>>>> when I opened http://www-server-name:www-address/, I got "Resource not >>>>>> found". main-plone-access.log recorded a 404 for GET /. >>>>>> What should I do now? >>>>>> -- >>>>>> 竹密岂妨流水过 >>>>>> 山高哪阻野云飞 >>>>>> _______________________________________________ >>>>>> Discuss mailing list >>>>>> [email protected] >>>>>> http://lists.plumi.org/listinfo/discuss >>>>> >>>>> _______________________________________________ >>>>> Discuss mailing list >>>>> [email protected] >>>>> http://lists.plumi.org/listinfo/discuss >>>> >>>> >>>> >>>> -- >>>> 竹密岂妨流水过 >>>> 山高哪阻野云飞 >>> >>> >>> >> > > > > -- > 竹密岂妨流水过 > 山高哪阻野云飞 -- 竹密岂妨流水过 山高哪阻野云飞 _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
