#general

Crashloopbackoff Error and Inotify Watches in Signoz Deployment

TLDR Dedy experienced crashloopbackoff errors in Signoz deployment and shared a clickhouse log error. Srikanth asked about inotify watches numbers.

7mo

Join the chat

May 08, 2023 (7 months ago)

Photo of md5-9a70e012174bb20a637d2c960fbe64f7

Dedy

07:11 AM

i have finished deployed the signoz but got crashloopbackoff in my collector metrics, collector and clickhouse,
and i have already check the logs about clickhouse i got

failed to create fsnotify watcher: too many open filestidur

do you can help me?

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

07:21 AM

What are your inotify watches numbers?

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

Issues with SigNoz Setup and Data Persistence in AKS

Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.

8mo

Dashboard Load Issues and Possible Solutions

Al experiences dashboard loading issues since updating to `0.18.1`. Srikanth believes the issue is not version related and suggests examining queries, memory resources, and server distribution for improvements.

7mo

Trouble with SigNoz Cluster and ClickHouse

Jatin is having issues with SigNoz cluster. Hoang advises using an external ClickHouse for ease of control, sharing their own successful experience.

4mo