Hello, has the buildout finished correctly? when you do a ./bin/supervisorctl status what do you get? Are all services running?
Remember you must have these two settings on the site.cfg, before you run buildout. www-server-name = new.plumi.org www-videoserver-name = newvideos.plumi.org If you can't create the domains, put them on /etc/hosts to point at localhost, to do some local testing (other computers won't see them of course, unless you point to real domains) You have to check the logs on var/log and parts/transcodedaemon/ why it returns Internal Server Error. From the buildout settings I cannot guess what the error might be Please follow the instructions on https://github.com/plumi/plumi.app/blob/master/docs/INSTALL.txt Finally, I see from your buildout that you're using an older version of Plumi. I suggest that you use the latest code from https://github.com/plumi/plumi.app (git clone https://github.com/plumi/plumi.app.git) or wait a few days until 4.5 version is released! On Mon, Nov 26, 2012 at 3:42 PM, 陈元斌 <[email protected]> wrote: > Hello Markos, >> > > I had successfully installed plumi on my labtop. But I cannot get > transcoding work on it. Transcode status says 'you may like to restart > transcoding'. But when I clicked 'restart transcoding' link, I got Internal > Server Error. Could you help on this? > > Below is my site.cfg. Currently I do not have a domain. So I just use > localhost in the configuration file. I installed plumi on ubuntu server > 12.04 with python 2.7. > > [site] > # github sources base, switch to the second option to bypass http auth > sources-base = git https://github.com/ > #sources-base = git [email protected]: > > # arch should be either linux32 or linux64. mac support coming soon > arch = linux32 > > # ipv4 address for ${site:local-ip} > local-ip = 127.0.0.1 > > # the default Administrator's username and password > user = admin:admin > > # the address where ZEO will be listening on > zeo-address = ${site:local-ip}:8100 > > # the address you worker instance will be listening on > worker-address = 127.0.0.1:8080 > > # gunicorn settings > gunicorn-port = 8000 > localhost = 127.0.0.1 > anyhost = 0.0.0.0 > > # hostname and port for transcode daemon > transcode-host = ${site:local-ip} > transcode-port = 8888 > > # hostname, port and credentials for supervisor > supervisor-host = ${site:local-ip} > supervisor-port = 8890 > supervisor-user = supervu > supervisor-pass = supervp > > # the folder where transcoded videos are being stored > videofolder = transcoded > > environment-vars = > PYTHON_EGG_CACHE ${buildout:directory}/var/.python-eggs > zope_i18n_compile_mo_files true > PTS_LANGUAGES en, id > # longrequestlogger_file ${buildout:directory}/var/log/longrequest.log > # longrequestlogger_timeout 5 > # longrequestlogger_interval 5 > > > ### The following configuration options are only used by production builds > ### > > # the id of your plumi site > portal-id = Plone > > # the address where Zope's Medusa FTP is listening on > instance-ftp = ${site:local-ip}: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 > > # effective user for the transcodedaemon process > transcode-user = daemon > > # 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 > > # varnish user and address to listen to > cache-user = root > cache-address = ${site:local-ip}:8099 > > # syslog address > syslog-host = ${site:local-ip} > > # web server user > www-user = www-data > www-address = 80 > #www-server-name = www.wheetie.com > www-server-name = localhost > www-videoserver-name = localhost > #www-videoserver-name = vedios.wheetie.com > > # effective user for zope and zeo processes > zeo-user = zope > zope-user = zope > > # cache options > zeo-client-cache-size = 1024MB > zodb-cache-size-bytes = 102400000 > > # the mimetypes supported by default by the transcode profiles below > default_supported_mimetypes = ['application/ogg',\ > 'video/ogg',\ > 'video/x-ogg',\ > 'video/x-ogm+ogg',\ > 'video/flv',\ > 'video/x-flv',\ > 'video/mpeg',\ > 'video/3gpp',\ > 'video/x-ms-wmv',\ > 'video/quicktime',\ > 'video/x-la-asf',\ > 'video/x-ms-asf',\ > 'video/x-msvideo',\ > 'video/mp4',\ > 'video/webm',\ > 'video/x-matroska',\ > ] > > # supported transcoding profiles > transcode-profiles = [\ > {'id': 'iso',\ > 'cmd': 'scripts/iso %s %s',\ > 'supported_mime_types': 'text/xml',\ > 'output_mime_type': 'application/octet-stream',\ > 'output_extension': 'iso' },\ > {'id': 'jpeg',\ > 'cmd': 'scripts/jpeg %s %s',\ > 'supported_mime_types': ${site:default_supported_mimetypes},\ > 'output_mime_type': 'image/jpeg',\ > 'output_extension': 'jpg' },\ > {'id': 'mpeg2',\ > 'cmd': 'scripts/mpeg2 %s %s',\ > 'supported_mime_types': ${site:default_supported_mimetypes},\ > 'output_mime_type': 'video/mpeg', 'output_extension': 'mpg' > },\ > {'id': 'mp4-high',\ > 'cmd': 'scripts/mp4-high %s %s',\ > 'supported_mime_types': ${site:default_supported_mimetypes},\ > 'output_mime_type': 'video/mp4', 'output_extension': 'mp4' },\ > {'id': 'mp4-low',\ > 'cmd': 'scripts/mp4-low %s %s',\ > 'supported_mime_types': ${site:default_supported_mimetypes},\ > 'output_mime_type': 'video/mp4', 'output_extension': 'mp4' },\ > {'id': 'webm-high',\ > 'cmd': 'scripts/webm-high %s %s',\ > 'supported_mime_types': ${site:default_supported_mimetypes},\ > 'output_mime_type': 'video/webm', 'output_extension': 'webm' > },\ > {'id': 'webm-low',\ > 'cmd': 'scripts/webm-low %s %s',\ > 'supported_mime_types': ${site:default_supported_mimetypes},\ > 'output_mime_type': 'video/webm', 'output_extension': 'webm' > },\ > ] > > # additional eggs that should be available to your portal - leave empty if > unsure > eggs = > # em.taxonomies > # unweb.shareit > # collective.captcha > # Products.LongRequestLogger[standalone] > # plone.formwidget.captcha > # plonetheme.plumigreen > # plumi.euclid > > # additional zcml includes - leave empty if unsure > zcml = > # em.taxonomies > # unweb.shareit > # collective.captcha > # plone.formwidget.captcha > # plonetheme.plumigreen > # plumi.euclid > > develop = . > # src/plumi.content > # src/plumi.skin > # src/plumi.locales > # src/plone.app.locales > # src/collective.transcode.daemon > # src/collective.transcode.recipe > # src/collective.transcode.star > # src/collective.mediaelementjs > # src/collective.piwik.mediaelement > # src/collective.piwik.core > # src/collective.recipe.scriptgen > > > [sources] > #plumi.content = ${site:sources-base}plumi/plumi.content.git > #plumi.skin = ${site:sources-base}plumi/plumi.skin.git > #plumi.locales = ${site:sources-base}plumi/plumi.locales.git > #collective.transcode.star = > ${site:sources-base}plumi/collective.transcode.star.git branch=master > #collective.transcode.recipe = > ${site:sources-base}plumi/collective.transcode.recipe.git branch=master > #collective.transcode.daemon = > ${site:sources-base}plumi/collective.transcode.daemon.git branch=master > #collective.piwik.mediaelement = > ${site:sources-base}plumi/collective.piwik.mediaelement.git branch=master > #collective.piwik.core = > ${site:sources-base}plumi/collective.piwik.core.git branch=master > #collective.seeder = ${site:sources-base}plumi/collective.seeder.git > branch=master > #collective.contentlicensing = > ${site:sources-base}collective/collective.contentlicensing.git branch=master > #em.taxonomies = svn http://svn.engagemedia.org/em.taxonomies/trunk/ > #collective.recipe.scriptgen = svn > http://svn.plone.org/svn/collective/buildout/collective.recipe.scriptgen/tags/0.2 > > [versions] > pycrypto = 2.4.1 > > > Date: Wed, 21 Nov 2012 21:45:46 +0200 >> From: Markos Gogoulos <[email protected]> >> To: Discussion about software development on Plumi >> <[email protected]> >> Subject: Re: [plumi-discuss] cannot visit plumi on my other pc >> Message-ID: >> <CA+CLxOYUmBGT9vGojzG5kRWoCLSt= >> [email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> >> Hi ben, >> >> we cannot tell what the problem might be, unless we have a look at the log >> files (var/log). >> >> Keep in mind that Plumi hasn't been tested to work on an existing Plone >> buildout setup, but requires to run it's own buildout. >> >> Cheers, >> Markos >> >> >> On Wed, Nov 21, 2012 at 7:15 PM, ??? <[email protected]> wrote: >> >> > Hi All, >> > >> > I tried to install plumi to my existing plone site via buildout. I add >> > plumi.app in buildout.cfg and then ran buildout. Plumi had been >> installed >> > successfully. And I can activate it on site setup. But after I activate >> it, >> > I cannot visit my plone/plumi site from other pc any more. >> > >> > Can you help on it? >> > >> > Thanks >> > Ben >> > >> > _______________________________________________ >> > Discuss mailing list >> > [email protected] >> > http://lists.plumi.org/listinfo/discuss >> > >> > >> >> >> -- >> https://unweb.me >> state of the art information systems >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.plumi.org/pipermail/discuss/attachments/20121121/f77eaf7b/attachment-0001.html >> > >> >> ------------------------------ >> >> >> _______________________________________________ >> Discuss mailing list >> [email protected] >> http://lists.plumi.org/listinfo/discuss >> >> >> End of Discuss Digest, Vol 66, Issue 38 >> *************************************** >> > > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.plumi.org/listinfo/discuss > > -- https://unweb.me state of the art information systems
_______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
