now it seems that Tensorflow is working when i test the set up worked ok via the validation method from the install instructions which brings me to my query…
Ive got something working on my local machine im porting over to the jetson
When i run the script im getting an error re: protobuf
Using TensorFlow backend.
[libprotobuf FATAL google/protobuf/stubs/common.cc:61] This program requires version 3.1.0 of the Protocol Buffer runtime library, but the installed version is 2.6.1. Please update your library. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in “external/protobuf/src/google/protobuf/any.pb.cc”.)
terminate called after throwing an instance of ‘google::protobuf::FatalException’
what(): This program requires version 3.1.0 of the Protocol Buffer runtime library, but the installed version is 2.6.1. Please update your library. If you compiled the program yourself, make sure that your headers are from the same version of Protocol Buffers as your link-time library. (Version verification failed in “external/protobuf/src/google/protobuf/any.pb.cc”.)
Aborted (core dumped)
and tensorflow does seem to be installed on the jetson so im slightly baffled why it’s not working?
I have installed 3.1.0 protobuf.whl however i dont think tensorflow has linked against it. I’m slightly concerned that installing tensorflow without the above install script is going to be a bit of a pain. Is there a simple way to upgrade and link to protobuf 3.1.0 or am i missing something here?
whl files install python modules, typically what you’ll find in /usr/lib/python2.7 and such.
Tensorflow is complaining about the shared library version of protobuf, typically what you’ll find in /usr/lib/
Typically, the protobuf library version is dependent on what version of the host OS you’re using, so for example, if it’s built on Ubuntu 16.04, it proabably won’t run on 14.04.
If it’s failing on the same system where it was compiled, then you have to figure out where the libprotobuf binary lives, and why it’s different from what it was compiled with. There are many reasons this could happen, including library search paths, separate versions used by the Python installer being picked up by the TensorFlow code, and so forth.
I understand the headers could be pointing to the wrong place but what im struggling to grasp is why does tensorflow seem to run ok when importing tensforflow in python yet when i run it in a script its throwing this error?
Ive tried important tensorflow as TF first in order to avoid possible library loading conflicts as some talk of this onine but still no luck.
Im happy to rebuild tensorflow again if thats what it takes but i’m concerned its not going to solve the problem as i would be more or less following the build i did originally.
One option could be to remove tensorflow etc and protobuf, install protobuf 3.1.0 and then go back through the steps above?
This should show various installations of Tensorflow and Protobuf that exist on your system. If there’s more than one, that would explain the discrepancy.
This means that Python code will find version 3.1.
You need to upgrade the C++ (system) library to match version 3.1.
I don’t think there’s a default package on Ubuntu that does this, so you will have to either hack it by building your own and installing it on top of the system package, or you will have to find a deb package that has a newer version that will still install on your current system.
It would be great if you could pin point me to a deb package that has a newer version
I’m not sure such a version exists for Ubuntu. You may have to build it yourself.
This, unfortunately, often happens when trying to build some parts of a Linux system yourself and use some parts from upstream :-(
This is why I try to stay with stock distributions as much as possible. Once I start pulling on the “I do this custom” thread, what ends up happening is that everything unravels, and I have to build larger parts of the system custom than I’d initially hoped for.
It sounds stupid but i would have thought someone else would be getting in to this trouble as i cant be the only person running / attempting to run TF on the jetson…i’m guessing reflashing and starting over from scratch wont help
Where does libprotoc.so live?
Did you replace the one that came with the system?
(It’s a hack to just overwrite it, but you gotta do what you gotta do …)
Also re: hacks etc - i’m not precious what so ever on how this gets solved / the sustainability of the tech stack moving forward. Its to get a proof of concept out of the door and i can make it stable / look at alternative approaches later!
That’s unlikely to work right, although I guess it checks whether the problem is a missing .so itself.
Did you run “sudo ldconfig” after you did “make install” for the protobufs?
You can also start programs with LD_LIBRARY_PATH=… to tell the dynamic loader where to look for dynamic libraries.
So, paths forward you can try:
try with LD_LIBRARY_PATH=…
start with “strace” and look through the output to see what library it’s looking for / finding when it’s loading it, and try to work backwards from there
build everything from source, configured to look at the things you build rather than system libraries. (Or configure to install in the system library directories, rather than /usr/local, and “sudo make install” after building.)
It’s quite possible there’s something dumb that I’ve overlooked, but as this isn’t my system and I can’t poke at it, that’s all I can think of to try.
basically i went through the scripts line by line and found that it was something to do with the import of TF and keras… moving these two to the start of my import statements seems to have fixed that particular issue.
import tensorflow as tf
from keras.models import Sequential (previously in another script which was causing the protobuf when it was called)
Thanks for the guidance @snarky - it really helped a lot and i understand whats fundamentally going on to a point but fixing it via that route seems like a real pain!
Can you please share how did you manage to install protobuf 3.1.0 eventually on tthe TX2?
I have the same problem and wasn’t able to resolve it by importing tf to the start of the code (I don’t even use keras)…
Can you share any info on what language you are using or if you are using another API etc? Might help trouble shooting for us both ! I’d forget about installing protobuf if you need to ugrade it becuase i just couldnt find a distro in the end that was compatible with the jetson and no one here could really do much for me (not for lack of trying and @Snarky helped a lot for me to drill down on certain things).
Do you import tf or any tools from tf more than once in your code?
Can you share any info on what language you are using or if you are using another API etc? Might help trouble shooting for us both ! I’d forget about installing protobuf if you need to ugrade it becuase i just couldnt find a distro in the end that was compatible with the jetson and no one here could really do much for me (not for lack of trying and @Snarky helped a lot for me to drill down on certain things).
Do you import tf or any tools from tf more than once in your code?