dinger1986 / TRMM-Grafana

Grafana Dashboards setup and preconfigured to work with Tactical RMM
30 stars 17 forks source link

debian installation fails to start grafana service because directory has reference/shortcut #26

Closed farleyoc closed 1 year ago

farleyoc commented 1 year ago

In the /etc/letsencrypt/live/example.com/ directory contains reference/shortcuts to the certificates located in another directory Screenshot 2022-11-16 005843

This causes run error with permission denied to the certificates Screenshot 2022-11-16 010158

Solution for my setup was to place a copy of the certificates in the "/etc/letsencrypt/live/example.com/" Screenshot 2022-11-16 010756

Not sure if there is a way to automate this or add into troubleshooting section of the readme?

dinger1986 commented 1 year ago

That directory always has a reference/link I don't think that's why it didn't work as it's a symbolic link.

I'll need to test again so will do that soon.

farleyoc commented 1 year ago

I did a bare metal install with debian, then tactical rmm, then trmm-grafana.

After digging through issue resolutions on github, I knew I hadn't made the typical mistake so I spun up a second fresh debian virtual machine install and closely followed each step thinking I missed something. Same error so I downloaded a copy of the certs and placed them in the folder and moved the references into a backup folder.

FYI

dinger1986 commented 1 year ago

sounds similar to #24

farleyoc commented 1 year ago

Nope isn't similar to #24. I checked permissions and followed the directions for "rmm.yourdomain.com" then "yourdomain.com" before working on an alternative solution not provided in anywhere on github or google. I read every issue you responded to plus searched across the web.

dinger1986 commented 1 year ago

That's ok, was just checking if it was related.

I'll take a look when I get a chance

patzl93 commented 1 year ago

Got the same issue on debian, checked the other threads and permissions. Hope you'll find some time

dinger1986 commented 1 year ago

issue resolved, grafana service is set to run as the tactical user, swapped it now and it works fine, the username was ignored for the service which is shouldnt have been