FIX: Tianji reporter service failing for SELinux
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 194
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
(forgive me if this is the wrong place)
If Tianji reporter service is not starting after copying the installation command from the Tianji application, check if it is an SELinux restriction on RHEL;
Command: journalctl | grep tianji-reporter
That should bring up something like the following;
tianji-reporter.service: Failed at step EXEC spawning /usr/local/tianji/reporter/tianji-reporter: Permission denied
Now we know which file needs to be allowed through SELinux, and here are the commands;
sudo semanage fcontext -a -t bin_t "/usr/local/tianji/reporter(/.*)?" && \
sudo restorecon -Rv /usr/local/tianji/reporter && \
sudo systemctl restart tianji-reporter.service
No need to reinstall the Tianji reporter service anymore, it should automatically retry and the server should be visible on your Tianji panel by now.
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
The issue provides the journalctl check, the /usr/local/tianji/reporter path, and the SELinux semanage, restorecon, and systemctl commands, but names no documentation file. Start by locating the Tianji reporter installation or troubleshooting documentation. Done means the RHEL/SELinux failure and recovery steps are documented in the appropriate place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100