Hi Dimitris,

Thank you for your reply.

I did what you suggest (in fact I have done it before). But
know I have the following erro in instance1.log:

2012-05-22T10:50:15 ERROR collective.transcode Could not connect to transcode 
daemon http://transcode.c3sl.ufpr.br: not well-formed (invalid token): line 1, 
column 2

In transcode.log we got:

2012-05-22 10:50:15-0300 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - 
[22/May/2012:13:50:15 +0000] "POST / HTTP/1.1" 200 3 "-" "xmlrpclib.py/1.0.1 
(by www.pythonware.com)"

and nothing else.  Transcode is running at port 8888 and apacha rewriting is 
like this:

    Alias /transcoded /home/plumi/plumi.app-4.3.1/transcoded
    <Directory /home/plumi/plumi.app-4.3.1>
       Order allow,deny
       Allow from all
    </Directory>

    RewriteRule ^/transcoded - [L]
    RewriteRule ^(.*)$ - [E=BACKEND_LOCATION:127.0.0.1]
    RewriteRule ^(.*)$ - [E=BACKEND_PORT:8888]
    RewriteRule ^(.*)$ - [E=HOST:transcode.c3sl.ufpr.br]
    RewriteRule ^(.*)$ - [E=PORT:80]
    RewriteRule ^(.*)$ - [E=PROTO:http]
    RewriteRule  ^/(.*)/$ http://%{ENV:BACKEND_LOCATION}:%{ENV:BACKEND_PORT}/ 
[L,P]
    RewriteRule  ^/(.*)$ http://%{ENV:BACKEND_LOCATION}:%{ENV:BACKEND_PORT}/ 
[L,P]

Do you have any futher ideas?

Thanks

Luis
On Tue, May 22, 2012 at 01:50:05PM +0300, Dimitris Moraitis wrote:
>  
> 
> Hi Luis, 
> 
> you probably need to change the transcoding options in
> the plone control panel (e.g.
> http://localhost:8080/plumi/@@transcode-controlpanel). Configure the
> deamon host to be http://transcode.c3sl.ufpr.br/ 
> 
> The backend port in
> the apache config for transcode.c3sl.ufpr.br should be the one that
> transcode daemon is listening on. The default is 8888 on localhost.
> 
> 
> Let us know if you have any other issues. 
> 
> Cheers, 
> 
> Dimitris 
> 
> On
> 22.05.2012 04:24, Luis Carlos Erpen de Bona wrote: 
> 
> > Hi,
> > 
> > I'm
> trying to install plumi-4.3.1 with apache (I don't want
> > to open any
> port in the FW expect 80). But I still having 
> > some problems to
> publish videos. 
> > 
> > When I configure transcode to localhost:8888 I'm
> able to
> > submitt and transcode the video (it appears on
> ../transcoded)
> > but I can't watch the video nor download transcoded
> version
> > of it, since localhost appears on video's URL.
> > 
> > I've tried
> to config transcode for a external address of
> > my website and then
> proxy it (following instructions). But
> > then I got the following erro
> in my logs:
> > 
> > ERROR collective.transcode Could not connect to
> transcode daemon 127.0.0.1:8888: unsupported XML-RPC protocol
> > 
> > If I
> understood correctly I should config something like this in apache: 
> >
> 
> > ServerName transcode.c3sl.ufpr.br
> > 
> > http://127.0.0.1:8888>
> > Allow
> from all
> > 
> > Alias /transcoded /home/plumi/plumi.app-4.3.1/transcoded
> >
> 
> > Order allow,deny
> > Allow from all
> > 
> > RewriteRule ^/transcoded -
> [L]
> > RewriteRule ^(.*)$ - [E=BACKEND_LOCATION:127.0.0.1]
> > RewriteRule
> ^(.*)$ - [E=BACKEND_PORT:8888]
> > RewriteRule ^(.*)$ -
> [E=HOST:transcode.c3sl.ufpr.br]
> > RewriteRule ^(.*)$ - [E=PORT:80]
> >
> RewriteRule ^(.*)$ - [E=PROTO:http]
> > RewriteRule ^/(.*)/$
> http://%{ENV:BACKEND_LOCATION}:%{ENV:BACKEND_PORT}/ [L,P]
> > RewriteRule
> ^/(.*)$ http://%{ENV:BACKEND_LOCATION}:%{ENV:BACKEND_PORT}/ [L,P]
> > 
> >
> In the documentation port 8338 is used, but there are no refereces
> abouth which port 
> > it is supposed to be.
> > 
> > My other virtual site
> is:
> > 
> > ServerName video.c3sl.ufpr.br
> > 
> > RewriteEngine On
> > 
> >
> CustomLog /var/log/apache2/access_video.log common
> > ErrorLog
> /var/log/apache2/error_video.log
> > 
> > RewriteRule ^/(.*) 
> >
> http://localhost:8081/VirtualHostBase/http/video.c3sl.ufpr.br:80/VirtualHostRoot/$1
> [L,P]
> > 
> > I've tried a lot of different rewritings without better
> results. 
> > 
> > Thanks for any idea!
> > 
> > Bona
> > 
> >
> ----------------------------------------------------
> > Above my
> site.cfg, if you notice I want to run everything using plumi user.
> > 
> >
> [site]
> > # arch should be either linux32 or linux64. mac support coming
> soon
> > arch = linux64
> > 
> > # 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 debug instance will be listening on
> > instance-debug-address =
> 8880
> > 
> > # hostname and port for transcode daemon
> > transcode-host =
> ${site:local-ip}
> > transcode-port = 8888
> > 
> > #transcode-host =
> transcode.c3sl.ufpr.br 
> > #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
> > 
> > # 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
> > 
> > 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 = Video
> > 
> > # 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 = *:2100
> > 
> > # change that if not using port 21
> >
> ftp-user = plumi
> > 
> > # the addresses of the zope instances
> >
> instance1-address = ${site:local-ip}:8081
> > instance2-address =
> ${site:local-ip}:8082
> > instance3-address = ${site:local-ip}:8083
> >
> instance4-address = ${site:local-ip}:8084
> > instance5-address =
> ${site:local-ip}:8085
> > instance6-address = ${site:local-ip}:8086
> >
> instance7-address = ${site:local-ip}:8087
> > instance8-address =
> ${site:local-ip}:8088
> > 
> > # the icp addresses for each zope instance
> >
> instance1-icp = ${site:local-ip}:8091
> > instance2-icp =
> ${site:local-ip}:8092
> > instance3-icp = ${site:local-ip}:8093
> >
> instance4-icp = ${site:local-ip}:8094
> > instance5-icp =
> ${site:local-ip}:8095
> > instance6-icp = ${site:local-ip}:8096
> >
> instance7-icp = ${site:local-ip}:8097
> > instance8-icp =
> ${site:local-ip}:8098
> > 
> > # effective user for the transcodedaemon
> process
> > transcode-user = plumi
> > 
> > # 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 = plumi
> > cache-address = ${site:local-ip}:8099
> >
> 
> > # haproxy port and host
> > balancer-host = ${site:local-ip}
> >
> balancer-port = 8090
> > balancer-user = plumi
> > 
> > # syslog address
> >
> syslog-host = ${site:local-ip}
> > 
> > # web server user
> > www-user =
> www-data
> > www-address = 8000
> > www-server-name = video.c3sl.ufpr.br 
> >
> www-videoserver-name = transcode.c3sl.ufpr.br 
> > 
> > # effective user for
> zope and zeo processes
> > zeo-user = plumi
> > zope-user = plumi
> > 
> > #
> cache options
> > zeo-client-cache-size = 1024MB
> > zodb-cache-size-bytes =
> 102400000
> > 
> > _______________________________________________
> > Discuss
> mailing list
> > [email protected]
> >
> http://lists.plumi.org/listinfo/discuss
> 
> -- 
> https://unweb.me
>  

> _______________________________________________
> Discuss mailing list
> [email protected]
> http://lists.plumi.org/listinfo/discuss

_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss

Reply via email to