Timeout (300) Reached.

Here you can submit bugreports
Post Reply
User avatar
kibi
Posts: 106
Joined: Mon Feb 29, 2016 12:57 pm
Contact:

Timeout (300) Reached.

Post by kibi »

"Node failed due to abnormal inactivity during encoding."
Is it possible to gather the information what particular node at what host has met the error?
What's possible to do to avoid such an error?
I produce MP4 files of rather big size, but it seems to be encoded entirely (based on the time of task execution):
29-11-2017 14-00-38.png
29-11-2017 14-00-38.png (29.63 KiB) Viewed 7892 times
I know, that at the last step FFMPEG rebuilds MP4 file (when runs with option "Video: Faststart") and it can take pretty long time.
May it be connected with new features in 0.8.2.2 comparing to 0.8.0.1?
Last edited by kibi on Mon Dec 11, 2017 2:20 pm, edited 1 time in total.
Alexander Sorkin
User avatar
kibi
Posts: 106
Joined: Mon Feb 29, 2016 12:57 pm
Contact:

Re: Timeout (300) Reached.

Post by kibi »

Can you adjust the timeout period accordingly to amount of time already required for a node?
For example, if MP4 Node is working for 10 second only, timeout is 300. 1 hour - timeout 15 min, 5 hours - timeout 1:15 and so on.
Alexander Sorkin
admin
Site Admin
Posts: 1687
Joined: Sat Feb 08, 2014 10:39 pm

Re: Timeout (300) Reached.

Post by admin »

I will take a look at the timeout-routines. Thanks for the feedback! :-)

-steinar
User avatar
kibi
Posts: 106
Joined: Mon Feb 29, 2016 12:57 pm
Contact:

Re: Timeout (300) Reached.

Post by kibi »

Hi, Steinar!
Could you please say whether it's possible to increase the timeout by patching/tweaking config files or maybe make a hotfix for that issue?
Alexander Sorkin
admin
Site Admin
Posts: 1687
Joined: Sat Feb 08, 2014 10:39 pm

Re: Timeout (300) Reached.

Post by admin »

No, currently you can't change the timeout behavour but the next version (0.9.0) will support this.

-steinar
Post Reply