Telemetry flowing? Brain working? If not, this guide will help you find the source of the problem.
NeurOps centralizes all operational data in the logs/ directory.
logs/neurosight.log: Look here if telemetry isn't reaching the dashboard or Google Cloud.logs/chaos.log: Look here if chaos injections aren't working.logs/neurotalk.log: Look here if the AI Assistant is giving errors.
Pro-Tip: Use tail -f logs/*.log to watch the whole system heartbeat.
Symptoms: Neurosight or NeuroTalk crashes with a message about "Application Default Credentials".
Fix:
gcloud auth application-default loginSymptoms: make startneurops hangs or fails while starting redfish containers.
Fix:
sudo usermod -aG docker $USER
newgrp dockerSymptoms: A specific service fails to start while others work. Fix: Find and kill the process using the port:
sudo lsof -i :8501
kill -9 <PID>Symptoms: The AI chat interface shows an error when you ask a question.
What it means: This usually happens if there is a mismatch in the Google ADK version.
Status: This is automatically fixed by the helpers.py shim. Ensure your codebase is up to date with the latest Makefile fixes.
make status is your first line of defense. It checks if the PIDs exist and if the processes are actually alive.
Check if the simulator is alive manually:
curl http://localhost:8001/redfish/v1/SystemsCheck if messages are reaching Google Cloud:
- Go to the GCP Console.
- Select your topic.
- Go to the "Messages" tab and click "PULL".
Note
If you find a new bug or a weird edge case, please contribute the fix to our FAQ.