Wowza Logo Wowza Icon
Wowza Video Sign Out
Talk to an Expert Free Trial
Wowza Video Sign Out

Wowza Community

Video encoder is stuck, recreating.

Wowza Streaming Engine
#5

@Karel Boek-Senior Consultant Thanks for your decent replies!

I forgot to mention that i’m running on a Windows Server (2012 r2 datacenter).

Running ffmpeg for a while (on a 2hr / 8GB mp4 file), both decoder and encoder are succesfully being adressed.

ffmpeg did show up in nvidia-smi at that point Wowza was still showing ‘insufficient permissions’. I did assume either that it had to do something with user rights. However, now i’m not sure anymore. Can it be because of Session 0 isolation? I thougt that was not applicable on tesla drivers, so never gave my attention to it.

I found a transcode template for wowza 4.2.0 on https://www.wowza.com/docs/how-to-set-up-and-run-wowza-transcoder-for-live-streaming , does this one include the scale tag?

Based on this template I set NVCUVID as decoder en NVENC for encoding. Still with the same results…

#6

If you’re running on Windows, then indeed you must run Wowza in a user environment in order to use the GPU; the Wowza Transcoder cannot use the GPU when running in session 0.

Probably best to test Wowza and GPU first in an UI environment to make sure that the GPU works. If you use RDP, you can decide which session you want to connect to (the “/admin” parameter will connect you to session 0; I assume there’s lots of info on the net that explain this furrher)

And you test with this workaround: https://www.wowza.com/docs/how-to-enable-hardware-accelerated-transcoding-when-running-as-a-windows-service

If none of this works, then maybe better to file a support ticket with support@wowza.com and also check with NVidia how you can make sure that it’s not a hw problem.

#7

I have the Telsa K40c card that is giving the same error. Everything worked properly until 4.8 update along with the new java. GPU decoding works. To the original poster… did you get it to work?

#8

I have the Telsa K40c card that is giving the same error. Everything worked properly until 4.8 update along with the new java. GPU decoding works. To the original poster… did you get it to work?

#9

I have the Telsa K40c card that is giving the same error. Everything worked properly until 4.8 update along with the new java. GPU decoding works. To the original poster… did you get it to work?

#10

@Carey Williamson, the problem is still present. I’m now using ffmpeg for the transcoding processes and output it to wowza. Besides, i’ve added a regular GTX1060 and this card works well within the wowza transcoding environment. It looks like, with the new update, wowza lacks supporting the Tesla K series!

#11

This comment does not address the issue of this thread at all. thanks

#12

this is very aggravating. I have been able to work around this issue through COVID19 by using CPU encoding. Now that my use situation is beginning to get ramped back up, I really need this to be fixed. Have you tried a different version of Java… other than the v9 that is provided by wowza?

#13

Ok @Carey Williamson, upon further discussion in the Engine team, we are seeing general failures with the latest Nvidia Drivers (Version 550 and Cuda 11) Rolling back to 440 does seem to help in most cases. Not all versions of the newest Nvidia drivers support cuda10 (which is what we build against right now).

440 support cuda 10.2. 450+ supports cuda 11. It seems like something breaks for us with cuda 11.

This has been tagged as a feature request and we are updating our docs with the following today:

I’m sorry for the inconvenience, please feel free to send a support ticket if you’d like discuss it with the engineers at Wowza.

#14

@Rose Power-Wowza Community Manager

I just installed the latest CUDA 10.2 compatible driver available for Server 2019… 443.18… The problem persists… pic

I was using driver v398.75 with wowza 4.7.6 with no issues before I upgraded to 4.8.0 and Java9.

What is the possibility of an issue with Java?

I replied to my old support ticket to continue troubleshooting.

Thanks

#15

Sorry @Carey Williamson that is what tech support suggested, but let me get a more specific response to this particular issue for you.

#16

Ok. I’m having tech support take another look at this thread. That error “Video encoder is stuck, recreating.” was happening in 4.8.0 for some folks with your scenario, but was resolved after upgrading to 4.8.5, so our tech support team suspect it was a combination of the OS and GPU model with Wowza Streaming Engine 4.8.0.

But, to make sure you get the correct answer, I am confirming with the engineers the only solution is to upgrade to 4.8.5. Be back soon. Appreciate your patience and communication.

Wowza - 4090 NVIDIA support
#17

I guess I should have mentioned that I did upgrade to 4.8.5 back when it was released. The issue persists.

I have a support ticket that was put on hold through COVID19. It is ticket #347197

#18

the link in this article clearly says that Tesla k series GPUs do not have console access requirements.

#19

more info on my environment… I was running Windows server 2016. Two days ago I did an in-place upgrade to 2019. The issue persists.

#20

I see it. Feel free to reply to that if you’d like to reopen that one as opposed to creating a new one.

#21

Engineers say not a Java issue, we had some other reports of 4.8.0 not working on windows with the kepler cards. Sorry for this and yes I let the engineer assigned to your ticket know you are ready to continue the conversation.

#22

Hi,

I have the same issue with video encoding stuck using Tesla cards. Strange thing is that on some older Windows Servers it’s all running fine. It’s a problem with latest installations. I tried to compare the older and newer servers but cannot find any differences. Also swapped cards between servers but nothing seems to help. Really strange. Anybody find something that can solve this issue?

Thanks, Joost

#23

Can you confirm what version of Engine you’re using @Joost_Sanders? We’ve had a few new releases since then with updates.

#24

Hi,

We use the latest release.

© 2007–2024 Wowza Media Systems™, LLC. All rights reserved.   Security & Privacy PolicyLegalSystem Status