Describe the current behavior
After running for some time (less than an hour) some requests take long and actually end up with a server error.
One of those requests is the one to check jobs, it seems no new job is run (I have transcoding jobs waiting and no ffmpeg is running on the server so I guess they aren't launched anymore). Also some jobs like activitypub-http-fetcher are timing out according to the logs.
I also have errors about no being able to renew a job lock so it might be related.
Steps to reproduce
- run for some time
- check if jobs page is still accessible
- once it isn't check logs for timeouts or other things showing no job is launched
Describe the expected behavior
No response
Additional information
Describe the current behavior
After running for some time (less than an hour) some requests take long and actually end up with a server error.
One of those requests is the one to check jobs, it seems no new job is run (I have transcoding jobs waiting and no ffmpeg is running on the server so I guess they aren't launched anymore). Also some jobs like activitypub-http-fetcher are timing out according to the logs.
I also have errors about no being able to renew a job lock so it might be related.
Steps to reproduce
Describe the expected behavior
No response
Additional information
PeerTube instance (found in https://instanceURL/about/instance/tech):
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (
journalctlor/var/www/peertube/storage/logs/): https://termbin.com/oxyao