-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TensorRT 8.4.2 #2218
Comments
can you check your LD_LIBRARY_PATH? this file should be under |
|
|
so can be found, but can not load |
I would guess you have more than 1 tensorrt version installed on your system. Can you try |
ok, i try it |
Hi, I downloaded tensorrt by python3 -m pip install --upgrade nvidia-tensorrt, where can i find my ### LD_LIBRARY_PATH? I can't find it in ### /usr/lib/x86_64-linux-gnu. Thanks! |
Hey, I ran into the same error today, the issue is that exporting your LD_LIBRARY_PATH can work, but on Ubuntu, you should really make a file such as |
Hi, I get the same problem, but just remove sudo(./yolov5 -s yolov5s.wts yolov5s.engine s), that works! why? |
For the concerned ones: apparently |
@kevinch-nv for viz |
Is there any update on this? I have the same error and was forced to use |
I am also experiencing this issue with version 8.5.1
All of the TensorRT libraries are installed in |
Setting the RPath of
|
For some reason, setting LD_LIBRARY_PATH doesn't work for me. I also had a minimal repro to confirm that "libnvinfer_builder_resource.so.8.5.1" can't be opened with
This failed at the last line
ls -l shows the files are there
|
@dev0x13 and @Bidski, thanks for this suggestion. I was afraid it would not work because we can't patch in the origin processing flag ( I agree this is a serious regression for deploying TensorRT stuff in production, and it also affects the TensorRT 8.5 releases. |
I had the same problem: But after I copied this file to /usr/lib/x86_64-linux-gnu, the problem was solved. I don't know why, please ask for an explanation.I searched the container for this file and found that it was only available in |
Throwing libraries in systems dirs needs root permissions for one, so this doesn't really "solve" anything. |
I also encountered this problem. Just turn off pycharm and then rerun program |
This is still a problem in 8.5.3. The release notes indicate that the runpath is no longer used as of TensortRT 8.4.1 (https://docs.nvidia.com/deeplearning/tensorrt/release-notes/index.html#rel-8-4-0-EA),
So setting the LD_LIBRARY_PATH, adding to /etc/ld.so.conf, or adding a suitable file in /etc/ld.so.conf.d are apparently the intended approaches. We have added a path to ld.so.conf.d that since we don't install CUDNN or Libnvinfer in the 'default' location. I continue to troubleshoot, despite our application working because the library can now be found.
where funnily I suspect now that there's something special with the builder_resource library - especially since there's this weird
I'll go out on a limb and suggest that this is what is messing things up. ldconfig is making these links and adding them to its cache, but doesn't realize that this is not the name of the library:
so this odd hack breaks the normal search methods of |
Thanks for finding the release note. Ugh, so NVIDIA broke this intentionally and you're supposed to use a wrapper or bootstrap executable before launching the real TensorRT application. Again, adding to I managed to get this working by hacking the libraries to fix back the $ORIGIN/rpath, but seriously the suggested solutions are not reasonable for deployment and this is a major regression. |
Really works for me. Thanks. |
works for me, just remove |
It works ! Good! |
Description
TensorRT 8.4.0.6 is no such problem, but TensorRT 8.4.0.6 has
6: [libLoader.h::DynamicLibrary::50] Error Code 6: Internal Error (Unable to load library: libnvinfer_builder_resource.so.8.4.2)
Environment
**TensorRT Version : TensorRT-8.4.2.4
NVIDIA GPU : RTX-5000
NVIDIA Driver Version: 460.73.01
CUDA Version: 11.1
CUDNN Version: 8.2.1
Operating System: 18.04.1-Ubuntu
The text was updated successfully, but these errors were encountered: