Hi Emanuele the traceback shows that the zope over doesn't start because you have another zope server running on the same port (8080 according to your site.cfg). So, when you're going to localhost:8080 you're probably seing another zope/plone instance running and not plumi's one.
You can change the port in site.cfg. You should then re-run buildout with: ./bin/buildout -vN devel.cfg the N switch tells buildout only to download and install new eggs, so it will run much faster than the first time. Also, in plumi 4.0 beta the product is just called "Plumi" on the "Add/Remove Programs". If you want the full plumi experience like on demo.plumi.org don't forget to install the plumi skin after you've finished installing Plumi. Cheers, Mike On Wed, 2010-12-01 at 15:22 +0100, Emanuele Rodo wrote: > > Hi Mike: Thanks for help; > > here what > > sudo ./bin/instance-debug fg > > produces: > > /usr/lib/python2.6/dist-packages/zope/__init__.py:1: UserWarning: > Module _hashlib was already imported from None, > but /usr/local/plumi4/eggs/hashlib-20081119-py2.6-linux-x86_64.egg is > being added to sys.path > # this is a namespace package > Traceback (most recent call last): > File > "/usr/local/plumi4/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/run.py", > line 56, in <module> > run() > File > "/usr/local/plumi4/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/run.py", > line 21, in run > starter.prepare() > File > "/usr/local/plumi4/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/__init__.py", > line 80, in prepare > self.setupServers() > File > "/usr/local/plumi4/eggs/Zope2-2.12.13-py2.6-linux-x86_64.egg/Zope2/Startup/__init__.py", > line 216, in setupServers > % (server.servertype(),e[1])) > ZConfig.ConfigurationError: There was a problem starting a server of > type "HTTPServer". This may mean that your user does not have > permission to bind to the port which the server is trying to use or > the port may already be in use by another application. (Address > already in use) > > I argue that is fine. Still, however, I do not find any **Plumi > application setup option* in the ***Add/Remove Products** Site > Setup sidebar of plone. How do I get to that? Shall I do something > else before. > > Thanks again in advance for any help. > > > > Emanuele. > > > > On Wed, Dec 1, 2010 at 12:05 PM, Mike Muzurakis <[email protected]> > wrote: > > Hi Emanuele, > > > On 30/11/10 8:10 PM, Emanuele Rodo wrote: > > > Hello And: > > > > > > my first attempts with the new plumi/beta in the > production setting were > > > not much fruitful; actually, no supervisord is found, nor, > when I run > > > the plone instance as addressed in the installation guide > (at > > > http://en.flossmanuals.net/bin/view/Plumi/Installation), I > do find any > > > **Plumi application setup option* in the ***Add/Remove > Products** Site > > > Setup sidebar of plone. > > > > You can try the plumi 4.0 beta, by doing the following: > You should first get some software required for compiling as > described > in the 1st section, here: > > http://svn.plone.org/svn/collective/plumi.app/tags/4.0b1/docs/INSTALL.txt > > Then: > svn co > http://svn.plone.org/svn/collective/plumi.app/tags/4.0b1/ > plumi4 > cd plumi4 > python2.6 bootstrap.py -c devel.cfg > ./bin/buildout -c devel.cfg > > Buildout should take quite a while to finish downloading an > installing > everything. Afterwards, you can do the: > ./bin/supervisord > ./bin/instance-debug fg > > If you don't have a supervisord, it means that buildout has > stopped > before the end and there should be an error message and a > traceback. > Send us the error and the traceback and we'll try to figure > out what's > wrong. > > Thanks for testing, > Mike > > > > > > > > > > > > > > > > > My current site.cfg file is as follows: > > > > > > [site] > > > # arch should be either linux32 or linux64. mac support > coming soon > > > arch = linux64 > > > > > > # the default Administrator's username and password > > > user = admin:******* > > > > > > # the id of your plumi site > > > portal-id = videobank-plumi #Plone > > > > > > # the address where ZEO will be listening on > > > zeo-address = localhost:8100 > > > > > > # the address you debug instance will be listening on > > > instance-debug-address = localhost:8080 > > > > > > # the address where Zope's Medusa FTP is listening on > > > instance-ftp = localhost:8021 > > > > > > # the public ftp address of plumiftp. By default any ip, > port 21, which > > > requires root privileges to start > > > plumiftp-address = *:21 > > > > > > # change that if not using port 21 > > > ftp-user = root > > > > > > # the addresses of the zope instances > > > instance1-address = localhost:8081 > > > instance2-address = localhost:8082 > > > instance3-address = localhost:8083 > > > instance4-address = localhost:8084 > > > > > > # the icp addresses for each zope instance > > > instance1-icp = localhost:8091 > > > instance2-icp = localhost:8092 > > > instance3-icp = localhost:8093 > > > instance4-icp = localhost:8094 > > > > > > > > > # hostname and port for transcode daemon > > > transcode-host = localhost > > > transcode-port = 8888 > > > transcode-user = daemon > > > > > > # varnish user and address to listen to > > > cache-user = root > > > cache-address = localhost:8090 > > > > > > # hostname, port and credentials for supervisor > > > supervisor-host = localhost > > > supervisor-port = 8890 > > > supervisor-user = supervu > > > supervisor-pass = supervp > > > > > > # haproxy port and host > > > balancer-host = localhost > > > balancer-port = 8089 > > > balancer-user = proxy > > > > > > # syslog address > > > syslog-host = localhost > > > > > > # web server user > > > www-user = www-data > > > www-address = 80 > > > www-server-name = dev.raw-news.net:8080/videobank-plumi > > > www-videoserver-name = video.raw-news.net > > > > > > # zope and zeo will be running as > > > zeo-user = zope > > > zope-user = zope > > > > > > # cache options > > > zeo-client-cache-size = 1024MB > > > zodb-cache-size = 10000 > > > > > > # the folder where transcoded videos are being stored > > > videofolder = transcoded > > > > > > # add here additional eggs that should be available to > your portal > > > eggs = > > > > > > # additional zcml includes > > > zcml = > > > > > > # the mimetypes supported by default by the transcode > profiles below > > > default_supported_mimetypes = ['application/ogg', > 'video/flv', > > > 'video/x-flv', 'video/mpeg', 'video/3gpp', > 'video/x-ms-wmv', > > > 'video/ogg', 'video/x-ogg', 'video/x-ogm+ogg', > 'video/quicktime', > > > 'video/x-la-asf', 'video/x-ms-asf', 'video/x-msvideo', > 'video/mp4'] > > > > > > # a list of dicts containing the supported transcode > profiles > > > {'id':..,'cmd':..,'supported_mime_types':..} > > > transcode-profiles = [ { 'id' : 'jpeg', 'cmd' : > 'scripts/getThumb \"%s\" > > > \"%s\"', 'supported_mime_types': > ${site:default_supported_mimetypes}, > > > 'output_mime_type': 'image/jpeg', 'output_extension': > 'jpg' }, { 'id' : > > > 'mp4', 'cmd' : 'scripts/transcodeMp4 \"%s\" \"%s\"', > > > 'supported_mime_types': > ${site:default_supported_mimetypes}, > > > 'output_mime_type': 'video/mp4', 'output_extension': > 'mp4' }, { 'id' : > > > 'ogg', 'cmd' : 'scripts/transcodeTheora \"%s\" \"%s\"', > > > 'supported_mime_types': > ${site:default_supported_mimetypes}, > > > 'output_mime_type': 'video/ogg', 'output_extension': > 'ogv' }, { 'id' : > > > 'mpeg2', 'cmd' : 'scripts/transcodeMpeg2 %s %s', > 'supported_mime_types': > > > ${site:default_supported_mimetypes}, 'output_mime_type': > 'video/mpeg', > > > 'output_extension': 'mpg' },{ 'id' : 'dvd', 'cmd' : > 'scripts/makeIso %s > > > %s', 'supported_mime_types': 'text/xml', > 'output_mime_type': > > > 'application/octet-stream', 'output_extension': 'iso' }, ] > > > > > > # shared secret for symmetric encryption of transcode > requests. If you > > > update it here make sure you also update it in the > transcode settings panel. > > > secret = 1771d99931264d538e75eeb19da7d6a0 > > > > > > Please, address me to any mistake or ingenuous setting. > Thank you. > > > > > > > > > Trust you can help. > > > > > > Kind regards. > > > > > > > > > > > > Emanuele. > > > > > > > > > > > > P.S.: In the manual, I would suggest the /usr/local rather > than the /opt > > > directory to install - in debian, the / directory gets > filled with > > > relative ease during the buildout-process, which then ends > with errors. > > > _______________________________________________ > > Discuss mailing list > > [email protected] > > http://lists.plumi.org/listinfo/discuss > > > > > > -- > Emanuele Rodo > > RAW-news, Report Around the World > > E: [email protected] > W: www.raw-news.net _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
