An issue with reading pods when using eks 1.31 on amazon linux 2023 (6.1.134-152.225.amzn2023.x86_64)
Describe the bug I am getting an error "Failed to execute script Compiler error on line 33, column 22: Table 'http_events' not found." when I am trying to open px/pods or px/cluster on pixie gui.
To Reproduce Steps to reproduce the behavior:
- Go to 'https://work.dev.withpixie.dev/'
- Click on 'run' when 'px/pods' is selected
- See error
Expected behavior Pods in cluster should showed
Logs Please attach the logs by running the following command:
./px collect-logs
time="2025-07-04T11:22:35Z" level=info msg="Received unhealthy heath check result: rpc error: code = InvalidArgument desc = Distributed state does not have a Carnot instance that satisifies the condition `has_data_store() && processes_data()`."
and
level=error msg=InvalidArgument error="rpc error: code = InvalidArgument desc = Table 'http_events' not found."
time="2025-07-04T12:04:56Z" level=error msg=InvalidArgument error="rpc error: code = InvalidArgument desc = Table 'http_events' not found."
App information (please complete the following information):
- Pixie version gcr.io/pixie-oss/pixie-prod/vizier-pem_image:0.14.14,
- K8s cluster version 1.31 (on eks)
- Node Kernel version amazon linux 2023 (6.1.134-152.225.amzn2023.x86_64)
- Browser version Google Chrome Version 135.0.7049.52 (Official Build) (64-bit)
Additional context In your documentation, there are tips for such error: "Error Table 'http_events' not found is usually an issue with deploying Pixie onto nodes with unsupported kernel versions. Check that your kernel version is supported here."
And there is EKS Supported (includes support on Bottlerocket AMIs), so at the beginning I thought that Amazon Linux 2023 is supported or it is just Bottlerocket AMIs? If so, then I would like to request to add support for Amazon Linux 2023 in future versions.
Hi @andre1704, thanks for reaching out.
Please provide the px collect-logs output from the cluster when it is in this state.
Can you also confirm that you've installed the linux headers for Amazon Linux 2023? It's highly recommended to do so, and the symptoms you've described often result from not having headers installed. You can install them with the following command:
sudo dnf install -y kernel-headers-$(uname -r) kernel-devel-$(uname -r)
I am experiencing the same issue, looking for workaround
@reandrii can you provide the px collect-logs zip file or the full contents of the PEM pod logs?