Victor, I tried running it as another user but had various error messages come up - I assume because the user did not have access to some resources required by indytube. However, I've fixed that problem (I think) by saving the flv files to the same server then using "sudo -u plone rsync.." to copy the files to the web-directory. This is now working.
But (ins't there always!) I now have the problem I had before with at least one avi file not transcoding. The errors I get are: ERROR: undefined method `timestamp' for nil:NilClass ERROR: /usr/lib/ruby/site_ruby/1.8/flv/stream.rb:285:in `lasttimestamp' ERROR: /usr/lib/ruby/site_ruby/1.8/flv/stream.rb:274:in `duration' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:181:in `add_meta_data_tag' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:137:in `update' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:47:in `send' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:47:in `execute!' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:46:in `each' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:46:in `execute!' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:206:in `process_files' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2/base.rb:44:in `execute!' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2.rb:168:in `execute!' ERROR: /usr/lib/ruby/site_ruby/1.8/flvtool2.rb:228 ERROR: /usr/bin/flvtool2:2:in `require' ERROR: /usr/bin/flvtool2:2 Input #0, avi, from '/opt/Plone-2.5.5/zeocluster/client1/var/files/Members/rsutton/videos/community_film.avi': Duration: 00:02:44.9, start: 0.000000, bitrate: 1635 kb/s Stream #0.0: Video: IV50 / 0x30355649, 432x324, 15.00 fps(r) Stream #0.1: Audio: pcm_s16le, 22050 Hz, mono, 352 kb/s Resize: 432x324 0:02:44.93 audio: 19kbps video: 0kbps, time remaining: 00:00:00 Are the ruby errors relevant? If not why does it appear to just not encode it? Others files in this users dir encode OK and even one avi file so I'm a bit at a loss as to why this one seems to fail. Any ideas? -- Regards, John Hackett E2BN t: 020 8764 2663 f: 020 8764 1318 m: 07801 231118 e: [email protected] w: www.e2bn.org skype: johh_hackett ----- Original Message ----- From: "John Hackett" <[email protected]> To: "victor rajewski" <[email protected]> Cc: "discuss" <[email protected]> Sent: Thursday, 14 May, 2009 11:29:38 GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [plumi-discuss] indytube problem Victor, Many thanks for you very prompt reply! That does confirm what I assumed - I'll try your fix later and see if it works... -- Regards, John Hackett E2BN t: 020 8764 2663 f: 020 8764 1318 m: 07801 231118 e: [email protected] w: www.e2bn.org skype: johh_hackett ----- Original Message ----- From: "victor rajewski" <[email protected]> To: "John Hackett" <[email protected]>, "Discussion about software development on Plumi" <[email protected]> Sent: Thursday, 14 May, 2009 11:27:44 GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [plumi-discuss] indytube problem Hi John, On Thu, May 14, 2009 at 4:42 PM, John Hackett <[email protected]> wrote: > I think this is an easy one - what user does indytube run as? I believe that by default it runs as root. This is not ideal. You could easily make it run as another user, provided the permissions are set correctly. NFS generally does not allow root access across machines. You might also be interested it this init.d script I wrote recently - it starts and stops indytube via the system daemon scripts: http://plumi.org/wiki/IndyTubeInitScript To change the user you'd have to "su $INDYTUBE_RUN_AS -c /some/command" or something to that effect; there may be hassles involving the log file redirects so make sure your quotes are set up properly. There is also: http://plumi.org/wiki/ZopeInitScripts > > The reason I ask is that I am having some issues with transcoding where the > data files are located on an NFS mounted directory. I thought I had this > working after this move was done but now I'm not so sure! The indytube log > is giving me permissions errors in the flv-files directory although it does, > it appers, have the correct permisisons for the plone and apache users (both > can read/write). However is indytube is running as root on the webserver it > will be denied access to the directory which is really on anther server. > > -- > Regards, > > John Hackett > E2BN > t: 020 8764 2663 > f: 020 8764 1318 > m: 07801 231118 > e: [email protected] > w: www.e2bn.org > skype: johh_hackett > > ----- Original Message ----- > From: "Lachlan Musicman" <[email protected]> > To: "Discussion about software development on Plumi" > <[email protected]> > Sent: Thursday, 14 May, 2009 04:08:19 GMT +00:00 GMT Britain, Ireland, > Portugal > Subject: Re: [plumi-discuss] Apache setup > > nice one, look forward to be able to use it. > > L. > > On Wed, May 13, 2009 at 01:33, victor rajewski <[email protected]> wrote: >> I've been toying with the apache setup conf, and have made the >> following page: http://plumi.org/wiki/ApacheSetup >> >> The first conf is a standard rewrite like what is used currently (some >> comments added) >> >> The second conf allows for putting the flv files in the same >> VirtualHost as the plone site. It doesn't perform the redirect if the >> URI matches a particular pattern - namely /flv-files or something >> equivalent. As long as a similarly named object isn't created in the >> root of the plone site there shouldn't be any conflicts. Can someone >> perform some sanity checking on this approach and the conf file I've >> created? It works on my test setup, and I think it makes installation >> slightly 'cleaner' and simpler. It can also be useful for installs >> that don't have the option of multiple virtual hosts, or a nameserver >> at all (this was prompted by the lack of DNS server at an archives >> install, which has since been resolved by adding a DNS server, but not >> before the idea had become ingrained :) >> >> vik >> _______________________________________________ >> Discuss mailing list >> [email protected] >> http://lists.plumi.org/listinfo/discuss >> > > > > -- > Vive les poissons rouges sauvages! > _______________________________________________ > 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
