#support

Resolving Log Errors on OpenShift 4.10 Deployment

TLDR lior was experiencing log errors on OpenShift 4.10, Prashant suggested updating the log path and provided potential directories, follow-up is expected.

5mo

Join the chat

Jun 25, 2023 (5 months ago)

Photo of md5-626989119b4514e065ffac057e8e0768

lior

09:02 AM

Hi,
deployed signoz on openshift 4.10 with the kubernetes helm chart,
can't seem to get logs, getting errors on the otel agent:
2023-06-25T08:54:32.640Z warn fileconsumer/file.go:63 no files match the configured include patterns {"kind": "receiver", "name": "filelog/k8s", "data_type": "logs", "component": "fileconsumer", "include": ["/var/log/pods//*/.log", "/var/log/pods//.log"], "exclude": []}

Jun 27, 2023 (5 months ago)

Photo of md5-f936d3e5743d23344d6c60813189716f

vishal-signoz

03:22 AM

Maybe Prashant can help here?

lior

08:08 AM

anybody?

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

08:57 AM

You will need to update /var/log/pods/**/**.log with the relevant log path.

lior

09:25 AM

what is the relevant log path?

Prashant

10:52 AM

Here are some common paths for logs:
• /var/log/pods
• /var/log/containers

10:52

Prashant

10:52 AM

lior which container runtime is being used?

lior

10:56 AM

Openshift 4.10 uses crio

Prashant

11:25 AM

> log_dir="/var/log/crio/pods" The default log directory where all logs will go unless directly specified by the kubelet. The log directory specified must be an absolute directory.
Ref: https://github.com/cri-o/cri-o/blob/main/docs/crio.conf.5.md#crio-table

Jun 28, 2023 (5 months ago)

Prashant

04:32 PM

lior Do let us know if it helps.

lior

04:33 PM

I'll hopefully return to it in a day or two, thanks for checking up.

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Troubleshooting Signoz Deployment for Log Collection on OCI k8s Cluster

sudhanshu faces issues with log collection despite successful application performance monitoring after deploying Signoz on OCI k8s cluster. Prashant suggests updating paths used for log collection and verifying container logs on the nodes. Log files' paths seem correct, but issues persist. Further solutions are needed.

1mo

Troubleshooting Signoz Log Collection in OCI

Harsh had problems collecting logs with Signoz after moving to OCI. Prashant helped pinpoint the problem to OCI's CRI and provided a solution using a specific crio logs path.

2mo

Implementing SigNoz Self-Hosted on K8s cluster

Nicolas was having issues setting up SigNoz on a K8s cluster and forwarding logs through OTel Agent. They were advised by Prashant to use crio log path instead of Docker in Oracle Cloud's managed K8s offering.

Signoz Kubernetes Logs Issue with External Clickhouse

Syed installed Signoz on Kubernetes EKS, but experiencing missing logs and delays using external Clickhouse.

8mo

SigNoz Helm Installation and Connection Issue

Ibrahim experienced connection issues with SigNoz Helm on their Kubernetes cluster and needs help. Prashant suggested checking logs of SigNoz OtelCollector and ClickHouse pods.

5mo