Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

editing configuration with thruk #1311

Open
bradymd opened this issue Oct 13, 2023 · 0 comments
Open

editing configuration with thruk #1311

bradymd opened this issue Oct 13, 2023 · 0 comments

Comments

@bradymd
Copy link

bradymd commented Oct 13, 2023

Describe the bug
I usually edit the configuration files with vim, however, I need to open this up to users with the GUI however, despite success messages, the underlying files don't change and nor are the changes actually applied.

Thruk Version
thruk-3.08.2-12404.1.x86_64
libthruk-3.00-0.x86_64
naemon-thruk-1.4.1-0.noarch
thruk-base-3.08.2-12404.1.x86_64

To Reproduce
Steps to reproduce the behavior:

  1. Go to Object Configuration as admin (with full rights for all hosts/services)
  2. Click on service, change a feature and save and apply.
  3. Observe the underlying file in Linux and see it doesn't change.
  4. Observe in the GUI the service hasn't actually changed either.

Expected behavior
I assumed it was going to be a file ownership issue, but I've been changing those to investigate.
Currently I expected this file to change as that is where these configurations are.
-rw-rw-r-- 1 naemon apache 2341 Aug 9 15:16 vuh-lb-share6.cfg
It's perplexing because the editing frontend is showing the changes I make.
I can restart and the configuration file isn't changed but the configuration GUI is showing the changes.
The actual object isn't showing the changes of course.

Screenshots
I can provide if you like eg the save and apply give very positive save
Desktop (please complete the following information):

  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
As I say I normally use vim, and will continue to do so until I can work this out. It might be that other files that need permissions opening up. Normally these files have root ownership.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant