Stephen Sekula
Been having a lot of problems with my peertube instance in the last week. Have not tracked down the issue, though I suspect something in the web server/socket setup that handles transactions between the server and runners on other systems.
The symptom: after transcoding, a runner reports that it "expected 204, got 408" when transacting via http with the main server. It seems time/video size related, happening with files at least 500M in size or larger. Not tied to an obvious file size limit...
Stephen Sekula
Note that it could be a problem for smaller files than 500M. That just happens to be the smallest file so far where I have noticed the problem.
Sometimes reuploading the original file and rerunning transcoding succeeds, but it is NOT consistent. It is also not runner-dependent. The same runner can be fine on one job and fail on the next. So weird.
Stephen Sekula
And for any hard core folks out there, the server is version 7.0.0 and the runners are all 0.0.22.
Stephen Sekula
408 is http code for "Request timeout" which is why I lean toward the web server, not peertube, being the problem. However, I am no web socket or server guru, so where to start tracking the cause is a little unclear to me. The art of problem solving is asking the right question, and I haven't figured out the question.
I have a thought now, though: check the URL returning the timeout and see what my server settings are for that specific path....
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.