Foliovision › Forums › FV Player › Bug Reports › Coconut Upload Failures
-
About 50% of the time when I upload a video, Coconut fails to complete processing because of a “bad url.”
The input URL is public
The HTTP server returns a proper response (200)
If the URL is protected with an username / password, verify them
Check the access right if you have setup a firewall
The URL points to a media fileNot only does this cause me a lot of headache in terms of time, it also forces coconut to rename future attempts–which completely screws up my file naming. I can sometimes figure out how to rename things (although fv player then shows the video as a broken link in the video selector), but …
What is the problem here? Why is coconut failing constantly?
-
-
Second attempt failed again —
Hello Russ White,
Your encoding job #21 1-8-f-2-2 has run into some problems.
{“id”:”Jym0OPGc5Z4K7L”,”created_at”:”2024-06-23 21:40:52 +0000″,”completed_at”:null,”status”:”job.starting”,”progress”:”0%”,”input”:{“status”:”input.starting”},”outputs”:[{“key”:”jpg:320x”,”type”:”image”,”format”:”jpg:320x”,”status”:”image.waiting”},{“key”:”jpg:300x”,”type”:”image”,”format”:”jpg:300x”,”status”:”image.waiting”},{“key”:”jpg:1280x”,”type”:”image”,”format”:”jpg:1280x”,”status”:”image.waiting”},{“key”:”httpstream”,”type”:”httpstream”,”format”:”httpstream”,”status”:”httpstream.waiting”},{“key”:”httpstream#above4K”,”type”:”httpstream”,”format”:”httpstream”,”status”:”httpstream.waiting”}]}I’ve double checked the video and it plays on my local computer just fine, so there is some defect in the coconut processing part of the fv player …
This player has so very many bugs … any chance we can get them fixed to make this thing usable in the real world?
One possible solution to this is to create a workflow where I can manually upload files through coconut to be stored on digital ocean, and the add a video playlist manually using the digital ocean url …
The complexity of the full process — uploaded to one folder in digital ocean which triggers a coconut job on a watched folder which then causes a file to be written in another digital ocean folder which then causes the fv player front end to create a video in a playlist is just too complex to make it all work right consistently.
There should be an alternative to this complex process that works more consistently than what we’re forced to use right now.
Hello riw777,
I’m sorry to hear about the issues you are experiencing with FV Player Coconut.
Please let us know what’s the exact filename of one of your failing videos and what’s its size.
I wonder if there might be some special character which we overlook and do not remove before the upload.
Or do you just upload again and then it works without any adjustments? I would still like to know about your file name and size in that case.
Based on your notes it also seems that you tried to upload the video to DigitalOcean Spaces directly and then pick in for encoding on wp-admin -> Coconut Jobs -> Add New. As you noted that workflow is indeed less convenient.
Thanks,
MartinIn this case the file name was 1.8.f.2.mp4. The third time I uploaded it–from the same location on my hard drive, the same file–it succeeded. The first two times it failed. It’s 1,406,670 kb (so 1.34g).
According to the property details:
12:36 length
1920×1080
14921kbps data rate
15239kbps total bit rate
29.97 fpsThe error (bad url) seems to indicate the file is uploaded to the “to be processed” folder on DO, and then is somehow unavailable when Coconut tries to access it. The job normally fails on the https timeout, so a few second (I think it’s 6 here). Rerunning the job has the same result, so it doesn’t look time bound.
What it looks like is Coconut picks up the wrong url or some such when trying to access the file.
I’ve not tried to upload the files directly as there aren’t any instructions on how to do that … I’m not entirely certain which directory I’d put the file in, nor is there an “add new” when I look at “coconut jobs” on wpadmin. When I select “coconut jobs” on wpadmin I only have the existing jobs. The “add new” button flashes, but then it’s disappears, so I assume that has been disabled to force users to upload through the fv player interface.
Hello riw777,
Thank your for your detailed description of the issue.
Please enable the “Debug” settings in wp-admin -> FV Player -> Coconut Jobs -> Settings. Once it’s enabled it should get a link to the log file.
Next time you upload a video it will log all the important events into that file. I expect to see some issue with the multipart upload. Perhaps it’s not closing properly.
So please let us know when you have that log file, it should start with
Log file created.
, followed bycreate_multiupload
and finishing withmultiupload_complete
.If the Add New button flashes, then it might mean that the dialog quickly opens and closes. This issue might be related to the Media Selector Broken issue you are having. It gives me some new ideas, but please follow up on that ticket too.
Thanks,
MartinI just received another failure —
We couldn’t transfer the input file, please check the following:
This is after the file is uploaded to the staging directory … the directory and files are there on digital ocean, and yet it “fails to upload,” and fails to process.
There is a defect in your processing pipeline (like so many other places with this software) that needs to be fixed.
(log file link, redacted)
is the log, which says:
2024-8-05 02:13:44 - multiupload_complete: S3 completeMultipartUpload done: nyc3.digitaloceanspaces.com/rule11-ac-source-vids-to-convert/3.5.a.mp4 2024-8-05 02:13:44 - job_submit: stdClass Object ( [settings] => stdClass Object ( [ultrafast] => 1 ) [input] => stdClass Object ( [url] => https://nyc3.digitaloceanspaces.com/rule11-ac-source-vids-to-convert/3.5.a.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=DO...AT4%2F20240805%2Fnyc3%2Fs3%2Faws4_request&X-Amz-Date=20240805T021344Z&X-Amz-Expires=14400&X-Amz-SignedHeaders=host&X-Amz-Signature=18...28 ) [notification] => stdClass Object ( [type] => http [url] => https://rule11.ac?fv_player_coconut_job_id=31 ) [outputs] => stdClass Object ( [jpg:320x] => stdClass Object ( [path] => //cdn.foliovision.com/3-5-a/sprite-ec5785f76c.jpg [interval] => 0 [sprite] => stdClass Object ( [limit] => 1000 ) [vtt] => stdClass Object ( [filename] => sprite-ec5785f76c.vtt ) ) [jpg:300x] => stdClass Object ( [path] => //cdn.foliovision.com/3-5-a/thumbnail-f69800fbd9.jpg ) [jpg:1280x] => stdClass Object ( [path] => //cdn.foliovision.com/3-5-a/thumbnail-large-49edb4dcc1.jpg ) [httpstream] => stdClass Object ( [if] => {{ input.height }} <= 2160 [hls] => stdClass Object ( [path] => /3-5-a [version] => 3 ) [playlist_name] => index [variants] => Array ( [0] => mp4:240p_320k::maxrate=960k [1] => mp4:480p_700k::maxrate=2100k [2] => mp4:720p_4000k::maxrate=12000k [3] => mp4:1080p_6000k::maxrate=18000k [4] => mp4:0x1440_10000k::maxrate=30000k [5] => mp4:2160p_16000k::maxrate=48000k ) ) [httpstream#above4K] => stdClass Object ( [if] => {{ input.height }} > 2160 [hls] => stdClass Object ( [path] => /3-5-a [version] => 3 ) [playlist_name] => index [variants] => Array ( [0] => mp4:240p_320k::maxrate=960k [1] => mp4:480p_700k::maxrate=2100k [2] => mp4:720p_4000k::maxrate=12000k [3] => mp4:1080p_6000k::maxrate=18000k [4] => mp4:0x1440_10000k::maxrate=30000k [5] => mp4:2160p_16000k::maxrate=48000k ) ) ) )
The file uploaded, but for whatever reason coconut fails to connect to the object storage on digital ocean … that needs to be fixed.
Hello Russ,
Thank you for the log file link, I removed it from your post.
It seems the file uploaded properly to DigitalOcean Spaces using FV Player Coconut, but then Coconut run into some error.
Please browse to your video on cloud.digitalocean.com -> Spaces and see if it plays if you copy it’s download link there and open it in browser. Or you can also download it and then play.
If it works, then Coconut should really just work with it. You can use the instructions from my post in Media Selector Broken thread to submit that URL again to Coconut without having to wait for the whole upload to finish again.
You should be able to delete the failed jobs on wp-admin -> FV Player -> Coconut Jobs. I see that it’s not practical when doing the upload via FV Player editor. I’ll double-check to see if they affect the folder names of the new video folders as a failed job should not do that.
Thanks,
Martin