Hi, seems that some configuration was missed and the transcodedaemon isn't
working properly. This could be related:

2015-11-30T07:21:48 ERROR collective.transcode Could not connect to
transcode daemon http://v.example.com: cannot marshal None unless
allow_none is enabled

What instructions have you followed? You need to edit site.cfg and edit
these two line:

www-server-name = new.plumi.org
www-videoserver-name = newvideos.plumi.org


to point to the 2 dns names that will be used for your portal, example

www-server-name = mgogoulos.plumi.org
www-videoserver-name = videos-mgogoulos.plumi.org


If you haven't access to a dns server, at least do the naming on /etc/hosts
file. You need to run the buildout again for the changes to take effect
./bin/buildout -vN

and after it finishes, then restart services
./bin/supervisorctl restart all

Hope this helps,
Markos



On Wed, Dec 9, 2015 at 5:17 AM, MichaelLeung <[email protected]> wrote:

> well ,  all services are runnng fine , and actually, the red lines in my
> previously reply are the log output when i upload a video file.
>
> INFO:collective.transcode:Initializing
> INFO:collective.transcode:Launched http channel
> INFO:collective.transcode:Launched TranscodeDaemon scheduler thread....
> INFO:collective.transcode:Scheduler thread running
> INFO:collective.transcode:['iso', 'jpeg', 'mpeg2', 'mp4-high', 'mp4-low',
> 'webm-high', 'webm-low']
> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
>
>
> On 12/09/2015 01:35 AM, Markos Gogoulos wrote:
>
> Hi, have you seen my reply? Copy/pasting in case you've missed it
>
>
>
> Hi there,
>
> first check that all services are up and running
>
> [root@production]# ./bin/supervisorctl status
> cache                            RUNNING   pid 19534, uptime 40 days,
> 19:11:47
> nginx                            STARTING
> ploneftp                         RUNNING   pid 19533, uptime 40 days,
> 19:11:47
> transcodedaemon                  RUNNING   pid 19532, uptime 40 days,
> 19:11:47
> uwsgi                            RUNNING   pid 19530, uptime 40 days,
> 19:11:47
> worker                           RUNNING   pid 19531, uptime 40 days,
> 19:11:47
> zeo                              RUNNING   pid 19529, uptime 40 days,
> 19:11:47
>
>
> also check what the logs say when you're uploading a file - and paste the
> output here if the errors continue
>
> [root@production]# tail -f var/log/*.log parts/transcodedaemon/*.log
>
> Cheers,
> Markos
>
>
> On Tue, Dec 8, 2015 at 6:18 PM, MichaelLeung < <[email protected]>
> [email protected]> wrote:
>
>> any update ?
>>
>>
>> On 11/30/2015 04:04 PM, MichaelLeung wrote:
>>
>> have you faced this issue before?
>>
>> On 11/30/2015 03:35 PM, MichaelLeung wrote:
>>
>> seems that my transcodedaemon service is working find
>> tcp        0      0 0.0.0.0:8888                0.0.0.0:*
>> LISTEN      22546/python
>>
>>
>>
>> On 11/30/2015 03:23 PM, MichaelLeung wrote:
>>
>> Hi
>>
>> thanks godness , some is alive
>>
>> no , the problem is still happening, but i think transcodedaemon is the
>> root case.
>>
>>
>> here is plone.log's output when i publish a video.
>>
>> 2015-11-30T07:21:47 INFO plumi.content.subscribers job queued:
>> <zc.async.job.Job (oid 13678, db 'main')
>> ``plone.app.async.service._executeAsUser(('', 'Plone', 'Members', 'admin',
>> 'videos', 'test-1'), ('', 'Plone'), ('', 'acl_users'), 'admin',
>> plumi.content.metadataextractor.setup_metadata)``>
>> ------
>> 2015-11-30T07:21:48 ERROR collective.transcode Could not connect to
>> transcode daemon <http://v.example.com>http://v.example.com: cannot
>> marshal None unless allow_none is enabled
>>
>> here is the trandcodedaemon.log's output while i click the 're-Trancode'
>> command.
>>
>> INFO:collective.transcode:Initializing
>> INFO:collective.transcode:Launched http channel
>> INFO:collective.transcode:Launched TranscodeDaemon scheduler thread....
>> INFO:collective.transcode:Scheduler thread running
>> INFO:collective.transcode:['iso', 'jpeg', 'mpeg2', 'mp4-high', 'mp4-low',
>> 'webm-high', 'webm-low']
>> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
>> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
>> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
>> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
>> ERROR:collective.transcode:Invalid transcode request: checksum mismatch
>>
>>
>>
>>
>>
>>
>> On 11/29/2015 07:56 AM, Anna Helme wrote:
>>
>> Hmm, not sure, we haven't noticed any issues with avi files... is
>> everything else working okay?
>>
>> Try with another avi file, in case you have a problem with that
>> particular file?
>>
>> On 25/11/2015 10:26 AM, MichaelLeung wrote:
>>
>> Hi,
>>
>> so far, uploading mp4 file  can be support on my Plumi , but not avi
>> file.
>>
>> any way to fix this problem ?
>>
>>
>> _______________________________________________
>> Discuss mailing 
>> [email protected]http://lists.plumi.org/listinfo/discuss
>>
>>
>>
>>
>> _______________________________________________
>> Discuss mailing 
>> [email protected]http://lists.plumi.org/listinfo/discuss
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Discuss mailing list
>> [email protected]
>> http://lists.plumi.org/listinfo/discuss
>>
>>
>
>
> --
> https://unweb.me
> state of the art information systems
>
>
>


-- 
https://unweb.me
state of the art information systems
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss

Reply via email to