Error during sending logs on some error
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
During sending logs on some issue the client terminated and I was asked to create this bug here
entered message:
I cannot accept a user who follows me. The UI freezes and sometimes throws an error. I accepted this user as follower befor
e and am not sure why the status was changed back?
More feedback (or press <Enter> when done):
error message:
▶ ERROR Error reading logs: Journalctl exited with an error: exit status 1
my log id: df0a2873aaf1a56eb4fa831c
Note:
I recently started using firejail [1] and am wondering whether this issue might be related due to some required directory not being visible 🤔
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the log-sending path that reports "Error reading logs" when journalctl exits with status 1, and investigate whether firejail's directory visibility contributes. Reproduce the failure using the provided error message and log ID where possible; done means the client no longer freezes or reports this error for the described workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100