Hi there,
I am having a strange issue with the video module - I am working with Zencoder, and trying to serve the files from S3. Everything seems to work fine when the node is created, and the video transcoding/upload/callback/playback all works well. However, when I try to edit the node again, it errors out, and the following is written to the logs:

Warning: fopen(): Filename cannot be empty in RequestCore->set_write_file() (line 435 of /vol/var/www/domains/htdocs/sites/all/libraries/awssdk/lib/requestcore/requestcore.class.php).

Warning: fwrite(): supplied argument is not a valid stream resource in RequestCore->streaming_write_callback() (line 577 of /vol/var/www/domains/htdocs/sites/all/libraries/awssdk/lib/requestcore/requestcore.class.php).

Warning: fclose(): supplied argument is not a valid stream resource in RequestCore->__destruct() (line 242 of /vol/var/www/domains/htdocs/sites/all/libraries/awssdk/lib/requestcore/requestcore.class.php).

cURL_Exception: cURL resource: Resource id #205; cURL error: Failed writing body (0 != 6914) (cURL error code 23). See http://curl.haxx.se/libcurl/c/libcurl-errors.html for an explanation of error codes. in RequestCore->send_request() (line 824 of /vol/var/www/domains/htdocs/sites/all/libraries/awssdk/lib/requestcore/requestcore.class.php).

Any help that you can provide would be much appreciated.

Comments

Jorrit’s picture

Jorrit commented
Status: Active » Postponed (maintainer needs more info)

Do you get these errors when you open the node edit screen? Or after you submit the node edit screen?

Jorrit’s picture

Jorrit commented

What is the value for the "Upload destination" field for your field? (I mean the form at admin/structure/types/manage/CONTENTTYPE/fields/FIELDTYPE)

dwilkinson’s picture

dwilkinson commented

The issue appears when you try to edit the node - basically, I can't actually get to /node/edit/[nid]. The "Upload destination" field in the content type is set to "Amazon S3".

Thanks!

Jorrit’s picture

Jorrit commented

My recommendation is to change Upload destination to Public for the moment. It only applies to the storage of the original file anyway, as the transcoded files are always stored on S3 if you are using Zencoder, if you set this up in the Zencoder properties. I will try to fix this bug, but not in the next release, but the one after that.

dwilkinson’s picture

dwilkinson commented

Thanks Jorrit - that appears to have solved the problem for now. I would be looking forward to this bugfix, of course, as storing the originals on the webserver isn't ideal for me. This will help me progress through the development phases, though.

Jorrit’s picture

Jorrit commented
Category: support » bug
Status: Postponed (maintainer needs more info) » Postponed

Great. I'm going to mark this as postponed for the moment.

jhrizz’s picture

jhrizz commented

I have experienced the same thing - going to try this fix ASAP!

I agree- storing the originals on S3 would be good.

The Sorage API employs some interesting logic- primary upload locations & propagation on cron runs. I was actually going to try to use it with the video module, but the field is not eligible- only file fields.

Cheers!

jhrizz’s picture

jhrizz commented

Okay-

So changed from S3 to Public for uploading- all works out as expected, but when I go to edit, screen goes white and I get:

Fatal error: Call to a member function query() on a non-object in /var/www/vhosts/theworkflowengine.com/httpdocs/sites/all/libraries/awssdk/services/s3.class.php on line 2616

Google is not being helpful, any thoughts?

- Josh

Jorrit’s picture

Jorrit commented
Status: Postponed » Postponed (maintainer needs more info)

I see that you are using a later version of the AWS SDK than I use. I'll try to upgrade and see if it still works for me. Am I right that you are using AWS SDK version 1.5.3?

Jorrit’s picture

Jorrit commented

Also, are there any other errors or warnings in the webserver error log or Drupal error log?

jhrizz’s picture

jhrizz commented

This may have been the dreaded Cache- I also disabled and re-enabled the modules and it works!

Again, thanks for your wonderfull support.

Jorrit’s picture

Jorrit commented

Ahh the cache. Can't live with it, can't live without it. If there are not other problems, please close this issue.

jhrizz’s picture

jhrizz commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Will do. I will check to see if the ability to directly upload is already a feature request, and if not, will start one.

markus61’s picture

markus61 commented

following - cause hit by same issue :-(
"drush cc all" does not do anything
everything we can do to help fixing this or motivating jorrit to fix it, we'll consider... ehm almost everything ;-) - cheers, /markus

Jorrit’s picture

Jorrit commented

Markus: What is the value for the "Upload destination" field for your field? (I mean the form at admin/structure/types/manage/CONTENTTYPE/fields/FIELDTYPE)

markus61’s picture

markus61 commented

Upload destination
Amazon S3

that's what you mean?
can we provide you with a screenshot? /m

Jorrit’s picture

Jorrit commented

Unfortunately, that value is not supported at this moment. If you change it to Public files the error will disappear. I am working on getting this fixed in the next release but it is a lot of work.

heneryh’s picture

heneryh commented

Can you at least gray out or disable the option? I got hung up on this too.

Jorrit’s picture

Jorrit commented

I don't need to, because I have implemented this in 7.x-2.x. Be careful when updating to this new version because it contains a lot of changes. Read the release notes and the change record before you update.

Anonymous’s picture

Anonymous (not verified) commented
Category: bug » support
Status: Closed (works as designed) » Active

I am running across this error while running the latest version.

I seem to get this once the video is encoded through zencoder. If I upload the video but don't encode it I can come back to edit the node and also see that the video uploaded to s3.

Is there something I'm missing from the last post?

Thanks.

Jorrit’s picture

Jorrit commented
Status: Active » Postponed (maintainer needs more info)

Could you explain your situation a bit more? Are you running 7.x-2.5 or 7.x-2.x-dev? Could you give a list of steps that you take before you get the error? What are the settings of the video module and your field?

Anonymous’s picture

Anonymous (not verified) commented
Version: 7.x-2.x-dev » 7.x-2.5

I'm running 7.x-2.5. I think since I'm not on dev that may be my case but here is my setup.

Video field:
Upload destination = Amazon s3
Enable auto video conversion is checked.

Video Module:
Video convert on node submit is checked.
Automatically start video buffering is checked.
Transcoder is set to Zencoder with the Output file base on s3 acct.
Preset made for mp4 and ogv conversion.

I add new video content and click save. It actually doesn't encode on save so when I go back to edit the node I can do so but once I save again I get the messaged of it being queued to encode.

I didn't notice you were pointing to the 7.x-2.x-dev so I am going to move to this version and see if it fixes this problem and my other problem here

Jorrit’s picture

Jorrit commented

Upload destination = Amazon s3 is not supported in 2.5, it simply doesn't work. Read the release notes carefully before updating, because some settings have changed, but it should make that setting work.

Anonymous’s picture

Anonymous (not verified) commented
Version: 7.x-2.5 » 7.x-2.x-dev
Status: Postponed (maintainer needs more info) » Closed (works as designed)

I've changed to the dev version and it's all working. Thanks for the help and sorry for my miss understanding.

Jorrit’s picture

Jorrit commented

No problem, thanks for helping to test 7.x-2.x-dev. If you have other problems with this -dev release, please let me know.