I have a configuration set up that takes an audio file from a CCK filefield, moves the file over to S3, then reattaches the file url back to the CCK filefield. The files are getting moved and the link is getting attached to the filefield when the node is saved. When I look in my logs I'm seeing a specific error and a specific warning for each file that I have processed.

The warning is: warning: filesize() [function.filesize]: stat failed for https://s3.amazonaws.com/path/to/file in /home/path/to/sites/all/modules/media_mover/media_mover_api.module on line 3242.

The error is: filesize() [function.filesize]: stat failed for https://s3.amazonaws.com/path/to/file in /home/path/to/sites/all/modules/media_mover/media_mover_api.module on line 3242.

The one functional problem that has manifested from these errors involves SWF Tools not properly displaying an audio player anymore.

Any guidance on the possible cause of these messages is greatly appreciated.

Comments

arthurf’s picture

arthurf commented

The problem is that the filesize function is trying to operate on a file that doesn't exist on the local filesystem. I think I've solved this in the latest dev. Please give the latest dev version a go and let me know how it works.

Anonymous’s picture

Anonymous (not verified) commented

Thanks for the quick update. The error is gone but the warning, FileField was trying to display the file...but it does not exist, remains.

arthurf’s picture

arthurf commented

Is there any more information on the error than that?

jordanmagnuson’s picture

jordanmagnuson commented

I'm also getting loads of these errors in my log, after moving files to S3:

FileField was trying to display the file https://s3.amazonaws.com/pixeled-memories-files/sites/default/files/templates/user-1/node-734/psd/paisleys.zip, but it does not exist.

Triggered from multiple locations, by anonymous and authenticated users.

mrwhizkid’s picture

mrwhizkid commented

I can confirm this behavior. The file is displayed correctly in the CCK...and can be downloaded...but I'm getting the same error as above about 5 or 6 times in a row after someone tries to access the data in the cck field.