no matching function for call SetTotalBytesLimit(int, int) in building grpc

[sschaud2]

Hi,
I am setting up P4 tutorial environment on my Ubuntu server (not VM).
OS version: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal
For this I'm following scripts in tutorial/vm-ubuntu-20.04 and executed scripts in following sequence:

1. root-dev-bootstrap.sh

2. user-dev-bootstrap.sh

For user-dev-bootstrap.sh, I got errors while building grpc while executing statement "sudo make install". Following are the errors:

In file included from /afs/unity.ncsu.edu/users/s/sschaud2/tutorials/vm-ubuntu-20.04/grpc/gens/src/proto/grpc/core/stats.grpc.pb.h:29,
from /afs/unity.ncsu.edu/users/s/sschaud2/tutorials/vm-ubuntu-20.04/grpc/gens/src/proto/grpc/core/stats.grpc.pb.cc:6:
include/grpcpp/impl/codegen/proto_utils.h: In function ‘grpc::Status grpc::GenericDeserialize(grpc::ByteBuffer*, grpc::protobuf::Message*)’:
include/grpcpp/impl/codegen/proto_utils.h:86:48: error: no matching function for call to ‘google::protobuf::io::CodedInputStream::SetTotalBytesLimit(int, int)’
86 | decoder.SetTotalBytesLimit(INT_MAX, INT_MAX);
| ^
In file included from /afs/unity.ncsu.edu/users/s/sschaud2/tutorials/vm-ubuntu-20.04/grpc/gens/src/proto/grpc/core/stats.pb.h:23,
from /afs/unity.ncsu.edu/users/s/sschaud2/tutorials/vm-ubuntu-20.04/grpc/gens/src/proto/grpc/core/stats.grpc.pb.cc:5:
/usr/local/include/google/protobuf/io/coded_stream.h:401:8: note: candidate: ‘void google::protobuf::io::CodedInputStream::SetTotalBytesLimit(int)’
401 | void SetTotalBytesLimit(int total_bytes_limit);
| ^~~~~~~~~~~~~~~~~~
/usr/local/include/google/protobuf/io/coded_stream.h:401:8: note: candidate expects 1 argument, 2 provided

Protobuf is already installed making grpc.

[jafingerhut]

I have never tried following the steps you have on a system before, so my advice is quite limited.

Did you start from a freshly installed Ubuntu 20.04 system, i.e. one that had just been installed, with no extra packages installed except perhaps for a few things like git, curl, etc.? If there was already a bunch of packages or other software installed on the system, any of them might conflict with assumptions made by these scripts. When developing these install scripts, no attempt has been made to try to make them work for arbitrary sets of packages that might have been installed on top of a freshly installed Ubuntu 20.04 system.

[sschaud2]

It is not freshly installed system and there is good possibility that it had some conflicting packages. Here my intend was to replicate steps VM takes to set up the P4 environment. If I start with freshly installed Ubuntu 20.4, what steps would you recommend?

[jafingerhut]

If you have a freshly installed Ubuntu 20.04 system, I would recommend one of the scripts described on this page: https://github.com/jafingerhut/p4-guide/blob/master/bin/README-install-troubleshooting.md. I test those every month and update them if they need changes to keep working.

I would guess that the scripts in this repository can also be made to work -- I just have not tested exactly which sequence of commands work myself.

[sschaud2]

Thanks! I will try this. I was using VM with its default memory setting and made a few topology changes in the exercise programs. Due to long logs I guess, my VM stopped working and it is not booting up. It throws a "no space left error". Can you help me to understand the way I can make it work? Can I recover it?

[jafingerhut]

My typical approach is to do searches on the Internet for the exact contents of specific error messages, and see if anyone else has found a solution to the particular problem. I do not have any advice other than that.

[jfingerh]

@sschaud2 I saw an email notification on this issue where it appears that you sent some details about an experiment you tried of removing a few packages, then running some of the scripts, and an error message you got.

My best guess is that whatever you did to remove some packages got your system closer to the state of a freshly installed Ubuntu 20.04 system, but not close enough for the scripts in this repo to work.

I test these scripts only on freshly installed Ubuntu Linux system with the stated version. There is no way anyone can test all possible variations of packages or configuration changes that might be made to a system after it is freshly installed. There are too many such variations to test. I am sorry, but I have no interest in taking the (perhaps large) time required to debug exactly what might be different between your system and a freshly installed system.

If you can actually try these scripts on a freshly installed system, I recommend trying that. Otherwise, these scripts are provided as is.

[sschaud2]

Hi, I am sorry for the confusion.
I got some errors in sudo apt-get update. But I resolved it. I removed "-qq" option in the command to see the logs. I identified the problem. It was a local issue and was not related to the P4 environment. Since it was not related to this repo, I deleted it from this page.
With that experience, I understand that it is not possible to test all possible variations and it depends on the local packages.
Update: After resolving my local issue, I got my script running without errors. But I am still working on it as I could not run the example program from the exercise folder.

[sschaud2]

Hi,

I used script install-p4dev-v6.sh and followed instructions from README-install-troubleshooting.md to install P4 related packages and P4 tutorial repository on freshly installed Ubuntu 20.04. It worked smoothly without any error and I can run the P4 tutorial programs on my system without VM.

Thanks, @jafingerhut for your support.