Hello and thank you very much for all the help you bring.
My last post related to files_external and one tell me to explore logs. Further more a friend told me about the necessity to understand log when you self hosted a service as NC. I am new in these practice although I use Linux for twenty years. But I never dig this subject.
Would it be possible for you to write a basic methodology to decrypt an ERROR log.
Best regards.
1 Like
Can you elaborate on what you’re envisioning? Perhaps provide an example entry and what you’d hope to understand from it?
The Nextcloud log contains two types of entries:
- Warnings / Errors / Info messages (which if they aren’t clear need to be adjusted themselves)
- Exceptions (stack traces)
The former can be cleaned up for clarity (which happens all the time).
The latter is a bit more challenging.
good point, I have it since ages on my wishlist - showing where to find and how to look into the logs would be good help…
But unfortunately it’s very hard to create generic and easy to read “log reading” and troubleshooting tutorial as there are many many different systems, log methods etc…
I’ll start with few hints. Just for the sake of completeness:
all the areas covered in this topic have it’s own logging mechanism which might be related in some specific troubleshooting case…
content from this post moved to the new 101 article: 101: logging, which logs exist, how to acces and understand
@pierrO I’m doing log reading since more or less ever… as you are starting the adventure it would be great if you read the docs, try some exercises and report your learning and obstacles you hit on the road.
2 Likes
@wwe see How to manage Nextcloud snap logs if you like it use it 