-
Notifications
You must be signed in to change notification settings - Fork 509
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
build_grpc error and vip configuration #110
Comments
Thanks for reporting this issue. This issue was introduced in the commit f6e5cbc I have a candidate fix going through review internally (for that missing function GetVipFlags in |
For the seconds issue, what does the output of Also, do you have decapsulation support on the IP_OF_REAL_WEB_SERVER? If you tcpdump on that host, do you see any incoming packet for the vip? (Also, try tcpdump with additional filter |
Thank you @udippant. Here is the output of
On the real server, (where apache is running), there is no output from tcpdump.
Also, on this node-2 (the REAL), I executed following as mentioned in example.md.
Finally, just to make sure katran is running properly I ran
|
No output from golient -s -sum -lru (0 packets). Xdpdump was not complied with build_katran.sh, should it be or needs to be built separately? I am using mac address of the default gateway for machine running katran (double checked again). On another note, When I start katran, I do see this netlink message, is this normal or katran is having problem receiving traffic?
|
It looks like katran didn't even receive the packet. Do you see xdp-drop (e.g. with That netlink message is likely while adding adding cls-act on the network interface. So shouldn't affect. |
Thanks. I ran ethtool while executing curl 10.200.200.1. However, It seems there is no correlation of xdp drop increase to running curl. The xdp_drop counters just increases slowly even without curl being run.
ip link output is as below:
Full katran command
Mac address of the default router:
I will try to get xdpdump running shortly but wanted to give you above info to see if you can spot any obvious issues. |
I got xdpdump working. There was a linking issue, I had to remove https://github.com/facebookincubator/katran/blob/master/tools/xdpdump/CMakeLists.txt#L48. (Not sure if it was needed) It seems katran is not advertising the VIP (10.200.200.1) so doing curl to the VIP on katran or from other servers (nn1/nn2) doesn't produce any traffic. I tried to curl to base IP (128.110.nn.nn) where katran is running and I see the traffic in xdpdump. But curl to 10.200.200.1 doesn't produce any result in xdpdump.
Is there any way to check if katran is advertising the VIP? |
Katran itself does not advertise the VIP. That part is not open-sourced, which also depends a lot on the environment it is running.
|
Ok sure. For now, I just defined a static route from my client to the katran VIP and everything seems to be working. Thanks. |
Summary: This allows building of xdpdump via the central build-script. (follow up from #110) Reviewed By: avasylev Differential Revision: D25877843 fbshipit-source-id: 7977e88a2251b4d0b98a23e90f521992c8c9bc08
Hi @WagleTanvi how to build xdpdump? Could you please explain here? I need the tool to debug in my server. Thank you! |
Summary: Pull Request resolved: facebook/sapling#110 Pull Request resolved: facebookexperimental/rust-shed#27 Make it so that changes to rust-shed or other common rust source are used locally vendored, so they don't need to be pushed to github before they are visible in a build. There was already some support for cargo vendoring in getdeps, but it was limited to dependencies between manifests built with cargo builder. This wasn't enough to build something like eden (cmake is main entry point, with later calls cargo) or eden_scm (make is main entry point, with later calls to cargo), so this diff adds a cargo prepare step for getdeps other primary build systems. The cargo vendoring is done by using a cargo config file to point to the source files used by getdeps. It has two modes: 1. per crate, existing mode which is already automatic for cargo to cargo manifest dependencies. To use it for a non cargo build manifest, add crate.pathmap 2. per git url, existing mode which was only use for crates.io third-party crates, now can be enabled by setting cargo.cargo_config_file Reviewed By: yancouto Differential Revision: D33895469 fbshipit-source-id: 7b13c0b679532492a336ce217de875c25fe1be90
Hi, I am trying to install/build katran with Ubuntu 18.04 on a physical server using the latest commit of katran.
Katran gets successfully installed with build_katran.sh. However, when running,
./build_grpc_client.sh
. I get this error:After some trial and error, when I checkout a previous commit like
92313218fe81aa5cc112a87a7a9493200a66d8ee
, the build is successful.With this build though, I am having issues with getting katran to respond to vip. I set everything up according to the instructions in example.md. As an initial setup, I have two physical servers in my topology each with one active link on same subnet. One server runs katran and second one has apache web server (REAL server).
Configuring Katran with VIP and Real
On Katran server (I tried on another server as well), when I try to curl the VIP I set up, it does not work. Nothing outputs. This is as if Katran is not responding to VIP.
Please advise. Thanks!
The text was updated successfully, but these errors were encountered: