On 07/01/2013 12:14 PM, Dimitris Moraitis wrote:
That's weird. Are you using a standalone transcode.daemon buildout?
yes, that's what I meant with "I setup a transcoder instance on a
separate machine." :)
I splitted out the transcoder part of the buildout (to be shared soon ;)).
I'm pretty sure that the exception is thrown at line 76 in xmlrpc.py
because of the following call:
encrypt(str((input['uid'],input['fieldName'],profileId)),
self.master.config['secret'])
Perhaps the secret isn't retrieved correctly for some reason?
yes, that is what I am about to debug.
On 2013-07-01 13:11, Simone Orsi wrote:
On 07/01/2013 11:51 AM, Dimitris Moraitis wrote:
I think you just need to configure the transcoder secret to be a
string of 16 or 32 bytes.
Actually I was using the default one from basic buildout, that is
32bytes long https://github.com/plumi/plumi.app/blob/master/site.cfg#L67
I tried to cut it down to 16bytes (1771d99931264d53) but I get the
same error :(
Hope that helps,
Dimitris
On 2013-07-01 12:49, Simone Orsi wrote:
Hi,
I'm setup a transcoder instance on a separate machine. The very same
setup on the same plumi machine works.
When a transcode request is triggered the log of the daemon says:
2013-06-28 15:03:36+0200 [HTTPChannel,5,192.107.92.224] Invalid
transcode request: IV must be 16 bytes long
and the request fails. It looks like I cannot place a pdb into the
daemon to see what is passed (it never stops on it).
Can you give any pointer on the problem itself or at least on how to
debug the transcoder daemon?
Thanks in advance,
S.
--
https://unweb.me
--
https://unweb.me
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
